[CMake] FW: cmake newbie questions

[Phil Smith]

>Failing on check size of is not a good thing, and I would track that
>down if I were you...

Any clues how to do that?  I see this in CMakeCache.txt:

HAVE_SIZEOF_LONG_LONG:INTERNAL=FALSE
HAVE_SIZEOF_UNSIGNED_INT:INTERNAL=FALSE
HAVE_SIZEOF_UNSIGNED_LONG:INTERNAL=FALSE
HAVE_SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=FALSE
HAVE_SIZEOF_UNSIGNED_SHORT:INTERNAL=FALSE
//Result of CHECK_TYPE_SIZE
SIZEOF_LONG_LONG:INTERNAL=
//Result of CHECK_TYPE_SIZE
SIZEOF_UNSIGNED_INT:INTERNAL=
//Result of CHECK_TYPE_SIZE
SIZEOF_UNSIGNED_LONG:INTERNAL=
//Result of CHECK_TYPE_SIZE
SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=
//Result of CHECK_TYPE_SIZE
SIZEOF_UNSIGNED_SHORT:INTERNAL=

...but that's about it.
-----Original Message-----
From: Bill Hoffman [mailto:bill.hoffman at kitware.com]
Sent: Wednesday, July 30, 2008 2:04 PM
To: Phil Smith
Cc: Cmake Mailing List
Subject: Re: [CMake] FW: cmake newbie questions

Phil Smith wrote:
> But then it complains that there's no CMakeLists.txt in the
> directory.
Anyway, I wasn't clear: the same person isn't likely to be doing z/OS
and Windows on the same machine. But since the same CMakeLists.txt is to
be used, I didn't want to hard-code anything in there. I've changed to
-G -- somehow I missed that before (I did look, honest!).
>

You really want out of source builds.   You have to give the path to the
source tree.  First make sure the source tree you are working on has not
had cmake run on it (no CMakeCache.txt, or other generated files).
Then, you do this:

cmake -G"Unix Makefiles" ../path/to/your/source

Note, the ../path/to/your/source.  That is important.



>
> Now, I'm sort of inclined to declare victory for now. But should I?
Are those "failed" messages significant? I was brought up not to ignore
errors without understanding them!


Failing on check size of is not a good thing, and I would track that
down if I were you...

-Bill