OSX Archive : Apple Silicon builds

[IcemarkUK]

First time uploading all the versions of my app to all the stores tonight, since the Axmol upgrade.

All seem to have gone through the process generally without hitch.

One issue I found when creating the archive for OSX.
I got this warning about architectures.

When I attempted to update and build, it added Apple Silicon as an architecture target, but the app wouldn't build. Looks like there is some ASM in the astcenc_mathlib that is not compatible. Or maybe pragmas not correct to change includes etc.

[rh101]

If that popup appears, it means you would need to deal with the issue in cmake, otherwise clicking "Update and Build" means Xcode is going to mess with the project. Ideally, the Xcode project needs to be correct at the time it is generated by cmake, so there should never be a need to modify things manually through the IDE.

Try passing the required architectures like this when generating the Xcode project files:
axmol build -p osx -a 'arm64;x64' -c
Never mind, the above doesn't work for OSX.

Passing -DCMAKE_OSX_ARCHITECTURES=$(ARCHS_STANDARD) works to set all the build targets to the correct setting:

So, pass it like this:
axmol build -p osx -a arm64 -c -f -xc '-DCMAKE_OSX_ARCHITECTURES=$(ARCHS_STANDARD)'

The problem now is that it's been configured for arm64 on the command line via the -a arm64, but I'm not sure how to get around that. It results in this issue (which is similar to what you posted above):

@halx99 is there a way to have this set correctly at build time, when Xcode is compiling for arm64 then x64_86? Something similar to how it is handled for Android.

[IcemarkUK]

No joy. Never mind I've got used to setting it.

Out of interest, here is the part in the Xcode project that is being changed.

   <ArchiveAction
      buildConfiguration = "RelWithDebInfo"
      customArchiveName = "The Lords of Midnight"
      revealArchiveInOrganizer = "YES">
   </ArchiveAction>

[rh101]

The build configuration must be set via the IDE, since you're in control which type of build you need.

I'd really like to find out if the customArchiveName can be set somewhere, and I still think there is a way. Are you certain none of these work:

set(PRODUCT_NAME "The Lords of Midnight")
set(BUNDLE_BUNDLE_NAME "The Lords of Midnight")

From what I can remember, the archive file name is sourced from the CFBundleName field of the Info.plist, and the CFBundleName can be set via CMake. I'm going to test this out when I have a bit of time.

[IcemarkUK]

No, neither of them. Just tried. But I already have CFBundleName and CFBundleDisplayName set in my Info.plist

[rh101]

No, neither of them. Just tried. But I already have CFBundleName and CFBundleDisplayName set in my Info.plist

Thanks for testing it.

If I ever do figure it out, I'll make sure to post it here.

[IcemarkUK]

Thanks for looking... :)

TBF. Some of the things we can now do with cmake, I'm not sure we could do even 6 years ago when I moved my project from Marmalade to Cocos2dx. 12 years my games have now been available on the stores... and things have changed... :)