I have to apologise again, my previous issue where compiling the Android libraries on Linux was failing due to some libraries being placed in a "lib64" path turned out to be distro-dependent. On some distros the files get placed into a "lib" path as was initially expected by the library. Due to this I reverted my previous changes and added a workaround using symlinks to make sure that if secp256k1 gets placed in a "lib64" path it will symlink to "lib" so CMake will always find it. Without directly integrating secp256k1 into CMake I don't think there's a better solution to this awkward problem.
giahuy98
commented
9 months ago
I have to apologise again, my previous issue where compiling the Android libraries on Linux was failing due to some libraries being placed in a "lib64" path turned out to be distro-dependent. On some distros the files get placed into a "lib" path as was initially expected by the library. Due to this I reverted my previous changes and added a workaround using symlinks to make sure that if secp256k1 gets placed in a "lib64" path it will symlink to "lib" so CMake will always find it. Without directly integrating secp256k1 into CMake I don't think there's a better solution to this awkward problem.
You can see I have the library building on Mac and Ubuntu via GitHub Actions: https://github.com/PeteClubSeven/cktap-protocol-flutter/actions/runs/7160231009