So the problem with CCMake forgetting valid user input stems from the
entire CMakeCache.txt file getting deleted if there's a compiler
mismatch?
On Tue, Mar 3, 2009 at 11:21 AM, Bill Hoffman bill.hoff...@kitware.com wrote:
Mathieu Malaterre wrote:
On Tue, Mar 3, 2009 at 4:20 PM, kent williams
Yeah, if you're comfortable using the Unix command line, using
non-interactive CMake this way is almost always an easier path to joy
than using the GUI or Curses interactive application.
It's why the Slicer people spent considerable time putting together a
suite of TCL scripts to do their builds,
kent williams wrote:
So the problem with CCMake forgetting valid user input stems from the
entire CMakeCache.txt file getting deleted if there's a compiler
mismatch?
Yes, that is what happens. The use case that this was supposed to
address was this:
ccmake ../source
- oops, I did not
I have had this issue an infinite number of time. Debian packager
would be using inconsistant c++ compiler and I could not use both ITK
and VTK at the same time (from debian package). So I provided an
(undocumented) hack:
CMAKE_OVERRIDE_COMPILER_MISMATCH
2cts
On Mon, Mar 2, 2009 at 8:27 PM, kent
That's all well and good, but is exactly the sort of thing I DONT want
to have to put in FOSS CMakeaLists.txt files. It would be useful in
situations like this where you're liking against multiple
system-installed CMake-built libraries. But any other situation,
you'd run into problems where a
On Tue, Mar 3, 2009 at 4:20 PM, kent williams nkwmailingli...@gmail.com wrote:
Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and
lets you generate your build files.
And if I recall correctly, earlier versions (2.3? 2.4?) did not act this way.
Yup, this behavior appears
On Tue 2009-03-03 09:20, kent williams wrote:
Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and
lets you generate your build files.
This and the fact that most modules aren't written to handle multiple
passes (for instance, if the wrong version is found on the first pass,
the
Mathieu Malaterre wrote:
On Tue, Mar 3, 2009 at 4:20 PM, kent williams nkwmailingli...@gmail.com wrote:
Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and
lets you generate your build files.
And if I recall correctly, earlier versions (2.3? 2.4?) did not act this way.
Yup,
Version 2.6 patch 2 on OS X and Linux -- you know your code is
portable when the same issue happens on multiple platforms!
Here's the scenario -- a guy in our department was having trouble
getting ccmake to generate makefiles.
My diagnosis was pretty simple: His project depended on both ITK and
