[Cmake] Unix installation

[Bill Hoffman]

../CMake/configure
vi CMakeCache.txt
gmake
gmake install

To install cmake, it must be built twice, the first time by configure, the
next time by cmake.   Perhaps the configure script should be renamed to
bootstrap_configure.

Because once you have a cmake, all you need to do is this:

cmake ../CMake
gmake
gmake install


So, configure is only needed if you don't have cmake already installed.
If configure is used, cmake must be built twice, as there are some options
that configure does not figure out.

-Bill


At 02:48 PM 7/18/2001 -0400, Miller, James V (CRD) wrote:
>What is the recommended procedure to install CMake in a directory other than /usr/local ?
> 
>From a fresh checkout, I've been doing
> 
>../CMake/configure
>make
>Source/cmake ../CMake
>vi CMakeCache.txt (change INSTALL location by hand)
>make
>make install
> 
>So I end up building cmake twice.  The first time is to get a cmake executable that I can build cmake a second time using cmake.  Once I run cmake on cmake, then I can edit the cache to change the install prefix.
> 
>Why doesn't cmake use
> 
>../CMake/configure --with-prefix=foo
> 
>Or has this been fixed?
>
>Jim Miller 
>_____________________________________
>Visualization & Computer Vision
>GE Corporate Research & Development
>Bldg. KW, Room C218B
>P.O. Box 8, Schenectady NY 12301
>
>millerjv at crd.ge.com <<mailto:millerjv at crd.ge.com>mailto:millerjv at crd.ge.com>
>(518) 387-4005, Dial Comm: 8*833-4005, 
>Cell: (518) 505-7065, Fax: (518) 387-6981 
>
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20010718/6b1e7583/attachment.html>