Re: On the toplevel configure and build system

["Joseph S. Myers" <joseph@codesourcery.com>]

On Wed, 30 Mar 2011, DJ Delorie wrote:

> > > (h) utils - I don't know what to do with this directory or where it best 
> > > goes.
> > 
> > relates to the other bits of src and where it would best go if src is 
> > split up.
> 
> For example, the MeP utils is used to reconfigure gcc, binutils, cgen,
> sid, and a few other places (libgloss) according to the templates
> provided by the chip fab (MeP is a synthetic chip) so as to match the
> specific cpu configurations in your chip (how many cores, which
> options each core has, memory layout, etc).

Thanks.  My inclination is to say that this should be considered an 
independent tool in its own repository, as something not required in the 
build of any of the other tools.  More specifically, utils/mep and 
utils/wince look like independent tools each of which would better go in 
its own toplevel directory (mep-integrator, cesetup) (and would each go in 
an independent repository based on the shared toplevel, since they use 
libiberty), while utils/spu appears to have no toplevel dependencies and 
so should be completely independent, possibly without toplevel support for 
building it.  Since utils/spu and utils/wince have no non-build-system 
changes since 2000, I'd be inclined to say we should declare those two 
subdirectories dead and run "cvs rm" on them - people wanting to resurrect 
them can always extract the data from CVS later.  (And I still think 
utils/mep should move to its own toplevel directory.)

-- 
Joseph S. Myers
joseph@codesourcery.com