2011/9/12 Akshay <akshay.ran...@gmail.com>: > Hello All, > > I have recently ported my project software tree to CMake and I am pretty > happy about it. There is a last step which is proving quite elusive to me. > The targets that are built in the software tree are TGZ'd for final > distribution, however, CPack if run from the CMakeLists.txt file will pickup > only those targets which are installed by INSTALL command.
This is the expected behavior CPack uses "install". > I can't change the directory structure for historical reasons. If I use > INSTALL from the > individual directories' CMakeLists.txt, CPack from the main CMakeLists.txt > is not finding anything and generates an empty TGZ. How does "make install" behave? Which version of CMake/CPack are you using? On which platform? > src > |- a > |- b > |- c > |- dt > |- proj > |- CMakeLists.txt (main) > |- build > |- e > |- x > |- y > |- z This means that you main CMakeLists.txt is in a sibling directory of others source dir and not has a parent, right? Would you be able to create a small project which exhibits the same issue? In particular how do you call CMake in your case? cd proj/build cmake ../proj if so, how do you recurse to other source dirs? Does your CMakeLists.txt includes something like add_subdirectory(../a) ? -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org _______________________________________________ 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
