View Single Post
Old 02-21-2021, 10:16 PM   #9
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,455
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Yes, once can disable library validation at build time, but this is not suitable for general calibre builds. You could possibly workaround it by either:

a) disabling gatekeeper on your mac
b) building calibre from source yourself
c) re-doing the code-signing of the entire calibre bundle using an adhoc signing key and removing the library validation restriction when doing so

And yeah, this whole thing is utterly ridiculous on Apple's part. It's so, umm moronic, that they allow processes to load code in the form of text files, but not pre-compiled code, as if one is more or less capable than the other of doing harm.
kovidgoyal is offline   Reply With Quote