Re: another possible crosstool cleanup

["Robert P. J. Day" <rpjday at mindspring dot com>]

On Mon, 29 Sep 2003, Dan Kegel wrote:

> Robert P. J. Day wrote:
> >   it's not clear why the "getandpatch" script checks for values in
> > the TARGET and TARGET_CFLAGS variables, since those variables are not
> > used in this script.  just a cut and paste thing, i assume.
> 
> True, thanks.
> 
> BTW I am tempted to reorganize the scripts like this:
> 1. move all code into a single file, 'functions.sh',
> as shell functions, one per build phase, probably ten functions in all
> 2. turn crosstool.sh into
>        . functions.sh
>     followed by calls to each of the ten or so functions
> The environment variable sanity checks that are now cut-and-pasted
> all over the place would then be concentrated at the top of functions.sh.

i've already done part of that, since it seemed clear that a single script
with a number of internal functions was the cleanest design.  my goal was
to simplify the whole build process just so *i* could understand what
was going on.  in the process, i did remove some functionality -- just
for my own use, i took out the whole download/wget ability.  from my
perspective, i can't see it being used so frequently that it needs to
be automated.  i just figured, if you know you're going to be using
a certain set of gcc/glibc/binutils/etc. tarballs, just download them
to start with and take it from there.

i'm not suggesting that anyone else feels the same way, but to keep 
things simple for me, i just decided to do things that way.

rday


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com