I just pushed the first example of a configure script

[Magnus Ihse Bursie]

On 2011-08-25 12:01, David Holmes wrote:
> 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.

Are these build scripts are managed by yourself locally on your system? 
Could you possibly post an example of such a script?

Quoting from another mail:
> But my output directory is often on a different file system (local 
> rather than NFS) and it is determined by build identifier eg:
>
> b00/linux-x
> b00/linux-y
>
> etc.
>
> and then
>
> b01/linux-x
> b01/linux-y
>
> etc. 

I don't think I'm familiar with this concept of build identifier. This 
is a name that is given to the build itself and the directory it resides 
in? Is the build identifier in the example above "b00/linux-x" or just 
"linux-x"? Is the "b00" an arbitrary part given by you, and "linux-x" 
the system it is compiled for?

As I understand you, your current situation looks somewhat like this:
Source code on NFS, like:
/nfs-mounted-disk/jdk-srcs/my-jdk-project-1

Builds created locally, like:
/local-disk/build-output/my-jdk-project-1/b00/linux-x
/local-disk/build-output/my-jdk-project-1/b00/linux-y
... etc

And then you have a bunch of scripts located somewhere (else?) which 
builds from /nfs-mounted-disk/jdk-srcs/my-jdk-project-1 and puts the 
output in one of the target directories in 
/local-disk/build-output/my-jdk-project-1; which one is determined by 
the script which has a name matching the actual build produced.

Have I captured the basics of your workflow correctly?

/Magnus