[CMake] OSX Code Signing best practice

[Roman Wüger]

Is it possible to sign after your package is complete (copying resource files and so on)?

I call a *.sh which is created from the CMake configure step which do the job.

Best Regards
Roman

> Am 12.07.2016 um 18:49 schrieb Harry Mallon <Harry at codexdigital.com>:
> 
> Hello all,
> 
> What is the current best practice for code signing OSX .apps and binaries? I am using:
> 
> 1. MAC_OSX_BUNDLE for my .app targets.
> 2. unix style executables
> 3. dylibs
> 4. A prefpane (which I haven't got working yet) using something like the below:
> 
>    add_library(prefpane MODULE
>        ${sourceFiles}
>    )
> 
>    set_target_properties(codexprefpane PROPERTIES
>        BUNDLE YES
>        BUNDLE_EXTENSION prefPane
>        XCODE_ATTRIBUTE_WRAPPER_EXTENSION prefPane
>        MACOSX_BUNDLE_INFO_PLIST ${prefpane_plist_file}
>    )
> 
> I am not using the CPackBundle generator so I cannot use the signing in that. I have tried:
> 
> 1. Using set_target_properties( .... "XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY" "${SIGN_ID}")
> 2. Using an add_custom_command step. This code signs before all the Resources are copied in so the signatures are invalid
> 
> Any ideas?
> Harry
> 
> Harry Mallon
> CODEX | Software Engineer
> 60 Poland Street | London | England | W1F 7NT
> E harry at codexdigital.com | T +44 203 7000 989
> -- 
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake