[openbeos-build-team] Re: Apples build team comments on Jam...

  • From: "David Reid" <dreid@xxxxxxxxxxxx>
  • To: <openbeos-build-team@xxxxxxxxxxxxx>
  • Date: Thu, 20 Jun 2002 11:25:27 +0100

I think there are some questions over Jam and it's suitability. However, I
think we can work through them (as we have) and the only point at which I
would advocate removing it totally is when we come across a situation where
it was just too limiting for our purposes.

I flagged this up to try and bring a degree of realism into our discussions
and point out that while Jam brings some nice things it also imposes a
degree of complexity and order that we will all have to get used to. It also
requires a total brain rewire for anyone used to using make, which is
something that needs to be made obvious to people getting tangled up with it
for the first time.

As long as it can do what we need then I'm happy enough to keep it, compared
with having to rewrite the whole thing using make which would be another
exercise in futility and wasted effort now we have Jam working.

david

----- Original Message -----
From: "Ithamar R. Adema" <ithamar@xxxxxxxxxx>
To: <openbeos-build-team@xxxxxxxxxxxxx>
Sent: Thursday, June 20, 2002 9:51 AM
Subject: [openbeos-build-team] Re: Apples build team comments on Jam...


>
> If this is the feeling of the OBOS build team as well, feel free to phase
> Jam out. I'm not going to be here very much longer, as I'm phasing myself
> out of OBOS anyway :-)
>
> Really, if everyone (me not included) agrees that Jam is a problem, please
> remove it from the build. I don't want to have the feeling I put you
through
> all this just because I thought Jam was nice :-)
>
> Regards,
>
> Ithamar.
>
> ----- Original Message -----
> From: "David Reid" <dreid@xxxxxxxxxxxx>
> To: <openbeos-build-team@xxxxxxxxxxxxx>
> Sent: Thursday, June 20, 2002 10:33 AM
> Subject: [openbeos-build-team] Apples build team comments on Jam...
>
>
> >
> > This is a direct quote from one of the team who wished to remain
> > anonymous...
> >
> > "First answer: do not use jam.  I know we are pretty much sorry we did.
> > This is not to say jam is a horrible tool, but it does not fit well
> > with a lot of complex build scenarios, and especially not with our
> > build system which is very complex.
> >
> > Second answer:  apart from a couple folks on my team and, presumably,
> > the perforce folks, I don't know of any jam experts.  My guys generally
> > hold the first opinion, so I doubt they'll be looking to get more
> > involved with jam issues than they already are..."
> >
> >
>
>
>
>


Other related posts: