On Tuesday 22 September 2009, Tyler Roscoe wrote: > On Tue, Sep 22, 2009 at 05:55:49PM +0200, [email protected] wrote: > > I have seen a thread about this issue but there was not a real > > solution, so I try to ask that again: Is there a way to define a > > specific CMakeLists.txt-file with a cmake call. > > Maybe you should post a link to the thread so we know what you're > talking about? > > > I have two projects, which have the same root directory (what is really > > nasty but I can't change it actually): > > > > -data > > - subdir1 > > - subdir2 > > - subdir3 > > > > These two projects need some subdirectories, so the cmake files would > > look like this: > > > > CMakeLists-1.txt: (Project 1) > > [..] > > SUBDIRS( > > subdir1 > > subdir3 > > ) > > [..] > > > > and > > > > CMakeLists-2.txt: (Project 2) > > [..] > > SUBDIRS( > > subdir2 > > ) > > [..] > > > > I want to build project 1 completly independent from project 2. > > subdirs() is deprecated. Use add_subdirectory(). > > You can explicitly tell CMake the name of your list file with something > like cd build && cmake ../MyCMakeLists.myext.
I don't think that works. > You could let the CMakeLists in the data directory take care of subdir1 > and subdir3 and move the CMakeLists for subdir2 into subdir2. yes, or add subdirs project1-cmake/ and project2-cmake/ and add the CMakeLists.txt for the projects there ? Alex _______________________________________________ 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
