 |
Hi Michael, Thanks for investigating the package signing issue. If you manually create the missing sym links and add the info.plist files where needed, are you able to successfully sign the package ? |
 |
Yes, I could sign it with my own Apple Developer ID. Unfortunately, we can't use the signing certificate issued by Digicert. Only Apple Developer IDs are recognized as valid by the Mac OS X Gatekeeper. We need to figure out details of the workflow (probably creating a slicer.org company developer account), but the technical issues are basically solved. |
|
|
Please, test the following topic: https://github.com/jcfr/Slicer/tree/3965-fix-bundled-qt-framework-layout Could you also add some instruction on the wiki: http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/ReleaseProcess#Sign_packages Kitware may be able to sign the packages, I will check the feasibility. That we would have also this option. |
|
|
Preliminary testing shows I can sign the resulting binary with my Apple Developer ID certificate without error. I will document more fully, but the code signing command is of the form: codesign --deep --force --sign "Developer ID Application: ..." ./Slicer.app where the argument to --sign is the name of the developer's certificate in Mac OS X Keychain.app . |
|
|
Hi Michael, Thanks for testing. Associated changes have now been integrated. |
- Anonymous
