Bug #1993

Mac build environment has started producing improperly-signed plugins

Added by Chris Cannam 14 days ago. Updated 11 days ago.

Status:NewStart date:2020-06-26
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


Seeing the same problem as described here:


Some update within the Mac build environment has resulted in plugins within the bundle (correctly signed) no longer being tagged with any SDK version, and therefore being regarded as unsigned when we come to load them.

The workaround is to add the disable-library-validation entitlement, and I've done that, but it shouldn't be necessary.


#1 Updated by Chris Cannam 11 days ago

Our build was still using Qt 5.13, but 5.15 is now current. Building with 5.15 does fix this - it passes the isysroot arg to the linker as mentioned - but sadly Qt 5.15 increases the minimum supported macOS version from 10.12 to 10.13, and I really don't want to do that yet. Am about to try Qt 5.14 and see how that goes.

#2 Updated by Chris Cannam 11 days ago

Qt 5.14 is the worst of both worlds - it does things the old way (resulting in no SDK key in the binary) but also specifies macOS 10.13 as the minimum version. Looks like a build hack is required.

Also available in: Atom PDF