I just pushed the first example of a configure script

[David Holmes]

On 26/08/2011 10:22 PM, Magnus Ihse Bursie wrote:
> On 2011-08-26 13:51, David Holmes wrote:
>
>> The scripts simply sets the desired environment variables such as:
>>
>> BUILD_HOTSPOT=true
>> BUILD_JDK=true
>> ...
>> ALT_OUTPUTDIR=/my-local-filesystem/$BUILD/$OS-$ARCH
>> cd ..
>> make all
>
> So they are all quite similair except for setting $OS and $ARCH (and
> $BUILD?) differently? Or do you have even more different configurations in
> them? So you might have like build-linux-ia32-without-smp.csh etc for stored
> typical special build configurations?

The common settings are split into a common script that is included in the 
per-target scripts. The per-target scripts need to set additional variables 
to control other aspects of the build (eg cross-compilation).

> If not, is the reason for having multiple scripts (instead of like
> "build.csh linux-ia32") tab completion/imlicit syntax check? Or is there
> another reason?
>
>> b00 is the build number - and yes it is arbitrary in this context. linux-x
>> represents $OS-$ARCH
>
> Build number as in the latest official JDK build number, or as in somethink
> you increment (automatically?) every time you build?

It is just a build differentiator to define part of the output path.

David
-----

>> Have I captured the basics of your workflow correctly?
>>
>> Essentially yes.
>
> Good. :)
>
> /Magnus