Add support to osx-aarch_64

A lot of libraries like Wiremock needs conscrypt to work in a native in the new mac books with m1 chip. In this moment when I execute this library I got this error: Suppressed: java.lang.UnsatisfiedLinkError: no conscrypt_openjdk_jni-osx-aarch_64 in java.library.path please add support to it. Thanks!

[prbprbprb]

I thought this would be straightforward, but it turned out otherwise… Legacy Gradle config in Conscrypt and gaps in Gradle itself, e.g. https://github.com/gradle/gradle/pull/20310 mean it’s taken a big chunk of time.

Anyway, I’ve made enough progress to share for people willing to download and build locally, e.g. @adaladam above

Work in progress is at https://github.com/prbprbprb/conscrypt/tree/m1_gradle - It builds and the tests pass on both Intel and ARM Macs - Each case will build for both architectures but only test the host one. Which also means you need to build BoringSSL for both architectures before you start (I’ll make this a bit more flexible before we finally merge it).

Something like:

cd $BORINGSSL_HOME
mkdir build.arm
cd build.arm
cmake -DCMAKE_POSITION_INDEPENDENT_CODE=TRUE -DCMAKE_BUILD_TYPE=Release -DCMAKE_ASM_FLAGS=-Wa,--noexecstack -DCMAKE_OSX_ARCHITECTURES=arm64 -GNinja ..
ninja
cd ..

mkdir build.x86
cd build.x86
cmake -DCMAKE_POSITION_INDEPENDENT_CODE=TRUE -DCMAKE_BUILD_TYPE=Release -DCMAKE_ASM_FLAGS=-Wa,--noexecstack -DCMAKE_OSX_ARCHITECTURES=x86_64 -GNinja ..
ninja
cd ..

BoringSSL tests for both architectures should pass on MacOS ARM if you have Rosetta. Note that for now the BoringSSL build directory names have to exactly match what’s in the Gradle config (see NativeBuildInfo.libDir() in openjdk/build.gradle)

Once that’s done, ./gradlew check should just work…

This doesn’t solve for Linux/ARM but it lays the groundwork by removing a lot of assumptions that the only differences between targets were x86 and x86_64. Once thing that’s different is that on Linux we can’t assume that x86 hosts can always cross-compile for ARM (and vice versa), as we can on Mac, so it’ll need a bit more smarts about whether to build for the “other” architecture. Or maybe just a flag. I’ll do some more work in that direction but I don’t currently access to a Linux/ARM box for testing. Presumably a VM on an M1 Mac would do.

[svichkar]

I promise to buy MacBook on M1 once it is fixed 🙂