|
|
I note the OP says the built natively on the M1, and it worked, but it was not clear to me if the fat-binary was created on the M1 ARM, or on the x86_64, or perhaps the two binaries were compiled natively then copied to one host for lips to do its magic?
Some more details: I'm building two standalone application bundles, one on my Intel Mac running Catalina, the other on the ARM Mac. I then copy the binary from the app bundle (xxx.app/Contents/MacOS/) on the ARM Mac to the Intel Mac where I use lipo to create a universal binary as explained before. This universal binary is then placed in the app bundled, replacing the existing Intel binary. I then sign and notarize this app bundle.
Indeed, it would be handy to know if a fat-binary (including an arm M1 binary) can be built entirely on an x86_64 host, since that would go a long way to address the issues that David (w1hkj) is having I imagine.
As my Intel Mac is from 2012 and runs only Catalina, I haven't tried this. It should be possible as XCode 12.2 runs on Catalina, but I don't want to change my working scripts. You know: Never change a running system. :-)
Building on a single system would only save copying and pasting some simple command line commands, so I don't want to mess around with it.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/08c146ca-07c3-4d30-bd46-755465d6d8d7n%40googlegroups.com.
[ Direct Link to Message ] | |
|
| |