-
Notifications
You must be signed in to change notification settings - Fork 13
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
Test executable fails to build #1
Comments
Thanks @loganblevins,
Are you using Crypto++ Master? Or a release version? |
@noloader Building with 8.1 release and following your build instructions with ndk-build as close as possible. |
OK, thanks. That's due to cryptopp-android following Crypto++ Master. We'll add cryptopp-android release zip files with the next library release. (Prior to last week, the Android build was broken so there was no sense in releasing). Go to
If you switch to Crypto++ Master, then you will get about a 30% speedup in (The last commit to this repo, Commit 8b7b93b1773b, was the one the cut-over from 32-bit to 64-bit). |
Thank you for your prompt help - really appreciate it. I had used your zip file on this release: https://github.com/noloader/cryptopp-android/tree/CRYPTOPP_8_1_0 coupled with cryptocpp 8.1 release thinking they'd work hand-in-hand but did not. Was that incorrect thinking? |
Alas, it seems the suggestion got me past my prior stumbling block on arm64 yet now have an integer problem on x86_64. I'm happy to switch to 8.2 or even
|
I think Crypto++ 8.1 has the old monolithic You may need this in your
I also added a section on the wiki at Android.mk | Problems. But I've got a feeling it is like trying to put out a fire with a wet sponge. |
Here's a script that will build Crypto++ 8.2 for Android... Redacted. See the Comment 546494926. |
I have yet to try a new version. Prior we depended on 5.6.5 and after experiencing a mysterious, uncaught runtime exception on 8.1, we moved back to the original 5.6.5 for now. Thought it would be a problem to build 5.6.5 on NDK 20 though did have success on all but x86_64. |
You were right. From a policies and procedures point of view we need to supply something that builds against a release zip. I added a I'm deleting the manual procedure a few comments up. Thanks for pointing that out. |
Thank you for ongoing help - really appreciate it. |
Example:
Using NDK 20 on macOS 10.14.6
The text was updated successfully, but these errors were encountered: