How do I codesign an App?

[Paul Dupuis]

Isn't code signing platform specific? Meaning, don't you have to code
sign a OSX Standalone on OSX and code sign a Windows standalone on Windows?

I would eagerly second adding code signing to the IDE if it could be
done cross platform. I.e. if I develop under Windows, I could sign the
OSX and Windows standalones I build OR if I develop under OSX, I could
code sign BOTH the Windows and OSX standalones (with different
certificates of course)

I'd even chip in money to a Livecode Feature Exchange for this ability.

Currently, I develop under Windows, build a Windows and OSX standalones,
code sign the Windows standalone via the command line interface, move
the OSX standalone over to an OSX system and code sign it there via
AppWrapper (and I use AppWrapper because Apple code signing through
Xcode is way too complicated!) I'd love to be able to drop both
certificate files into a LiveCode folder and have it just sign for both
platforms.



On 10/26/2016 8:39 AM, Trevor DeVore wrote:
> On Tue, Oct 25, 2016 at 9:51 PM, William Prothero <prothero at earthednet.org>
> wrote:
>
>> Trevor:
>> Thanks a bunch! I haven’t played with the GLX App Framework, but I will
>> and use that code. This is something that really needs to be in the IDE.
>> Its SUCH a common thing to do and can be so frustrating.
>>
>> The other problem I get into is having a bunch of certificates that don’t
>> work and I can’t seem to figure which one to use. I try them all, so…
>> Anyway, the signing code looks like a natural for the IDE.
>>
> Here is a gist with the code for a script-only stack that will codesign a
> LiveCode application:
>
> https://gist.github.com/trevordevore/3e91724c4573690b691510d2e2dcd2a7
>
> Save the text in the gist to a file named “signOSXApplication.livecode”
> then open the file in LiveCode (I tested in 8.1.1). Steps:
>
> 1) Click the Sign Application button
> 2) Select an application bundle that you built with LiveCode
> 3) Enter your certificate name. Just enter the part that is unique to you.
> For example, I enter “Blue Mango Learning Systems”. My keychain has entries
> like “Developer ID Application: Blue Mango Learning Systems” and “3rd Party
> Mac Developer Application: Blue Mango Learning Systems”. The code will add
> the appropriate prefix.
>
> The log field will show what is going on.
>
> I tested with a simple app built from LiveCode on macOS Sierra. Last week I
> had to add some additional code to the signing process to accommodate
> Sierra. If you run into problems on other platforms we may need to comment
> out the xattr call on line 60.
>
> Let me know how it goes.
>