[vtk-developers] LocalUserOptions move?

[Bill Hoffman]

The LocalUserOptions are after the source lists and before the wrapping.
I think we would want to leave it this way, or people would not be able
to add new classes that were wrapped.   I would guess that this is the
most common use for the LocalUserOptions, and moving them would break that.

-Bill


At 11:51 AM 8/20/2002 +0100, John Biddiscombe wrote:
>Hi all,
>
>I'd like to move
>INCLUDE (${VTK_BINARY_DIR}/Common/LocalUserOptions.cmake OPTIONAL)
>INCLUDE (${VTK_SOURCE_DIR}/Common/LocalUserOptions.cmake OPTIONAL)
>(&etc for each vtk dir)
>
>from the middle of cmakelists.txt, to the end.
>
>Why?
>
>When I first advocated the use of LocalUseroptions.cmake in each directory of vtk, I wanted to remove certain files from the build, and needed it done before the VTK_WRAP_TCL(...) command was executed to prevent the removed files from appearing in the wrapped list.
>
>Yeterday, Bill H (many thanks), showed me that I could use
>
>SET_SOURCE_FILES_PROPERTIES( 
>  ${CommonTCL_SRCS}
>  COMPILE_FLAGS 
>  -H="$ENV{TEMP}/vtk/vtk.csm"
>)
>
>to add flags to just the tcl sources and by doing this, I can add precompiled header support for part of vtk. (The vtkWrapTcl.exe is tweaked to insert extra lines in each source file - this only applies to my local build by the way).
>
>However, this needs to appear after the WRAP_TCL command. 
>
>Any objections to me moving it? Will it affect any other customizations? (earlier trouble can be resolved using the REMOVE command on the tcl srcs if necessary)
>
>JB
>
>
>_______________________________________________
>vtk-developers mailing list
>vtk-developers at public.kitware.com
>http://public.kitware.com/mailman/listinfo/vtk-developers