[vtkusers] compiling issues

[John Drescher]

On Wed, Mar 18, 2009 at 3:28 AM, Oliver Kania
<ptw.freiburg at googlemail.com> wrote:
> I think using Cmake implies having to manually add the names of new files
> etc. to the Cmake file, doesnt it ? Whenever the project changes, I have to
> "regenerate" the visual studio solution. I do not consider this to be
> convenient.
> It would be if Cmake could be integrated in Visual Studio and the Cmake
> stuff would
> be generated automatically.
>

I add new files to the CMakeLists.txt file (usually 2 or more at a
time) then I either create a new files with notepad++ or visual studio
or drag the file names (one at a time) to my command window (I always
have a command/shell window open on windows or linux) and execute
touch <filename>. Which is usually touch ./src/MyNewClassName.cxx and
touch ./Include/MyNewClassName.h

I have touch in my path from git but there are other places to get it.
I discussed with the list this week 2 different ways to automatically
call touch on nonexistent files but I have not implemented this yet.

I really like the out of source building with cmake. It makes cvs/svn
and backups cleaner and smaller and also cleaning any junk that ends
up in the binary folders when testing. I can just delete the whole
build tree (minus the CMakeCache.txt) if I want and I am assured that
every file in there is generated from the compiler or cmake. And then
there is the integrated unit testing and generation of an installer.
And I am forgetting the ability to have one source tree and build for
multiple compilers in their own build tree with or without different
settings. I am now not sure how I programmed in windows for 12 years
(and 500K+ lines of MFC code) without it. Eventually I plan to convert
all my code to cmake.

John