I just pushed the first example of a configure script

[David Holmes]

Hi Magnus,

On 25/08/2011 7:35 PM, Magnus Ihse Bursie wrote:
> Hi David and everyone else,
>
> I'm an Oracle engineer that have just barely returned from my paternity
> leave, and I will be helping Fredrik, Erik and Kelly with the build
> infrastructure project, as soon as I get up to speed. :)
>
> On 2010-10-22 02:43, David Holmes wrote:
>> I guess I'll have to reserve judgment but I don't like the idea of having
>> to setup different build directories in which to run configure for local
>> vs cross-compile - so far that's not making my job (as a developer) any
>> easier.
>
> The goal of this project is of course to make the everyday work situation
> for the developers better - not worse!
>
> Can you please elaborate on what the problem is? If I understand you
> correctly, you have a situation where you want to repeatedly build the same
> source code to the local platform and also to one (or more) foreign
> platform(s) using cross-compile, right?

Right.

> How would you accomplish this today and how does it differ from using
> configure?

Today I have a source forest and a top-level builds directory that contains 
my build scripts for the different platforms. I simply do build-x.csh or 
build-y.csh.

My recollection from building configure based tools is that now I would have 
to do something like:

mkdir build-x
cd build-x
<run configure for platform x>
cd ..
mkdir build-y
cd build-y
<run configure for platform y>

And thereafter I'd have to identify the right build-x or build-y directory 
to do the actual build.

I'm not saying this is intolerable just saying that this is more cumbersome 
than what I have to do now and I'm unclear what benefit configure is 
actually going to buy me.

Cheers,
David

> /Magnus
>