[openbeos-build-team] Re: Jam 2.4 hack
- From: "David Reid" <dreid@xxxxxxxxxxxx>
- To: <openbeos-build-team@xxxxxxxxxxxxx>
- Date: Tue, 2 Jul 2002 02:30:39 +0100
In that case I say go with a script. Rename Jamrules to Jamrules.in and have
the variables as @GCC_PATH@ and let it be substituted into a new file called
Jamrules.
It can also be used for checking versions, as we've just discovered a need
for a recent ld on beos.
david
----- Original Message -----
From: "Ryan Leavengood" <leavengood@xxxxxxxxxxxx>
To: <openbeos-build-team@xxxxxxxxxxxxx>
Sent: Tuesday, July 02, 2002 2:21 AM
Subject: [openbeos-build-team] Re: Jam 2.4 hack
>
> >In the standard Jam source distro a makefile is included for
> >"bootstrapping" Jam. It should be possible to simply use that
> >one.
>
> I've used this Makefile (even on Windows) and it works fine. In fact
> the default settings in it (for CC, etc.) are fine for a BeOS build.
> Of course since we are supporting multiple build environments, we may
> want to use autoconf to really make it easy for people to build this.
>
> Actually on that note, I have no problem at all with using a simple
> configure script to set up the GCC-PATH, etc for the main OpenBeOS
> build. I say this because I'm not sure if that Jam change is the best
> way to do this. From what I've read, using autoconf isn't really that
> much against the "Jam philosophy". So I say we do it if we need to.
>
> Ryan Leavengood
> OpenBeOS Build Team Lead
>
>
Other related posts:
