On Tue, Oct 25, 2016 at 9:51 PM, William Prothero <proth...@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. -- Trevor DeVore ScreenSteps www.screensteps.com - www.clarify-it.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
