Skip to content
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

Android Issues #28

Open
seanh1986 opened this issue May 27, 2019 · 1 comment
Open

Android Issues #28

seanh1986 opened this issue May 27, 2019 · 1 comment

Comments

@seanh1986
Copy link

Hi,

I am trying to integrate boost into an android application for use with the Android NDK. I am trying to integrate boost 1.70.

I have tried two different configurations (both on Android):

Configuration 1
Android Gradle Plugin version: 3.4.1
Gradle version: 5.1.1
CMake version: 3.14.4
Android NDK version: 19.2.5345600

Configuration 2
I upgraded to the latest beta versions of all the above, so 3.5.+, etc.

Both are using Clang compilers. I built the boost library in two different ways... Using the following two repositories:
https://github.com/Orphis/boost-cmake
https://github.com/moritz-wundke/Boost-for-Android

In all cases (both configurations and both build types), I was able to successfully generate the boost files and import them into my project.

The only boost class that I require is boost::circular_buffer (and it's corresponding classes it references).

Basically, boost itself seems to be missing includes that it needs.

In the file boost/circular_buffer/base.hpp, I have the following issues

  • Missing include for details.hpp, otherwise it cannot find "cb_details::const_traits"
  • "BOOST_CB_ASSERT" and ".is_valid( ... )" all seem to be missing imports, etc.

Note: other issues exist in other files, as well. I tried manually adding the 'recommended' imports, but that just caused a chain reaction of missing imports that I couldn't resolve.

I tried using the tagged 1.70 version so I expected it to be stable.

Thanks for your help!

image

@seanh1986
Copy link
Author

Here is another screen shot showing the issue.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant