Yeah, sounds like it lost the correct permissions during the transfer to the mac. you can either chmod 755 <executablefile>
I think you have to go into the app package and hit the actual executable, don't think it will work on the app package itself. (You can probably also set the permissions using finder.. go to where the app package is located, bring up the context menu and show the package contents, then drill down through contents/MacOS to locate the binary, get the context menu for the file and get info and from there, set the permissions. (for everyone, probably read and execute, not write.) Sorry for kinda glossing over all this. I can't get on a mac mac at the moment, so I can't give exact steps. On Fri, Jul 1, 2016 at 7:21 AM, Klaus major-k <kl...@major-k.de> wrote: > Hi friends, > > a client of mine has compiled a Mac standalone on Windows and now the app > will not run: > "The application XXX cannot be run" or what the exact english message > reads!? > > I remember faintly there is some problem with erm. "executable bit"? > But forgot the details... > > Or does the app have to be compiled on a Mac, to run properly? > > Any hints highly appreciated! Thank you! > > > Best > > Klaus > -- > Klaus Major > http://www.major-k.de > kl...@major-k.de > > > _______________________________________________ > 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 > _______________________________________________ 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
