[cmake-developers] How to get a nightly build process going.

[Nils Gladitz]

On 30.08.2014 22:09, dev wrote:
> The problem is probably in my own head because I tend to define "work"
> as
> the ability to completely compile AND pass a testsuite. Which means that
> by that definition GCC never "works" but it gets pretty close.
>
> Perhaps "close" is good enough for now however I won't actually install
> whatever I have into a production system until it passes all the tests.
>
> So for the moment I have :
>
> $ /usr/local/bin/git clone --verbose git://cmake.org/cmake.git
> Cloning into 'cmake'...
> remote: Counting objects: 162805, done.
> remote: Compressing objects: 100% (41649/41649), done.
> remote: Total 162805 (delta 124692), reused 157825 (delta 119979)
> Receiving objects: 100% (162805/162805), 37.37 MiB | 953.00 KiB/s, done.
> Resolving deltas: 100% (124692/124692), done.
> Checking connectivity... done.
> Checking out files: 100% (7410/7410), done.
>
>
> What I need to do now is figure out a simple sequence of steps. I figure
> I'll need to tar up that result and move it to a build area, then use
> autoconf tools to generate a configure script or some such set of magic.

I imagine it would be:

1 mkdir build
2 cd build
3 ../bootstrap
if build fails fix issues and go back to 3

If the build succeeds you should be able to run the cmake binaries from 
the build directory as-is (without having to install anything).
You just need a build of cmake (including ctest) capable of running the 
dashboard scripts to start with.

I am not sure why you would have to tar up or move anything or why you 
would have to involve autotools.

Nils