Mac Xcode 11 Generator bug/problem with CODE_SIGN_IDENTITY default

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Mac Xcode 11 Generator bug/problem with CODE_SIGN_IDENTITY default

Eric Wing
I hit a problem with the CMake/Xcode Generator using Xcode 11. (I
think this problem started in Xcode 10 actually, but now I'm blocked
really hard and need to solve this.)

By default, Xcode is now trying to do "Sign to run locally" for the
Code Signing Identity (CODE_SIGN_IDENTITY) property, by default.

For trivial apps with no embedded libraries/frameworks, this seems to
get through. However, for my real, more complicated projects, I have
bundled libraries/frameworks. But since CMake doesn't really have full
support for Xcode signing, the embedded libraries/frameworks are not
signed, and the code sign process to local sign the .app fails.

So to workaround this, I would like to tell Xcode to disable code
signing entirely.

Unfortunately, the only way to disable this seems to be to set the
CODE_SIGN_IDENTITY to "", i.e. make the field completely blank. The
following link shows all the steps with pictures, but basically you
set the box to "Other" and then submit a completely blank input box.
This internally in the Xcode project sets CODE_SIGN_IDENTITY to "".

But my problem in CMake is that when I try to set the Xcode property
to "", it ignores the setting and defer to Xcode's default value of
"Sign to run locally".

# This has no effect

How can I force this property to be overridden with ""?


Powered by

Please keep messages on-topic and check the CMake FAQ at:

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support:
CMake Consulting:
CMake Training Courses:

Visit other Kitware open-source projects at

Follow this link to subscribe/unsubscribe: