[CMake] Handling library dependencies and minimizing duplicated include_directories

[Michael Jackson]

If you are using any of the "Makefile" generators, you can simply  
drill down into the folder of the library you want to build and issue  
the "make" command. The library, and anything that it depends on will  
be built (or rebuilt) accordingly.
___________________________________________________________
Mike Jackson                      www.bluequartz.net


On Mar 22, 2010, at 9:52 AM, Aaron_Wright at selinc.com wrote:

> I've always been a little confused by FIND_PACKAGE and those "*- 
> config.cmake" files. So much so that I didn't use them in my build  
> system at all. The main question I have is that I have several  
> developers and numerous little and big libraries. Because the whole  
> project is so big it would be prohibitive for them all to work from  
> a master CMakeLists.txt file at the top. I want each developer to be  
> able to go the folder of the library they want to work on today and  
> start building there. I want all the libraries that library depends  
> on to be built or rebuilt if anything has changed in addition to  
> building the current library.
>
> I've been unable to find a simple solution to this problem using  
> CMake, which makes me wonder if what I'm doing is off the wall, but  
> it sounds so normal to me. I see these "*-config.cmake" files but it  
> seems they are generated from a CMakelist.txt file, which wouldn't  
> make any sense, because I'm not going to have a developer go to each  
> dependant library and build it seperately so that the "*- 
> config.cmake" can be generated so that he can have those variables  
> back in the library he really wants to build.
>
> What am I missing?
>
> -------------------------------------------------------------
> Aaron Wright
>
>
>
> From:
> Daniel Lidström <daniel.lidstrom at sbg.se>
> To:
> Cc:
> <cmake at cmake.org>
> Date:
> 03/20/2010 01:25 PM
> Subject:
> Re: [CMake] Handling library dependencies and minimizing  
> duplicated        include_directories
> Sent by:
> cmake-bounces at cmake.org
>
>
>
>
> > If the projects UMC3D, GFL etc can be used independently, but
> > are all "under your control", then you shouldn't write
> > FindUMC3D.cmake, FindGFL.cmake etc files, but create
> > UMC3D-config.cmake, GFL-config.cmake etc files instead. Read
> > the documentation of the FIND_PACKAGE command, especially the
> > paragraphs about the "config mode". You'll also find many
> > discussions on this in the archives of this list.
>
> Thanks a lot for your help Mike!
>
> Regards,
>
> Daniel Lidström
> Stockholm, Sweden
> _______________________________________________
> 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