-
Notifications
You must be signed in to change notification settings - Fork 73
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
broke compilation of nodejs-mobile for iOS from a x64 macBook #184
Labels
Comments
gengjiawen
changed the title
TL;DR this commit broke compilation of [nodejs-mobile](https://github.com/nodejs-mobile/nodejs-mobile) for iOS from an x64 macBoo
broke compilation of [nodejs-mobile](https://github.com/nodejs-mobile/nodejs-mobile) for iOS from an x64 macBoo
Jan 10, 2023
ryzokuken
changed the title
broke compilation of [nodejs-mobile](https://github.com/nodejs-mobile/nodejs-mobile) for iOS from an x64 macBoo
broke compilation of nodejs-mobile for iOS from an x64 macBook
Jan 10, 2023
ryzokuken
changed the title
broke compilation of nodejs-mobile for iOS from an x64 macBook
broke compilation of nodejs-mobile for iOS from a x64 macBook
Jan 10, 2023
Similar issue building on a x64 macBook using "nodejs-mobile-react-native": "16.17.4" for an iPhone simulator (iOS target 15). I'm using node version v16.15.1 . So I can't run "nodejs-mobile-react-native" on an iOS simulator.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR this commit broke compilation of nodejs-mobile for iOS from an x64 macBook. See PR nodejs-mobile/nodejs-mobile#9
(I'm not sure if it's good practice to comment on old PRs, so feel free to tell me to move this discussion elsewhere.)
I maintain nodejs-mobile lately, and I'm updating our fork from Node 12.x to Node 16.x. Since we're compiling node.js for iOS, we want the
arch
to bearm64
, but the host clang has flags like__amd64__
and this mixed with the iPhoneOS SDK headers ends up causing anUnsupported architecture
compilation error.Maybe a solution would be to patch this gyp-next script to detect whether we're running in arm64 darwin (such checks are common throughout the codebase, I've noticed) and then use the new logic. Else, use the old logic.
What do you think?
Originally posted by @staltz in #78 (comment)
The text was updated successfully, but these errors were encountered: