[CMake] Using Checksum to generate files

[avner cohen]

Eric,
I may have used wrong terminolegy there, my IDLs are indeed part of the the project, It's only that the project is a C++ based project, so the IDLs are not being "compiled" in any way, they are used to generated a set of .h and .cpp files (which in term, are patr of the project.
As soon as I generate these files, all compilers (xlC, cc and gcc) will execute a full build, even if the files are identical to the previously generated files.

So my main aim is to find a way to:
1. Always check if IDL changed.
2. Generated ouput .cpp and .h files only IDL are changed.

Thanks,

Avner.

 


----- Original Message ----
From: Eric Noulard <eric.noulard at gmail.com>
To: avner cohen <avcoh at yahoo.com>
Cc: Tyler Roscoe <tyler at cryptio.net>; cmake at cmake.org
Sent: Wednesday, August 12, 2009 10:26:48 AM
Subject: Re: [CMake] Using Checksum to generate files

2009/8/12 avner cohen <avcoh at yahoo.com>:
>
> Thanks Tyler.
>
> I'm not sure I'm following how this is related to my question.
>
> The solution I'm looking for is to be able to execute or generate a file, ONLY when an out-of-project file is being modified (which is why I tried to use checksum caching). How is this condition satisifed in the below link?

As far as I understand your testcase I think both Tyler and Michael are right.
Why do you state that "when an out-of-project file is being modified"
your IDLs files are in the project right?

Your example says:
-I ${PROJECT_SOURCE_DIR}IDLs ${PROJECT_SOURCE_DIR}/IDLs/CORBAStructDefs.idl

so the COMPILE_IDL of Michael should be just fine, or are we missing something?

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org