Re: crosstool-0.36 coming up soonish

[Dan Kegel <dank at kegel dot com>]

Robert Schwebel wrote:
> > > It would result in a cleaned up top directory; contrary to what we have
> > > in PTXdist you probably only need one file per config, so it would just
> > > move the config files into a sub directory. 
> >
> > Yes, but I ship crosstool with several hundred configs...
>
> Well, if you have the SVN repo ready I'll make a prototype 
> in a branch ;) - that's better than discussing without code.  

Now, Robert, you're perfectly able to make a prototype
without SVN.    But I don't think a gui front end is
neccessary for the current problem.

I think we're both trying to come up with a way to get rid
of the zillions of .dat files.  Here's my best idea so far:
right now, I do
   eval `cat $cpu.dat $toolchain.dat` sh all.sh
to build.  I could replace that with
   eval `ctconfig.sh $cpu $toolchain` sh all.sh
Then instead of a zillion .dat files, I'd have a single
ctconfig.sh script that accepts arguments describing
the toolchain.  Initially the script could just contain
exactly the .dat files, but it could be smarter, too.
- Dan

--
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

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