On 6. Sep, 2010, at 9:21 , Chris Hillery wrote: > On Sun, Sep 5, 2010 at 10:06 PM, Clifford Yapp <cliffy...@gmail.com> wrote: > >> I was hoping I wouldn't need to do a custom wrapper for every target, >> particularly since I'm building some sub-projects using foreign >> CMakeLists.txt files and I'd really rather not change them from their >> default state - that's an extra maintainance burden and one of the >> advantages I'm most hoping for with CMake is to be able to use >> external build logic without altering it. >> > > Well, if Michael's correct about the original form being available with an _ > prefix, then at least you wouldn't have to modify any sub-project build > files. Just > > function (add_library name ....) > # do stuff to remember this target > _add_library (name ....) > endfunction (add_library) > > Not 100% ideal, but a relatively small amount of work should get you what > you asked for initially, I think. > > Ceej > aka Chris Hillery
There is one problem, though: What if one of the sub-projects also overrides the commands? Michael -- There is always a well-known solution to every human problem -- neat, plausible, and wrong. H. L. Mencken
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ 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
