User Profile

Posts

Posts

Post marked as solved
2 Replies
367 Views

Loadable bundle symbol name conflict

I'm building a plug-in (loadable bundle) for Adobe Illustrator (macOS) which uses boost extensively and boost is linked statically. The host application also uses boost albeit a different version and they include it as a framework. As it turns out, when my bundle is loaded by the host app, the dynamic linker prefers the function from the framework that comes with the application and not from the bundle, causing compatibility errors. Is there a way to instruct the dynamic linker to always prefer symbols defined in the bundle?
Posted
by DmitryO.
Last updated
.
Post not yet marked as solved
18 Replies
4.2k Views

Notarizing a loadable bundle

HiI'm trying to notarize a plug-in for Adobe Illustrator (project type: Mach-O Bundle).I have signed it with a Developer Id certificate and have enabled hardened runtime. The bundle contains 2 binaries: the main binary and a helper tool. Both binaries are reported signed by codesign -d -vv, as well as the bundle itself is.After a few attempts I finally managed to get "Package Approved" from the notary service, but the approval only contains a ticket for the helper tool, but not for the main bundle binary.Some of our products don't contain a helper tool. Trying to notarize such a bundle, I always get an error saying "Package has no signed executables or bundles. No tickets can be generated".Is this normal behavior, or am I doing something wrong? Non-notarized bundles are no longer loaded by the host application on macOS 10.15 beta.
Posted
by DmitryO.
Last updated
.