-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building with "macOS Intel" and "macOS Apple" fails #207
Comments
I was wrong - if I select both "macOS Intel" and "macOS Apple" in Standalone settings, It builds an Intel version and then tries to build a separate Arm version but aborts on the Arm version when it is unable to moved it into the macos folder, unless I move the macos folder and Intel app out of the build folder in between. But no Universal version. With a previous version of LC (can't remember) it was building a universal version. I may have upgraded to Ventura since then as well. If I build a non-Levure app with the "macOS Intel" and "macOS Apple" options it makes one universal app. |
@martyknapp I got a chance to look at this today and put a PR together that should fix it. If you use the packager script from https://github.com/trevordevore/levure/blob/tkd/issue-207/packager/packager.livecodescript you should be able to test. |
Hey Trevor,
Good news. I was able to build a universal app. However I had to remove the AppUpdater helper from the build to get it to run, otherwise it crashes. It appears the Sparkle Framework in this helper is Intel only. I did update to the latest Sparkle version 2.4.2. I found where it looks like I can download a universal version here:
https://github.com/sparkle-project/Sparkle/releases/tag/2.4.2
and then the “Sparkle-for-Swift-Manager” appears to have the universal version in the folder “macos-arm64_x86_64" but in looking at the app updater helper, the code folder only has a subfolder for “x86_64-mac” I tried placing the new universal framework there and it seems to work on an Intel Mac (a least reporting that the app was up to date). But it crashes on an “M” chipped Mac even under Rosetta
Thanks again Trevor, the framework is so great for building apps and I appreciate all you’ve put into it.
---
Marty Knapp
… On Sep 14, 2023, at 10:40 AM, Trevor DeVore ***@***.***> wrote:
@martyknapp I got a chance to look at this today and put a PR together that should fix it. If you use the packager script from https://github.com/trevordevore/levure/blob/tkd/issue-207/packager/packager.livecodescript you should be able to test.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
When you try to build a Mac app with both the "macOS Intel" and "macOS Apple" options set in the Standalone settings, it first builds a universal version (successfully). Then it tries to build a "M" only version in the same "macos" folder and aborts when it tries to move the compiled app into that same folder (since there is already an app present). It then never gets to build the Windows version. (Personally I don't need the "M" only version)
Using LC 9.6.9 on Ventura 13.2.1
The text was updated successfully, but these errors were encountered: