-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add boringssl #8
Comments
I have submitted a build fix for EDIT: The fix is now merged in google/boringssl@d3ec6f1 |
Ping @marijnvdwerf |
Note to self: jansson fails due to the script executing An invocation like
gets it going a bit further, but then fails on
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This adds boringssl to all architectures.
I couldn't rebuild all the libraries, it failed on my system, so libpng and sdl2 are still outdated.
With this and OpenRCT2/OpenRCT2#6760 I could connect to a multiplayer server:
I had to manually copy the key from my desktop, as OpenRCT2 crashed with the one generated on device, as it had 0 bytes.
It crashed on this line:
https://github.com/OpenRCT2/OpenRCT2/blob/33d0fa9b8c506c6d56777df940fbb2228268d9aa/src/openrct2/network/NetworkKey.cpp#L315
The stack trace was:
The build command:
The built libs use google/boringssl@bc37ad9
The binaries in question:
openrct2-libs-android-arm64-v8a.zip
openrct2-libs-android-armeabi-v7a.zip
openrct2-libs-android-x86.zip
openrct2-libs-android-x86_64.zip
The text was updated successfully, but these errors were encountered: