Properly code-signing an app with bundled JRE

Paul Taylor paul_t100 at fastmail.fm
Tue Jan 28 12:36:46 PST 2014


On 28/01/2014 19:05, Hendrik Schreiber wrote:
> On Jan 28, 2014, at 19:56, Hendrik Schreiber <hs at tagtraum.com> wrote:
>
>> On Jan 28, 2014, at 19:28, Paul Taylor <paul_t100 at fastmail.fm> wrote:
>>
>>>> This email sent to paul_t100 at fastmail.fm
>>> I can confirm I had to change it to use --deep option a while ago for it to work, I do bundle it with a jre and it still works, but maybe not as a plugin not sure what you mean here.
>> I package the JRE into MyApp.app/Contents/PlugIns/jre - so in essence it's a plugin.
>>
>> Would you mind sharing your codesign call, Paul?
> Though from reading http://furbo.org/2013/10/17/code-signing-and-mavericks/ it sounds like Steve took the "correct" approach by signing the plugin individually.
>
> -hendrik
Ah right, I package my application up using  the BitBucket branch 
AppBundler https://bitbucket.org/infinitekind/appbundler whihc just 
relelized all puts the jre in the plugin folder

but I only have to do this

/usr/bin/codesign --sign "Developer ID Application: P Taylor" --force 
--deep --verbose /Applications/SongKong.app
/usr/bin/codesign --verify --deep  --verbose /Applications/SongKong.app

and it works, or at least seems to.

Paul






More information about the macosx-port-dev mailing list