OpenMP is now available as a dynamic library (and this is the new default behavior, so link with -static-openmp if you want to stick with the static runtime).Ī handful of driver improvements have been made to reduce the amount of compiler configuration required by each build system as well. This includes fixes for quite a few bugs in the previous release, perhaps most importantly LLD no longer hangs when using multithreaded linking on Windows. The toolchain has been updated to r365631 (the master branch as of 10 July 2019). GDB has been updated to version 8.3, which includes fixes for debugging modern Intel CPUs.Īs always, we’ve updated LLVM and all of its components (Clang, lld, libc++, etc) which includes many improvements. This also includes a number of bug fixes, including fixing the pesky CreateProcess errors on Windows. This is enabled by default with ndk-build. We’ve updated GNU Make to version 4.2, which enables -output-sync to avoid interleaving output with error messages. There are quite a lot of new things in this release, resolving bugs and helping you write better, safer code.
More detail, including the criteria we will use to determine what will be backported, what kinds of bugs will trigger a point release, and the bar we hold each release to can be found documented on our GitHub Wiki. If you want the latest features from Clang and libc++, this is the release for you. These will be approximately quarterly releases of our latest set of features, which will only be patched later for critical toolchain fixes. The non-LTS releases each year, which we call the “rolling” release, will be similar to our current process. Generally releasing in Q4, our first LTS release will be NDK r21. The release will undergo a longer beta cycle before being released, and will receive bug fixes as backports until next year’s LTS release. One release a year will be our Long Term Support (LTS) release for users that want stability more than they need new features. Linux users must have glibc 2.17 or newer. While this change will not affect most developers, this change does have an impact if you use 32-bit versions of Microsoft® Windows®.
ANDROID NDK TOOLCHAIN ANDROID
Following Android Studio and the SDK, 32-bit Windows is no longer supported. This release comes with new minimum system requirements. We have the usual toolchain updates, improved defaults for better security and performance, and are making changes to our release process to better accommodate users that need stability without hindering those that want new features. Posted by Dan Albert, Android NDK Tech LeadĪndroid NDK r21 is now in beta! It’s been a longer than usual development cycle (four months since NDK r20), so there’s quite a lot to discuss for this release.
0 kommentar(er)
