You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ ls -d /usr/local/share/android-sdk/ndk/21.3.6528147/sysroot
/usr/local/share/android-sdk/ndk/21.3.6528147/sysroot
$ ls -d /usr/local/share/android-sdk/ndk/22.0.7026061/sysroot
ls: cannot access '/usr/local/share/android-sdk/ndk/22.0.7026061/sysroot': No such file or directory
The sysroot moved to <NDK>/toolchains/llvm/prebuilt/<host-tag>/sysroot starting with NDK r19. r22 removed the deprecated sysroot and platforms directories from the top-level of the NDK.
By using the appropriate driver (e.g. toolchains/llvm/prebuilt/<host-tag>/bin/aarch64-linux-android21-clang), it shouldn't be necessary to do things like pass --sysroot=, include the STL header directories, etc. The driver should handle all that stuff implicitly.
Reacted by Aman Karmani, PARK DongHa, kristafari and tangdaizheng
The changelogs are helpful for things like this :) I know Studio doesn't show them and that's frustrating, but we publish them on our wiki and they always include announcements for things like this.
Activity
rprichard commentedon Dec 24, 2020
The sysroot moved to
<NDK>/toolchains/llvm/prebuilt/<host-tag>/sysrootstarting with NDK r19. r22 removed the deprecatedsysrootandplatformsdirectories from the top-level of the NDK.By using the appropriate driver (e.g.
toolchains/llvm/prebuilt/<host-tag>/bin/aarch64-linux-android21-clang), it shouldn't be necessary to do things like pass--sysroot=, include the STL header directories, etc. The driver should handle all that stuff implicitly.tmm1 commentedon Dec 24, 2020
Thank you for the explanation
DanAlbert commentedon Jan 5, 2021
The changelogs are helpful for things like this :) I know Studio doesn't show them and that's frustrating, but we publish them on our wiki and they always include announcements for things like this.