On 7/12/16, Harry Mallon wrote:
> 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
>
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 :
>
> Hello all,
>
> What is the current best practice for
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
${
