On 07.03.2018 17:15, Nathan Froyd wrote:
FWIW, the Android team is planning on making standalone toolchains
obsolete in the relatively near future (the roadmap says later this
year):
https://android.googlesource.com/platform/ndk/+/master/docs/Roadmap.md#make-standalone-toolchains-obsolete
FWIW, the Android team is planning on making standalone toolchains
obsolete in the relatively near future (the roadmap says later this
year):
https://android.googlesource.com/platform/ndk/+/master/docs/Roadmap.md#make-standalone-toolchains-obsolete
-Nathan
On Tue, Mar 6, 2018 at 7:46 PM, Josh
The standalone NDK's problem is that we moved to use the same C++ standard
library as Firefox in order to match SM when Gecko made the move.
Unfortunately, the make-standalone-toolchain.sh script was broken for years
for anything apart from the default C++ standard library (it would either
just
We talked a bit about standalone NDKs when we worked on adding support for
new android CPU architectures here:
https://github.com/servo/servo/issues/11921#issuecomment-299052122
The benefit of using a standalone NDK is that we have to configure less CXX
flags in Servo. But the main concerns are
We used to use a standalone toolchain:
https://github.com/servo/servo/wiki/Building-for-Android/16f371c68d7da393d178646dcb18dac2c2ea8826
but this changed back in 2016; I'm not clear on the exact reasons:
https://github.com/servo/servo/pull/13945
On Tue, Mar 6, 2018 at 4:46 PM, Josh
5 matches
Mail list logo
