Update build for macos M1 (#77)
This commit is contained in:
@@ -27,7 +27,9 @@ You must edit `secp256k1-kmp-staging-upload.sh` and add your sonatype credential
|
||||
## Adding custom JNI bindings
|
||||
|
||||
Github CI currently generates JNI bindings for Windows x64, Linux x64 and iOS x64. But it is possible to add custom bindings to JNI packages before
|
||||
they are published to maven central. This is how we add linux arm64 bindings:
|
||||
they are published to maven central.
|
||||
|
||||
This is how we add linux arm64 bindings:
|
||||
- compile JNI bindings for Linux Arm64 (on a Linux Arm64 machine, cross-compilation is not supported)
|
||||
- git clone --recursive https://github.com/ACINQ/secp256k1-kmp.git
|
||||
- cd secp256k1-kmp
|
||||
@@ -37,6 +39,19 @@ they are published to maven central. This is how we add linux arm64 bindings:
|
||||
- JNI library is: jni/jvm/build/linux/libsecp256k1-jni.so
|
||||
- copy libsecp256k1-jni.so to fr/acinq/secp256k1/jni/native/linux-aarch64/libsecp256k1-jni.so
|
||||
- run `secp256k1-kmp-add-linuxarm64.sh` and specify either `release` or `snapshot` and the `VERSION` environment variable, for example:
|
||||
- VERSION=0.6.4-SNAPSHOT ./secp256k1-kmp-add-linuxarm64.sh snapshot
|
||||
- VERSION=0.6.3 ./secp256k1-kmp-add-linuxarm64.sh release
|
||||
- VERSION=0.9.0-SNAPSHOT ./secp256k1-kmp-add-linuxarm64.sh snapshot
|
||||
- VERSION=0.9.0 ./secp256k1-kmp-add-linuxarm64.sh release
|
||||
|
||||
This is how we add macos arm64 (M1/M2) bindings:
|
||||
- compile JNI bindings for macos Arm64 (on a macos Arm64 machine, cross-compilation is not supported)
|
||||
- git clone --recursive https://github.com/ACINQ/secp256k1-kmp.git
|
||||
- cd secp256k1-kmp
|
||||
- TARGET=darwin ./native/build.sh
|
||||
- mkdir -p jni/jvm/build/darwin
|
||||
- TARGET=darwin ./jni/jvm/build.sh
|
||||
- JNI library is: jni/jvm/build/darwin/libsecp256k1-jni.dylib
|
||||
- copy libsecp256k1-jni.dylib to fr/acinq/secp256k1/jni/native/darwin-aarch64/libsecp256k1-jni.dylib
|
||||
- run `secp256k1-kmp-add-darwinaarch64.sh` and specify either `release` or `snapshot` and the `VERSION` environment variable, for example:
|
||||
- VERSION=0.9.0-SNAPSHOT ./secp256k1-kmp-add-darwinaarch64.sh snapshot
|
||||
- VERSION=0.9.0 ./secp256k1-kmp-add-darwinaarch64.sh release
|
||||
|
||||
|
||||
17
publishing/secp256k1-kmp-add-darwinaarch64.sh
Executable file
17
publishing/secp256k1-kmp-add-darwinaarch64.sh
Executable file
@@ -0,0 +1,17 @@
|
||||
#!/bin/bash -x
|
||||
|
||||
if [ $# -eq 0 ]
|
||||
then
|
||||
echo "specify either snapshot or release"
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# add aarch64 (ARM64) library to the darwin jar
|
||||
if [ -e fr/acinq/secp256k1/jni/native/darwin-aarch64/libsecp256k1-jni.dylib ]
|
||||
then
|
||||
jar -uf $1/fr/acinq/secp256k1/secp256k1-kmp-jni-jvm-darwin/$VERSION/secp256k1-kmp-jni-jvm-darwin-$VERSION.jar fr || exit
|
||||
else
|
||||
libsecp256k1-jni.dylib for arch64 is missing
|
||||
exit 1
|
||||
fi
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
GROUP_ID=fr.acinq.secp256k1
|
||||
ARTIFACT_ID_BASE=secp256k1-kmp
|
||||
VERSION=0.6.3-SNAPSHOT
|
||||
VERSION=0.9.0-SNAPSHOT
|
||||
|
||||
cd snapshot
|
||||
pushd .
|
||||
|
||||
Reference in New Issue
Block a user