[Openmcl-devel] Codesigning a CCL based applicaiton
R. Matthew Emerson
rme at clozure.com
Wed Aug 29 12:15:13 PDT 2012
On Aug 29, 2012, at 3:04 PM, Michael Minerva <minerva at agentsheets.com> wrote:
> I am still just a little confused about what I need to do. It seems from your script (and from my interpretation of your message) that I need to: goto the lisp kernel directory and do a make clean, copy all of the files from ccl into MyApp.app/Contents/Resources/ccl, then finally execute the codesign command. Does this sound about right?
You may not need to copy all of them, but yes, you put the files you want in that directory, and then sign the bundle.
> I tried doing that but still get the same error.
If you get the same error, then I assume that you must still be trying to sign a heap image with a prepended kernel. When you call save-application, make sure that you do *not* specify :prepend-kernel t. If MyApp.app/Contents/MacOS/MyApp is larger than about 400K, then you've probably got a heap image in there.
> I am wondering if maybe my problem is name related? In your example you said the lisp kernel should be at: MyApp.app/Contents/MacOS/dx8664cl and the image should be in: MyApp.app/Contents/Resources/ccl/dx86cl64.image. In my case my kernel is called: MyApp.app/Contents/MacOS/MyApp and the image is: MyApp.app/Contents/Resources/ccl/dx86cl64.image do these two need to have related names?
Yes, they do. If the lisp kernel is named "frotz", then the heap image should be "frotz.image".
More information about the Openmcl-devel