I guess a follow on to that would be the opposite to composition. If I wanted to decompose a cmake library to determine what object files it contains is there an easy mechanism for this?
Cheers, Tim On Wed, Sep 8, 2010 at 4:30 PM, David Cole <david.c...@kitware.com> wrote: > On Wed, Sep 8, 2010 at 4:54 PM, Tim St. Clair <timoth...@gmail.com> wrote: > >> Folks, >> >> Is there an easy way (best practice) to add prebuilt .o files >> (external to my build) to a .a easily? >> >> -- >> Cheers, >> Timothy St. Clair >> >> >> _______________________________________________ >> 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 >> > > If it's compatible with the other .o files being built to go in your > library, just add the .o file in question as a "source file": > > add_library(mylib /path/to/my.o ${other_sources}) > > > HTH, > David > > -- Cheers, Timothy St. Clair
_______________________________________________ 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
