Michael, I agree with the first part and not agree with the second part of your message. Libraries (*.lib) are stored to the different folders and compiler will not find A to link it into B without full path. So CMake should provide linker with the full path of the A and B libraries. To calculate full path CMake should process project file.
2009/5/28 Michael Jackson <[email protected]> > > On May 28, 2009, at 3:03 PM, Dmytro Ovdiienko wrote: > > >> > The other side of this problem is you have to write ADD_SUBDIRECTORY >> > commands in specific order. IMHO it is inconvenient. >> >> CMakeLists are essentially a scripting language, so of course order >> matters. What would you propose instead? >> >> But... why does TARGET_LINK_LIBRARIES work correctly? You can pass not >> loaded-yet project name to TARGET_LINK_LIBRARIES. >> > > > Remember that you are passing the names of _libraries_ to > "target_link_libraries" and not the names of Projects. The fact that it > might work just means that you named your libraries the same as the project > name. > > _________________________________________________________ > Mike Jackson [email protected] > BlueQuartz Software www.bluequartz.net > Principal Software Engineer Dayton, Ohio > > > > _______________________________________________ > 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 >
_______________________________________________ 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
