Run the installer, including accepting the license, selecting the destination, and authenticating for the install. Download Node.js for macOS by clicking the 'Macintosh Installer' option. Also, please don't count on me to solve all of these problems, I don't really have time to be doing any of this and was really just checking to see how far off we might be - this all suggests that the answer is "quite a way off, and it will require coordinated effort across subsystems to make this happy". Here's the abbreviated guide, highlighting the major steps: Go to the Node.js Downloads page. configure because icupkg breaks the build - this is an expected part of cross compiling, we probably need a system ICU installed to make this work (although this isn't a great option for release machines where we want to push the ICU version with the source so we might need to figure out how to first compile it for 圆4 then use that binary to run against the arm64 build).īut my latest failure is V8 related: OSError: Bad CPU type in executable: '/Users/rvagg/git/iojs/io.js/out/Release/bytecode_builtins_list_generator'. Manually added 'SDKROOT': '/Library/Developer/CommandLineTools/SDKs/MacOSX11.0.sdk/' to my common.gypi in the 'target_arch="arm64"' section for the "mac" block (without this it keeps on defaulting to my system SDK, I assume if we built on the latest OS this would default to the right directory).Installed Xcode 12 beta which I believe is the only way to get this to work (I could be corrected on this, the fact that it's still beta has me confused about this point).Here's some things I've tinkered with so far on my 圆4 mac: This second piece is still the right way as far as I understand, the problem is the -dest-cpu=arm64 bit. we could do a -dest-cpu=ia32 build and a -dest-cpu=圆4 build and smush the resulting node binaries together with lipo. Here's how we used to make fat binaries: ![]() here's the key piece that someone needs to figure out - how do we get our toolchain to compile arm64 macos binaries on 圆4?
0 Comments
Leave a Reply. |