#Mac os 10.9.5 update to 10.10 how to

Signatures created with OS X Mountain Lion 10.8.5 or earlier (v1 signatures) will be obsoleted and Gatekeeper will no longer recognize them. On the subject of signing for Mac, Apple recently sent out an email stating: You can avoid this by using cp -R instead. So you end up with 3 copies of each framework library. It turns out that the cp -r commands in my script don’t preserve symbolic links. The first time I ran my script I ended up with a whopping 50MB. Note that you can just find and replace all the ‘5’ characters in the script by ‘4’ if you are still using Qt4. In the above rebundle.py is a Python script written by some public spirited individual that can be downloaded from github (thank you, ‘kingcheez’). This is all stuck it all in a bash script, which I can pretty much forget about it (until Apple break something else). dmg image file complete with licence and background image. (Sorry about the small font, but I wanted to avoid confusing line wraps). # the 2 lines below are just for verification/diagnostics app bundle (including frameworks and plugins)Ĭodesign -deep -force -verify -verbose -sign 'Developer ID Application: '. # optionally delete unwanted framework and plugin folders, e.g.: So here is the basic process to build and sign your Qt. The good news is that Apple have also made the codesign command easier with a -deep option to traverse and sign the whole bundle in a single command.

#Mac os 10.9.5 update to 10.10 how to

I managed to work out how to get it working again after a bit of digging around.

The problem appears to be that the directory structure of the app bundle has changed and the Qt4 macdeployqt command does not conform to the new layout (I believe this is also the case for Qt5). Those Apple chaps do love to break stuff. It all worked fine until I upgraded to Mac OS X 10.9.5, which broke my signing script. I have written previously about signing Qt applications for Mac OS X.