[openbeos-build-team] Re: Jam 2.4 hack
- From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
- To: openbeos-build-team@xxxxxxxxxxxxx
- Date: Tue, 02 Jul 2002 21:11:19 CEST (+0200)
> The shell script can just use sed or some such and simply substitute
> the
> paths...
Mmh, what's the point of using sed again? I mean, if BuildConfig is
merely a collection of the platform/target/whatever specific variables,
it can simply be generated as proposed. I actually don't any reason for
a BuildConfig.in. Where you would write "@GCC_PATH@" which would be
replaced by the configure script, you can just write "$(GCC_PATH)".
> Then it can run Jam :)
That's an easy one. :-)
Though it's certainly annoying, when working on the script.
> We can have a line telling people they only need to run Jam from then
> on.
>
> Don't get too involved - it's should be a wonderfully simple little
> bootstrap script that gets run once. Avoid autoconf like the plague.
No problem with that.
> > # Generate BuildConfig
> > cat << EOF > BuildConfig
> > # BuildConfig
> > # Note: This file has been automatically generated by configure.
> >
> > GCC_PATH = ${GCC_PATH}
> > EOF
Who finds the missing ";". ;-)
CU, Ingo
Other related posts:
