qertsticky.blogg.se - Android ndk r14bx86

#Android ndk r14bx86 full
#Android ndk r14bx86 android

It is comparable to boost::filesystem in that it is using its own namespace and so its not the same as std::, but it differs from boost::filesystem in that it pretends to be std::filesystem in questions of api and behavior.

These comments have been a few weeks ago, but I just found this discussion and want to add a small detail to the suggested workaround implementation in case someone might think about it:

#Android ndk r14bx86 android

Yes the current implementation is irritating - either don't include it at all, or include it so it links!Īs mentioned further up, there is a workable Android alternative which I am using and haven't had any issues with at If I am reading docs right, this is equivalent of using boost::filesystem, right? It doesn't pretend to be std::? It'd be better to get them fixed if we can, but I don't think we need to hold back the feature for them. It's going to take me some time to get the test fixes pushed upstream, but if that takes too long I don't think we need to wait for that before shipping it in r22 beta 1.Īs for the two bugs, I don't think those are severe enough that we necessarily need to fix them before shipping.

Ability to set the permissions of a symlink is inconsistent (see fchmodat with AT_SYMLINK_NOFOLLOW is very inconsistent #1258).

no types of special files ( mknod, named fifos, unix domain sockets, etc) are allowed (at least in /data/local/tmp for the shell user).

hardlinks aren't allowed (at least in /data/local/tmp for the shell user).

There are a fair number of other things that don't work, most of which depend on API level, but they are all related to Android security policy and std::filesystem signals the error appropriately:

realpath doesn't fail on non-existent paths on old devices #1260 std::filesystem::canonical will incorrectly succeed for non-existent paths on devices older than API ~19 (not sure exactly when).

fchmodat with AT_SYMLINK_NOFOLLOW is very inconsistent #1258 std::filesystem::permissions(symlink_path, p perms, std::filesystem::perm_options::nofollow) will not honor nofollow for devices older than API 23.

Tests did uncover two bugs, but they're relatively minor: Everything looks good within a reasonable margin of error.

#Android ndk r14bx86 full

If you're seeing different behavior then open a bug.Alright, managed to get a full test run on Jelly Bean. usr/local/google/home/danalbert/src/ndk/out/linux/android-ndk-r20-canary/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ -target=armv7-none-linux-androideabi16 -gcc-toolchain=/usr/local/google/home/danalbert/src/ndk/out/linux/android-ndk-r20-canary/toolchains/llvm/prebuilt/linux-x86_64 -sysroot /usr/local/google/home/danalbert/src/ndk/out/linux/android-ndk-r20-canary/toolchains/llvm/prebuilt/linux-x86_64/sysroot -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -mfpu=vfpv3-d16 -mthumb -Wa,-noexecstack -Wformat -Werror=format-security -stdlib=libc++ -std=c++11 -fPIE - std=gnu++14 -MD -MT CMakeFiles/foo.dir/ -MF CMakeFiles/foo.dir/.d -o CMakeFiles/foo.dir/ -c /usr/local/google/home/danalbert/src/ndk/ndk/foo/foo.cpp The compilation command when built (note the order of the two -std flags):