Hi,
I want to reanimate discussions about (Visual Studio) support for the
following sourcecode layout:
Toplevel
|
-CMakeLists.txt (sets all common stuff)
-apps
-CMakeLists.txt (adds only the different apps with add_subdirectory(...))
|
- App1
- CMakeLists.txt (project(app1), add_executable(app1 ...),
target_link_libraries(app1lib1)
|
- App2
- CMakeLists.txt (project(app2), add_executable(app2 ...),
target_link_libraries(app1lib1 lib2)
|
-libs
-CMakeLists.txt (adds only the different libs with add_subdirectory(...))
|
- lib1
- CMakeLists.txt (project(lib1), ...)
|
- lib2
- CMakeLists.txt
I think the behaviour with Visual-Studio and Makefiles differs for
those projects. If I cd into $(BUILDDIR)/apps/app1, and do make, the
libraries (lib1 in this case) is build before the app. In Visual
Studio, that lib isn't build, and its .vcproj file isn't included in
the solution for app1.
I know it is possible to open the toplevel solution and then
everything is build fine, but for a project tree where there are many
targets the toplevel solution becomes easily cluttered and it would be
nicer to directly use the solution from the target one wants to build
(e.g. app1).
There were already several discussions about this topic on this list
(http://tinyurl.com/2s3e69 , http://tinyurl.com/3c29em) and there is a
bugreport with an attached patch from Manuel Klimek
(http://preview.tinyurl.com/3bg4za).
But actually I could not read the opinion from CMake-developers about
this issue. Will the patch be included? Are there problems one should
now?
Thanks in advance,
Stephan
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
