Skip to content
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

Apple m1 support (processor / SoCs) #92

Open
raphaelguye opened this issue Jun 7, 2023 · 4 comments
Open

Apple m1 support (processor / SoCs) #92

raphaelguye opened this issue Jun 7, 2023 · 4 comments

Comments

@raphaelguye
Copy link

Currently, the MAM SDK seems to not becompatible for the Apple m* processor (like the m1).
The main difference with between m1 and intel is that the m1 is an ARM based processor. It means that the simulator needs also an app built for the arm64 architecture, instead of x86_64.

Using Bitrise, we get the following errors when trying to build on an m1 stack:

[00:51:19]: ▸ Linking MyApp
[00:51:19]: ▸ ⚠️ ld: directory not found for option '-F/Users/vagrant/git/MyApp/Carthage/Build/'
[00:51:19]: ▸ ⚠️ ld: ignoring file /Users/vagrant/Library/Developer/Xcode/DerivedData/MyApp-ffivjnulvvpxqygojsdjcsrfyqwu/Build/Products/Debug (Dev)-iphonesimulator/CTXMAMCore.framework/CTXMAMCore, building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64
[00:51:19]: ▸ ⚠️ ld: ignoring file /Users/vagrant/Library/Developer/Xcode/DerivedData/MyApp-ffivjnulvvpxqygojsdjcsrfyqwu/Build/Products/Debug (Dev)-iphonesimulator/CTXMAMCompliance.framework/CTXMAMCompliance, building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64
[00:51:19]: ▸ ⚠️ ld: ignoring file /Users/vagrant/Library/Developer/Xcode/DerivedData/MyApp-ffivjnulvvpxqygojsdjcsrfyqwu/Build/Products/Debug (Dev)-iphonesimulator/CTXMAMContainment.framework/CTXMAMContainment, building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64
[00:51:19]: ▸ ⚠️ ld: ignoring file /Users/vagrant/Library/Developer/Xcode/DerivedData/MyApp-ffivjnulvvpxqygojsdjcsrfyqwu/Build/Products/Debug (Dev)-iphonesimulator/CTXMAMNetwork.framework/CTXMAMNetwork, building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64
[00:51:19]: ▸ ⚠️ ld: ignoring file /Users/vagrant/Library/Developer/Xcode/DerivedData/MyApp-ffivjnulvvpxqygojsdjcsrfyqwu/Build/Products/Debug (Dev)-iphonesimulator/CTXMAMAppCore.framework/CTXMAMAppCore, building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64
[00:51:19]: ▸ ⚠️ ld: ignoring file /Users/vagrant/Library/Developer/Xcode/DerivedData/MyApp-ffivjnulvvpxqygojsdjcsrfyqwu/Build/Products/Debug (Dev)-iphonesimulator/CitrixLogger.framework/CitrixLogger, building for iOS Simulator-arm64 but attempting to link with file built for iOS Simulator-x86_64
[00:51:19]: ▸ ❌ Undefined symbols for architecture arm64
[00:51:19]: ▸ > Symbol: OBJC_CLASS$_CTXMAMCore
[00:51:19]: ▸ > Referenced from: objc-class-ref in AppDelegate.o
[00:51:19]: ▸ ❌ ld: symbol(s) not found for architecture arm64
[00:51:19]: ▸ ❌ clang: error: linker command failed with exit code 1 (use -v to see invocation)

Can you tell me if we miss something and if there is already a version compatible with the m1?
Otherwise, can you communicate us your plan regarding this question?

@makunterry
Copy link
Collaborator

@raphaelguye
Thanks for your question. We will work on this soon, and we need to resolve some dependency issue here before we can provide ios-arm64-simulator framework.

@bryanrmq
Copy link

@makunterry May I ask for a timeframe ?
We have some clients which depends on this issue and they are asking for a status check on this.

@makunterry
Copy link
Collaborator

@bryanrmq
Sorry we don't have a clear time frame for this work.

@F1nn-T
Copy link

F1nn-T commented Jan 24, 2024

@makunterry
Any updates on this topic? I also need ARM support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants