To add to my post, to use (or build) filesystem, you need at minimum the following Boost modules: assert config core detail functional io iterator mpl predef preprocessor range smart_ptr static_assert system throw_exception type_traits -----Original Message----- From: Peter Dimov Sent: Tuesday, September 27, 2016 23:41 To: boost@lists.boost.org Subject: Re: [boost] CMake Modularization Philip Woods wrote:
I created an example project https://github.com/Elzair/cmake-boost-filesystem-test to demonstrate my ideas. I added CMake build support to the minimum number of modules needed to support this demo: https://github.com/Elzair/assert https://github.com/Elzair/config https://github.com/Elzair/core https://github.com/Elzair/filesystem/tree/master and https://github.com/Elzair/system
A few questions come to mind... why is filesystem on master and the others
on develop?
In filesystem/CMakeLists.txt, shouldn't
set(BOOST_SYSTEM_INCLUDE_DIRS "${CMAKE_CURRENT_SOURCE_DIR}/include" CACHE
STRING "Location of boost.system headers")
refer to FILESYSTEM instead?
As far as I can see libs/CMakeLists.txt requires the add_subdirectory calls
to be properly ordered. Isn't this inconvenient? I suppose it's fine for
this case where there are only five lines, but not all libraries are like
that.
Why does the Filesystem CMakeLists.txt file require C++11?
Does this actually work? When I do 'make' I get
D:/tmp/cmake-boost-filesystem-test/test.cpp:3:32: fatal error:
boost/filesystem.hpp: No such file or directory
#include