LiveCode Forums.

AND who, pray tell, is trying to build a combined 32-bit & 64-bit standalone on a Mac at the moment, and with which version of LiveCode? I thought I was retro, but . . . If I ever need to run of 32-bit standalones (which I do about once a week when my school is open) for Macs I use a version capable...

Thanks, that helps. Looking up the lipo command, I get this definition: Create or operate on a universal file: convert a universal binary to a single architecture file, or vice versa. It's a Mac-only command and it sounds like it will allow ...

-
Not really very informative.

I'm tellin ya Craig, PostImage, it is a great resource

What does the dialog say exactly? (It's too much trouble to download a file, unzip it, and look at it on a mobile device.) Posting the image here directly would work too.

... splash would not allow any external stack files to be attached. I trashed it and created a new one, and all is well. But that is the moment the LIPO dialog started to appear during a standalone build. They does not seem to be harming anything; I do not even have to dismiss them. My Mac itself ...

LC is not used for Liposuction.

Installing upgrades to macOS 11 requires you reinstall the command line tools each time:

viewtopic.php?f=5&t=35277

I all of a sudden started getting about three of these during a standalone build.
Any reason for this?
Craig

-
Yuck!

You are allowed to use lipo to combine different architectures into a single framework, but Apple forbids the combining of different platforms (macOS and iOS). It seems to work OK, and it's often done for frameworks distributed outside ...

-
odd message when building a Mac standalone.

?

Seems a bug. We scripters should never be bothered with engine implementation details. FWIW, I found some background on lipo - if the name reminds you of "fat", there's a reason for that, it's a set of utilities for the modern equivalent of what Apple used to call "fat binaries": https://eclecticlight.co/2020/07/24/magic-lipo-and-testing-for-universal-binaries/

But the "Lipo" thing is odd. Building for iOS? No. desktop. Do you know what that is? But now my only recipe is to send my project to Scotland. I don't have problem with that; it is purely for in-house use. But does this make ...

Good to see that whatever had caused the errant substack copying appears to have been fixed.

But the "Lipo" thing is odd. Building for iOS?

... the same inclusions as in my main project. During a standalone build, I get no dialog asking about cursors. I do get a dialog telling me that the "Lipo Command" requires command line developer tools, and offers a version of XCode. I do not use, or even have XCode resident. Craig