This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Sample directory structure
- To: Martin von Loewis <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Subject: Re: Sample directory structure
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sun, 06 Sep 1998 01:17:22 -0600
- cc: jab3 at hotmail dot com, egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199809051752.TAA18542@mira.isdn.cs.tu-berlin.de>you write:
> > Could someone draw me a picture :-) ?
>
> Without having actually tried, here's how I'd proceed:
>
> - unpack egcs, to egcs-src
> - unpack binutils.
> mv bfd binutils gas gprof ld opcodes egcs-src
> not_sure_what_todo_with config etc include libiberty texinfo
> #you certainly need the include stuff, the config stuff should be
> #identical. You probably copy those binutils directories over to
> #the egcs directory
> (see the toplevel Makefile for subdirectories that are supported)
> - make a number of build directories, one for each target
> - in egcs-hpux, do
> ./configure --prefix=/ecad/contrib
> make
> make install
Basically right.
The problem areas are config, include and all the toplevel files.
These are not likely to be the same between the binutils release and
the egcs releases.
Odds are you'd want the include tree from the binutils release,
libiberty from egcs, texinfo from either. config from egcs and
the toplevel files from egcs.
For various reasons I do expect this to get simpler in the future.
jeff