LiveCode Forums.

I can't follow this discussion. If Richmond hasn't suggested LC did anything wrong I misread his post. So let's say I'm to blame for blaming Richmond for blaming LC for the differences between OSes.

I wonder if we might let the OP have his thread back? I can't remember the last time a thread here stayed on topic...

Well, I sure ain't blaming you, so I sure hope I don't hear about me having did any such a thing. I'm pretty sure no one really is blaming anyone, I am sorry if you feel like someone is.

No worries. I'll happily go along with whatever might get this thread back on the OP's topic.

Maybe Richmond can propose some alternate wording is feels is important to the team for their consideration.

Err . . . How about:

Code on any platform: compile on target.

Or . . .

Never believe completely what is written on the box.

richmond62 wrote: Thu Apr 09, 2020 7:10 am Err . . . How about:

Code on any platform: compile on target.

Or . . .

Never believe completely what is written on the box.

Yes, I got it now !


As long as people know it ("compile on target"), then I believe we can live with it.

As I wrote, i'm totally lost with my new MacBook Air (last time I used a mac was... in 1995, since then i went to the other side of the "force"). And I was afraid to miss something important, a special parameter in LiveCode.

So anyway thanks all for your answers.

It's not necessary to compile in the target platform. You can compile for nearly all platforms from nearly all platforms, with the exception that Apple requires you to buy a Mac to deploy to iOS, and deploying to Mac from Windows will require that you set the executable bit.

And itlf you mount a network volume with a Unix or Linux file system you should be able to compile to that even from Windows.

It may even be (don't take my word for it, fuzzy memory and never needed to do this myself) that if you zip the Mac bundle before copying it from a Windows machine the executable bit is preserved.

And all stacks can be run from a copy of LiveCode in any supported platform, regardless of the platform they were made on.

Try to reduce that to a single sentence.

Try to reduce that to a single sentence.

I'd rather wash the dishes.

I thought some Windows setups could preserve things like the executable bit, like the way that some WinNT servers supported the classic Mac OS 9 resource forks back in the day? And there's software like "MacDrive" for Windows that let you use Mac HFS+ formatted drives in Windows, as well as other software that let you use EXT *nix formatted partitions (although the MacOS can't natively read those either).
Also, I didn't think you could set the executable bit on the Mac app binary from the "Get Info" window, only certain basic user/admin permissions. I've always used the Unix command from the terminal (sudo chmod +x "pathToMyBinary) to do that when the need has risen (rarely).

As a test I just copied the Mac OS (Mohave 10.4.x) app/bundle TexEdit.app to an NTFS formatted drive shared from a Windows server over SMB file sharing and it launched on the Mac from there without a problem.

Huh, I had never tested doing an app from any other platform to Mac until this morning, where I had some time to waste. I fired up my (ancient) OSX 10.6.x Snow Leopard, and created a simple testHello stack. No surprise, it ran with no issues.

I moved the stack to my 'nix box, and saved it as a mac 32bit standalone there, then uploaded it to dropbox, then downloaded it to Snowy. What a shock, I could not get it to run to save my life.

Now, I don't normally consider myself to be the brightest bulb in the pack, but I would put myself on par with the average user no matter which desktop environment I'm in. Someone want to point out what I might be missing?

Wow, I thought this might have taken all of an hour to get a reply too. You mean to tell me no one has made an OSX app from anything other than an Apple computer? Was my question not clear enough? Everyone else took it as a joke or something? Is 'the yoke on me' ?? Is this thing on?? Bueller....Bueller....

I did try it some time ago and it didn't work. I have not tried recently though. From what I understand, the actual binary needs the execute bit set (which is a couple of levels down in the package).

Ok, just tested...

In the terminal, need to navigate to the folder holding your app and... or simply

bwmilby wrote: Tue Apr 21, 2020 3:27 am or simply

Code: Select all

chmod +x AppName.app/Contents/MacOS/AppName

Thank you.

And it's working now (see my first post : stack compiled on windows for mac, then directory copied onto the Mac via file sharing, and then the chmod instruction and then double click to open/launch the app).

LOL! I had tried that yesterday when I still hadn't seen a response, and it didn't work here anymore than previously. Man I just love being a special snowflake

./TestHello.app