You should be able to configure a file into your binary directory that references all the option variables of interest and then make a dependency on that file for your add_custom_command.
That way, the file will change only if one of the options changes in cmake and the dependency on it should trigger a re-run of the custom command... Have you tried that? HTH, David On Tue, Oct 28, 2008 at 3:45 PM, James Bigler <[EMAIL PROTECTED]> wrote: > I have a project that makes use of a add_custom_command that generates some > cpp files from a given input file. The command can have different arguments > depending on some CMake OPTION variables. > > If I change the option variables from the CMake GUI, configure and > regenerate the Visual Studio projects, are the add_custom_commands supposed > to be run again? Currently they are not. > > I would argue that the add_custom_command should be rerun if any of the > commands change via editing the CMakeLists.txt file or by a configuration > modification. > > Has anyone come up with a mechanism to work around this issue? > > CMake: 2.6.2 > VS 2005 (32/64 bit) > WinXP 64 > > Thanks, > James > > _______________________________________________ > CMake mailing list > [email protected] > http://www.cmake.org/mailman/listinfo/cmake >
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
