On 09/07/2012 01:43 PM, Robert Dailey wrote: > This is actually a really great idea, but kind of complex (which is > OK, since I already have code to recursively determine target > dependencies). My only concern is that these custom targets will > appear in the solution, when they are really just a stop-gap. I > wouldn't want them to be visible. Any way to hide those custom targets > from appearing in the solution and make sure they are excluded from > the build?
You can group them in the IDE project files: http://www.cmake.org/cmake/help/v2.8.9/cmake.html#prop_tgt:FOLDER > If not, I can use a global property to store each target's > tests, and then only make executable targets depend on those tests. Why bother with a global property? Just add a property to each target to record its own test targets. That information is accessible from other directories. -Brad -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
