Yuyi Wang
Well, I somehow suspect that. Anyway it worth a try. I will split tar-parser out when I am free and will inform the prgress here.
`tar-parser` is published: https://crates.io/crates/tar-parser2 `vfs-tar` is also updated to use it: https://crates.io/crates/vfs-tar
It's a usage be like hot patching. One main file system with other patch file system. With my another issue tar support, we can patch one tar file with other...
I modified the generated project and removed armv7 arch. It is resolved temporarily.
I've installed a new NDK and could still reproduce that. However I've found it an NDK issue. I've opened one for NDK: https://github.com/android/ndk/issues/1856
I choose to modify NDK following this comment: https://github.com/android/ndk/issues/1856#issuecomment-1542248775
If you want UTF-8, simply use function `std::filesystem::u8path`. If you also need C++20, use `char8_t` overloads. If you want UTF-8 with `char` and C++20, disable `char8_t` by `/Zc:char8_t-` after `/std:c++latest`,...
> However developers will forget and often we will find that out after the release... C++ is not a language that will avoid developers' mistake, and also it *should not*...
> How exactly does Boost.Filesystem prevent such conversions? As far as I know, there's a method `imbue` to change the locale of path class, which could be used for casting...
Well, if you don't need other code pages, don't want to change or review codes, and need `filesystem` on all platforms, I suggest you still using `boost::filesystem`. Or do another...