[Insight-developers] [ITK + Wrapping (Python)] Wrappingclasses proposal - V.3

William A. Hoffman billlist at nycap.rr.com
Tue Aug 2 09:13:03 EDT 2005


You can use:

FILE_WRITE(tmpfile)
EXEC_PROGRAM(${CMAKE_COMMAND} ARGS -E copy_if_different tempfile finalfile)

Why is it a multi-pass process?   Seems like you could build up the file in a cmake
variable, then use CONFIGURE_FILE with one variable in it.  @FILE_CONTENTS@
SET(FILE_CONTENTS ${FILE_CONTENTS} .....)


-Bill

At 06:02 AM 8/2/2005, Benoit Regrain wrote:



>----- Original Message ----- From: "Gaetan Lehmann" <gaetan.lehmann at jouy.inra.fr>
>To: "Benoit Regrain" <benoit.regrain at creatis.insa-lyon.fr>; "William A. Hoffman" <billlist at nycap.rr.com>
>Cc: <insight-developers at itk.org>
>Sent: Tuesday, August 02, 2005 10:50 AM
>Subject: Re: [Insight-developers] [ITK + Wrapping (Python)] Wrappingclasses proposal - V.3
>
>
>>On Tue, 02 Aug 2005 10:31:04 +0200, Benoit Regrain <benoit.regrain at creatis.insa-lyon.fr> wrote:
>>
>>>No, because I'm writting these files in multi-pass, using FILE_WRITE with the
>>>APPEND flag. And due to the keep of the actual file list, it seems impossible
>>>with the CONFIGURE_FILE command.
>>
>>It seems to be feasible to write a temp file, and then use CONFIGURE_FILE to copy the temp file to a file named wrap_???.cxx
>>Don't you think so ?
>The content of a CMake command (like CONFIGURE_FILE) musn't be the file generated by
>WRITE_FILE. So, it doesn't work :-(
>(I have tested it)
>
>
>
>Benoit Regrain 



More information about the Insight-developers mailing list