[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-devel] change in how to build condor in 6.8.x and beyond
- Date: Wed, 2 Aug 2006 14:11:00 -0500
- From: Erik Paulson <epaulson@xxxxxxxxxxx>
- Subject: Re: [Condor-devel] change in how to build condor in 6.8.x and beyond
On Wed, Aug 02, 2006 at 11:57:37AM -0700, Derek Wright wrote:
> part of the changes i made in the TRUNK between the time i merged
> V6_7-branch in and when i created the V6_8-branch were to fix an
> issue that's been driving me nuts and creating a lot of problems (and
> work) for condor developers -- how we handle config.h.in.
>
> ------------------------------
> short version:
> ------------------------------
>
> to build condor, once you check-out from source, you should now run
> the "build_init" script in src. this will check for the right
> versions of autoconf and autoheader, and run them to automatically
> generate a configure script and a valid config.h.in file. this is
> already done for you if you use "new_workspace", and the nightly
> condor builds in NMI already do this. so, this should only effect
> you if:
>
> a) you setup your own build workspaces without new_workspace
> or
> b) you make changes to configure.ac and want to test them
>
> in general, the new procedure for building condor should be:
> 1) get sources (cvs checkout, tarball, whatever)
> 2) cd src; ./build_init
> 3) ./configure
> 4) make
>
If I want to have a seperate build tree from my src tree, is anything
different? (or, "do we still need new_workspace, and if we do, could we
put it into CVS as well"?)
-Erik