-
Notifications
You must be signed in to change notification settings - Fork 263
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
How to build without using standalone toolchain? #773
Comments
the key point is "deprecate or remove standalone toolchains by making every toolchain a standalone toolchain". you shouldn't be doing any prep work yet, because there's no new thing to move to yet. right now, you're doing it right if you're using a standalone toolchain. r18 will remove stlport and gnustl, so there will no longer be any need to specify an STL. (i'll update the docs to reflect that when r18 ships.) the API level is the only thing that remains, and that will be part of the triple. |
(i'll leave this open for now, since our wording has definitely caused some confusion.) |
Ah, ok I misunderstood. Thank you for clarifying. I thought that we were expected to somehow use the existing NDK structure as a replacement for standalone, but that's not the case. |
FYI, I also have no plans of getting rid of the standalone toolchain script. The only difference there is that it will essentially just be an overly complicated |
To build boost i use pure ndk with b2 ./b2 $jobs toolset=clang-aarch64 target-os=android link=static runtime-link=static variant=release optimization=speed ..[other options].. install using clang : aarch64 : clang++ : |
Sorry to ask here, I also like standalone toolchains because they are just easier to use when building external libraries that are autotools based. Using them you don't have to pass dozens of parameters. So it is safe to continue relying on it for the future? |
we're just making every toolchain a standalone toolchain. r18 removed stlport and gnustl, so there's no need to specify an STL. the API level is now part of the triple. r19 moves most compiler/linker flags into the driver (the there are no plans to remove the standalone toolchain script. the only difference is that it will essentially just be an overly complicated cp. standalone toolchains are not "going away" so much as "going everywhere". |
It's mentioned in the roadmap for NDK that r19 or r20 (I forget which one) will deprecate or remove standalone toolchains. However, I do not see a guide anywhere today that shows how to build libraries against the NDK toolchains without using the standalone toolchains. There's a very good writeup on how to use the toolchain, but not one for without that I could find.
Basically if I build the Boost library, I can probably point
--sysroot
to thesysroot
directory at the root, but I'm not sure how to do things like specify the STL to use, or specify the minimum API level. Does such a guide already exist? And if not, could this task serve as a request for such a guide?The text was updated successfully, but these errors were encountered: