I guess a different question I should be asking is why is the CMakeLists.txt build rule running after my other custom rules. It seems to me that the CMakeLists.txt build rule should *always* be the first thing to build in a given project.
James On Tue, Aug 9, 2011 at 4:06 PM, James Bigler <[email protected]> wrote: > I also just noticed that if I set CMAKE_SUPPRESS_REGENERATION, then the > CMakeLists.txt files don't get added to the projects. > > I wonder how hard it would be to just not add build rules to the > CMakeLists.txt files...... > > James > > > On Tue, Aug 9, 2011 at 2:48 PM, James Bigler <[email protected]>wrote: > >> What would it take to remove the build rules on the CMakeLists.txt files >> in Visual Studio? >> >> They are causing me no end of grief with the CUDA tools. Basically what >> happens is that the CMakeLists.txt files are getting compiled after the CUDA >> rules causing each and every project to trigger a "reconfigure" event which >> loads the plugin dialog box. I'm wanting the reconfigure even to happen >> only during the ZERO_CHECK phase (e.g. once for every 'build it' command). >> >> At one point we had discussed the fact that having a build rule on the >> CMakeLists.txt files is generally a Bad Idea when dealing with parallel >> builds, but it is even more unbearable now that VS 2010 seems to be running >> the CMakeLists.txt build rule after the CUDA ones. >> >> Thanks, >> James >> > >
_______________________________________________ cmake-developers mailing list [email protected] http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
