On Wednesday 07 April 2010 10:37:54 pm Michael Wild wrote: > On 8. Apr, 2010, at 3:39 , Ryan Pavlik wrote: > > You might consider just setting the EXCLUDE_FROM_ALL property on specific > > targets, instead of an entire subdirectory. > > > > Ryan > > > > On Wed, Apr 7, 2010 at 8:33 PM, Daniel Nelson <tor...@connect2.com> wrote: > >> If I use add_subdirectory with the EXCLUDE_FROM_ALL option, then any > >> files whose install commands are in that directory are not installed as > >> part of 'make install'. Is this on purpose, and if so is there a way I > >> can install these files? > >> -- > >> Daniel > > Also there is the OPTIONAL argument to the INSTALL command which might be > of help here. > > > Michael >
This is probably a pretty good workaround, but it's not ideal because I have several projects that add this directory, and I only want it to be excluded for some of them. So I'll end up needing to use a variable in the parent directory to control the EXCLUDE_FROM_ALL property. Then I need to use the OPTIONAL argument to prevent errors if I haven't built the directory, which means I won't be notified if a file is missing. What I'd really like to be able to do, is add new targets, and then manually set them to depend on whichever install commands I want. Then I could just run: make install/my_exclude_from_all_project. But it seems that the install commands are outside of the target system. -- Daniel _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
