On Mon, Jul 26, 2010 at 7:28 PM, Michael Wild <[email protected]> wrote: > The build_thirdparty macro calls itself other macros, e.g. build_zlib. That > one "guesses" the output location of the zlib libraries, creates an IMPORTED > library target and sets XXX_LIBRARIES accordingly. > > The problem of finding the output location of external projects has been > discussed quite a few times, and there is only one really clean, although > complex and confusing solution: There is one "master" project which only > makes calls to ExternalProject_Add, even the main project is build as such an > external project.
Isn't the solution to use system libs for zlib? Building zlib 'privately' seems like a bad work around. Olaf _______________________________________________ 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
