#944 Signing requirements for OSX builds...

[Daniel Kulp]

In order to sign the CodeBlocks.app that is generated with the bundle.sh command, the info plist needs a minor update. The CFBundleExecutable value needs to be lower case to match the actual executable name. This needs to be applied to src/build_tools/Info.plist and codeblocks.plist.in. Simple patch.txt attached.

I've also attached a signing shell script that will do the signing, package the app into a dmg, submit for notarization, staple the notarization, repackage to notarize the dmg with the now notarized app, submit that, and staple the notarization to the final dmg. This requires an Apple developer ID with appropriate keys and such. See the top of the script the information it needs.

[Teodor Petrov]

Interesting what does

# libProfiler doesn't sign correctly, we'll just delete it for now

mean? Is there a way to diagnose the problem?

[Andrew Cottrell]

The patch was applied as [r12315], but the sign.sh is not included so it is not in the source tree!!!!

[Miguel Gimenez]

Is sign.sh up to date and useful? Where should it be in the source tree?

[Andrew Cottrell]

Miguel, I am going through the Mac tickets as I now have the ability to debug (okay simple debugging at the moment) on a virtual MacOS using the the DAP debugger I/F and when digging into this ticket founds that part of the patch was applied and part was not.

At the moment I cannot answer the questions as I am a Mac noob. I have put it in my local CodeBlocks_MacOS directory, but as for the C::B truck I have no idea.

I would defer to Xaviou for where it should be in the source tree, but you may need to PM him via the forum to get answers to the questions.