Filesystem doesn't work on Windows, so we need a mechanism to turn it off for the time being.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
Looks sensible to me, modulo the option description.
CMakeLists.txt | ||
---|---|---|
80 ↗ | (On Diff #191594) | This option text is a bit misleading (there's no separate libc++fs.a any longer if I understand it correctly) now. |
CMakeLists.txt | ||
---|---|---|
80 ↗ | (On Diff #191594) | Woops. Thanks for catching that. |
libcxx/trunk/utils/libcxx/test/config.py | ||
---|---|---|
438 | Instead, I think this should be dependent on the platform. I don't see a reason why this would be different from` dylib-has-no-filesystem`. |
libcxx/trunk/utils/libcxx/test/config.py | ||
---|---|---|
438 | That information is specified at configure time and the build system should respect that choice. I see no value auto-magically detecting it here. If they don't want it to run, they should disable it at configure time. |
libcxx/trunk/utils/libcxx/test/config.py | ||
---|---|---|
438 | The way I see things, the lit test suite is disjoint from the CMake build configuration. When we run the lit test suite, we run it against a concrete release of the standard library (i.e. release by a vendor shipping the library). It just happens to be very convenient to pretend that libc++-as-shipped-with-LLVM is something that makes sense to test against because it gives us a sane workflow. This is why I'd rather not use switches to turn this-or-that on/off, but instead have the test suite know about various implementation characteristics and work with that. In other words, instead of saying c++filesystem-disabled, just don't build filesystem into the dylib, and then have a way of telling the test suite that the library you're testing (libc++ trunk without filesystem support) has no support for filesystem. |
Eric and I spoke and we agreed on a way to handle disabling subparts of the test suite.
Instead, I think this should be dependent on the platform. I don't see a reason why this would be different from` dylib-has-no-filesystem`.