[CMake] CMake and it's invocation from MS VC7

Steve Johns steve.johns at verizon.net
Tue May 16 15:53:25 EDT 2006


> Steve Johns wrote:
>>> CMake takes responsibility both for generating projects and for keeping 
>>> them up to date as sources (CMakeLists.txt code) change.

> The rules are attached to CMakeLists.txt as custom-build rules.  If you 
> right-click on one and say "Build" it will re-run CMake.

Is this right-click procedure available in MS VS .NET 2003, do you know?  If 
so, I'm not clear on where to find it.

>> I notice that each directory gets a <DIR>.vcproj.cmake file and a 
>> <DIR>.vcproj file - which are the same on my machine.

> When CMake regenerates the project files it puts them in .vcproj.cmake and 
> then copies them to .vcproj only if they have changed.  This way if CMake 
> reruns and nothing changes the users don't have to reload all the projects 
> in the IDE.

Cool.  Thanks for that explanation.

>> I also notice, looking at <DIR>.vcproj.cmake for one of my library 
>> directories, that each source file is listed with
>> AdditionalOptions = " /TP "

> Don't try to edit the property sheets by hand.  They will just be 
> re-written with the old values by CMake the next time it runs.

That matches with my experience ;^)

So, if the " /TP " assigned by CMake is wrong, and I need " /TC " what would 
be the way to accomplish that, permanently?  and can it be done in the 
CMakeLists.txt file so that that file remains the "mother of all build 
instructions"?

__

This project is actually fairly simple in scope, even though it's still 
partially opaque to me at the moment.  I will post the tree layout and my 
CMakeLists.txt files in another message and perhaps what I've bent up can be 
unbent with just a little more expert commentary.  <g>

Brad, I think my questions are merely mediocre, but my understanding is 
growing by leaps and bounds, so your answers must be excellent!

- Steve






More information about the CMake mailing list