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
Cross-compiling for android does not work anymore on OpenSUSE and Travis CI #59
Comments
Yes. In fact, I had finished an Android and an iOS cross-compile about 2 hours before you posted (It was literally 2 or hours or so).
Ah, OK. All the cross-compile stuff has been added to the library. There's no need to apply the patch. All you need are: You can find Here is the 10 second tour:
Or:
And here is what it looks like:
No, but I believe they exist. The root cause is our documentation is stale. I think we should leave this open until we update the docs.
I believe this is because the setup is bent. I did not experience it when using the |
By the way, I'm happy to work directly with package maintainers. I view this as a partnership between us. If the maintainer has any questions, then ask them to reach out to me directly. If OpenSUSE needs an accommodation, then they need to reach out to us quickly. We want to release 5.6.3 soon. We effectively performed the pre-release check-in yesterday. Once we release, we won't be able to get changes into 5.6.3 for them (if they want or need something). |
Thank you for your help. I used the GNUmakefile-cross, which is already in the repository. The compiling then worked. The third error, i.e.
still is present. But this is, when we build our library. So this has only indirectly to do with cryptopp. I will have a look at this next week and inform you about the progress. To prevent misunderstandings: I am not a package maintainer. The OS names in the title of this issue were just there to inform you about the platforms we are building cryptopp on. |
OK, thanks. I'm going to close this report to keep things tidy. For completeness, we cannot duplicate it (see below).
...
My guess is a compiler is pretending to be C++11 (or it is and it does not have the feature yet). We have to jump through some hoops on Apple platforms because Apple supplies compilers that pretend to be C++11. See the comments in If its still a problem for you, then please (1) open another bug report for the SecBlock issue, (2) tell us about the toolchain you are using, and (3) tell us how to duplicate it. |
@eriknellessen - we performed a complete overhaul of the Android docs. Please let me know what you think, or if you ave any troubles. |
Cross-compiling produced many errors today on OpenSUSE 13.1 and Travis CI (Ubuntu 12.40).
We used to follow the procedure described in http://www.cryptopp.com/wiki/Android_%28Command_Line%29 . That means, we downloaded the patched files and then built cryptopp for android. This still worked 7 days ago. With the new commits today, this does not work anymore.
I believe that this is because of the many changes in the new commits. We tried to apply the patch (from the wiki) to a fresh copy of cryptopp, but patch failed:
We then had a look at the new GNUmakefile and saw, that it already has built-in many features of the patch. So we tried to just use that GNUmakefile for cross-compiling for android. That did not work with the following error message:
So we changed the GNUmakefile and just commented out the line CXXFLAGS += -march=native (dirty). Cryptopp then compiled, but when we built our library depending on cryptopp, we encountered the following error:
Did you already test cross-compiling for android? Can you reproduce the problems?
The text was updated successfully, but these errors were encountered: