get_target_properties() with the property SOURCES then for each value you get back there, do a get_source_file_properties() for LOCATION and add all such locations to a new list, then create a target with that source list.
On Wed, Mar 10, 2010 at 5:04 PM, Markus Raab <[email protected]> wrote: > Hi, > > Thank you both for your help! > > Ryan Pavlik wrote: > > A bit less work: if you're building all the modules in CMake too, you > > could loop through them extracting their source lists then adding those > to > > a new target: probably could be generalizable to a custom command in a > > cmake module. > > Yes, all modules are going to be build withing cmake too. > (Thats the plan if I can solve the static/dynamic issue.) > > What do you mean with source lists? How could I extract their source lists? > And how to I add those to the new target? > > best regards > Markus > > -- > http://www.markus-raab.org | Der Überfluß pflegt auch der > -o) | Allerweisesten Verstand zu blenden. -- > Kernel 2.6.24-1-a /\ | Kaiser Friedrich II > on a x86_64 _\_v | > > _______________________________________________ > 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 > -- Ryan Pavlik HCI Graduate Student Virtual Reality Applications Center Iowa State University [email protected] http://academic.cleardefinition.com Internal VRAC/HCI Site: http://tinyurl.com/rpavlik
_______________________________________________ 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
