On Wed, Jul 2, 2008 at 4:38 PM, Doug Gregor wrote: > On Wed, Jul 2, 2008 at 4:31 PM, Miguel A. Figueroa-Villanueva wrote: >> On Wed, Jul 2, 2008 at 2:06 PM, David Abrahams wrote: >>> troy d. straszheim wrote: >>>> and those HEADERS from each library will get moved from toplevel boost/ >>>> to each library's libs/*/include/boost directory. This currently >>>> requires 'rsync' and 'rm' presumably working only unixy platforms, >>>> which should be fine, there's nothing about this that needs extensive >>>> special testing on windows. Who knows, maybe under cygwin it would work. >>> >>> I'm certain that it would; cygwin is POSIX. >>> Could you use something like python's shutil.copytree or >>> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/231501 to do >>> this portably? >> >> cmake can handle this cross-platform... if you type 'cmake -E' it will >> give a list of commands that it can support. Notice: remove, >> remove_directory, make_directory, and copy_directory. Through custom >> commands it can be made to work in all platforms. > > Ah, so this would be done at configuration time, then? I could imagine > toggling a "BOOST_AUTO_MODULARIZE" option within the CMake GUI, and > having the next "Configure" run do all of the directory-shifting.
It can do it both at configure or with a make target. If you use something like: "execute_process(cmake -E copy_directory ....)" it will be run at configure time. With something like: "add_custom_target(modularize cmake -E copy_directory ...)" then it can be run at run-time as "make modularize" or through the IDE. --Miguel _______________________________________________ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
