Re: [dev-servo] Standalone NDK concerns?

2018-03-07 Thread Imanol Fernández
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

Re: [dev-servo] Standalone NDK concerns?

2018-03-07 Thread Josh Bowman-Matthews
On 3/7/18 6:04 AM, Imanol Fernández wrote: 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

Re: [dev-servo] Standalone NDK concerns?

2018-03-07 Thread Nathan Froyd
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

Re: [dev-servo] Standalone NDK concerns?

2018-03-07 Thread Lars Bergstrom
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