[cmake-developers] [CMake] CMake 2.8.3-rc1 ready for testing!

Brad King brad.king at kitware.com
Tue Sep 28 17:33:17 EDT 2010


On 09/28/2010 05:03 PM, Alexander Neundorf wrote:
> Works, but still it doesn't feel good.
> This means that whenever doing a 
> include(FPHSA)
> in one of cmakes find-modules it must actually be a
> include(${CMAKE_CURRENT_LIST_DIR}/FPHSA.cmake)
> 
> Similar issues can come up with other files and in other projects.
> In the end this would mean that in cmake basically all include()s would have 
> to use the full path :-/

Yes, and overriding any one module in CMake would mean copying it
out and everything that depends on it.  Still, this particular
case is a very short dependency chain.

> Another thing is, a few days ago I added an include guard to KDE's version of 
> FPHSA.cmake, since it is included several times and it's quite long, so it 
> should save some time:

...but as you discovered doesn't work unless there is exactly one
version of the file.  Just leave out the guards.  Correctness is
more important than speed.  We need each module that loads the
macro to get the one it wants.

-Brad



More information about the cmake-developers mailing list