This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: What's the right way to do host libraries required for gcc
- From: Nathanael Nerode <neroden at twcny dot rr dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Wed, 13 Nov 2002 14:13:01 -0500
- Subject: Re: What's the right way to do host libraries required for gcc
The "right way" is as follows...
Add an "--with-libbanshee=" argument to gcc's configure.in (using the
usual autoconf methods).
--without-libbanshee makes sure libbanshee is not used
--with-libbanshee=/foo/bar looks for libbanshee in /foo/bar
--with-libbanshee looks for libbanshee in ../libbanshee (as you have it now)
(no argument) doesn't use libbanshee
Then change the top level to
1. Recognize libbanshee as a directory to build; this is done in
Makefile.def
2. Put in dependencies so that libbanshee is built before
gcc; this is done in Makefile.tpl right now, with a line like:
all-gcc bootstrap-gcc: all-libbanshee
I'm going to change this method after a while, so watch out.
3. Automatically add --with-libbanshee to the arguments when
configuring the gcc subdirectory, if and only if nothing was specified
on the command line and libbanshee is in configdirs. This is done in
some abstruse mix of configure and configure.in at the moment and the
method will change when I finish making subdirectories configure from
the Makefile.
Personally, I suggest skipping step 3 for the time being, since it
should be significantly easier after I'm further along in
autoconfiscation. This would just mean that people would have to use
--with-libbanshee to use Andersen's points-to analysis for now. (All
--with-foo arguments are passed down from the top level to subdirectories.)
That's the "right way" to do it. You may not want to do it the "right
way", but I encourage you to.
--Nathanael