-
Notifications
You must be signed in to change notification settings - Fork 25
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
Try to create arm prebuilds #96
Conversation
Well this is tedious - https://boringssl.googlesource.com/boringssl/+/546093ca4a6b2bf9b7c29018687d53f8a2ad428a/CMakeLists.txt#300 In the olden times (e.g. during the ppc -> intel switch) you'd use a tool called lipo to make a universal binary from a ppc and an intel build. If boringssl only supports building one arch at a time that might be necessary? |
Well, I have a problem, the lines did not turn cmake into multi-arch. So if boring does not support it anyway, I should cross-compile..., ok, I try again..... (sadly I did not find if one can access the arm GitHub runner beta test) |
Ok so Certainly if I build this module locally I can create a universal binary from the arm64 version $ lipo -create webtransport_arm.node webtransport_x64.node -output webtransport.node
$ file webtransport.node
webtransport.node: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64Mach-O 64-bit dynamically linked shared library x86_64] [arm64]
webtransport.node (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
webtransport.node (for architecture arm64): Mach-O 64-bit dynamically linked shared library arm64 The universal binary works for running the tests in this module (previously needing an |
I try now if I can cross-compile, but than we will have separate binaries. |
Should work now... |
No description provided.