The 'Readme.txt' for the Windows source distribution says:
"You need to download and install a binary release of CMake in order
to build CMake."
Unlike UNIX/Mac, the Windows source can't be bootstrapped...
I assume the Readme.txt is accurate? Any plans to change this?
Thanks,
snaroff
On Dec 7, 2009, at 4:42 PM, Óscar Fuentes wrote:
Bill Hoffman
writes:
[snip]
Even with the IDE based files if you are using install rules, then
the
CMake executable must be available on the machine doing the
install. CMake is also used as the program to do the install
commands.
So, CMa
On Dec 7, 2009, at 9:17 AM, Eric Noulard wrote:
2009/12/7 steve naroff :
As Eric pointed out, you must add CMake to your compiler build
chain.
It's one more tool (and with no third-party dependencies), like
the C
preprocessor, the C compiler and the linker. We did that at work and
it
On Dec 7, 2009, at 7:58 AM, Pau Garcia i Quiles wrote:
On Mon, Dec 7, 2009 at 1:04 PM, steve naroff
wrote:
Thanks for your comments Oscar.
Our current thinking is to post process the cmake generated files
and remove
all the absolute paths (since the project files are simply text
lear if this a 'good' idea? Or will I bump
into other gotcha's?
Any advice is appreciated...you have a lot more experience with this
than I do!
snaroff
On Dec 7, 2009, at 1:10 AM, Óscar Fuentes wrote:
Hello Steve and Eric.
Eric Noulard
writes:
2009/12/6 steve naroff :
Thanks for the quick response...comments below:
On Dec 6, 2009, at 12:20 PM, Eric Noulard wrote:
2009/12/6 steve naroff :
Hi, I work on llvm/clang (a client of cmake).
For development, cmake is wonderful (no big issues).
For deployment, cmake's inability to copy it's generated proje
Hi, I work on llvm/clang (a client of cmake).
For development, cmake is wonderful (no big issues).
For deployment, cmake's inability to copy it's generated project files
to another machine is causing us some grief. The scenario is quite
simple: I want to copy the llvm/clang source tree over
