[openbeos-build-team] Re: Jam 2.4 hack

  • From: "David Reid" <dreid@xxxxxxxxxxxx>
  • To: <openbeos-build-team@xxxxxxxxxxxxx>
  • Date: Sun, 30 Jun 2002 18:36:38 +0100


While this is very cool I think we should stick as much as possible to a
standard version of Jam if we can.

Can you submit the changes to perforce and see if they will roll them in?
Either that or we need to put the entire source into the tree and have the
first thing done to be build Jam. I guess for that we need a buildconf
script or some such...

Nice work though.

----- Original Message -----
From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
To: "OBOS Build Team" <openbeos-build-team@xxxxxxxxxxxxx>
Sent: Sunday, June 30, 2002 8:25 PM
Subject: [openbeos-build-team] Jam 2.4 hack

> Hi,
> as you might already have noticed, I fixed a few things on the build
> system and added an autodetection for the GCC path. It is still
> commented out as it uses the Command rule I hacked into Jam 2.4. and
> thus won't work with other Jam versions. The hack can be found here
> (sources as well as executables for x86 BeOS and Linux, and SPARC
> Solaris):
>   http://cs.tu-berlin.de/~bonefish/download/jam-2.4-2002.06.30.zip
> Give it a try and tell me, if you like it.
> Oh, right, the Command rule: It passes each list element supplied to it
> to a shell, gathers the commands' output and returns it as a list split
> at line bounds.
> CU, Ingo
> PS: Ryan, didn't you want to send me your changes to Jam?

Other related posts: