This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: how to develop new target-specific library - autoconf?
- To: Gary Funck <gary at Intrepid dot Com>
- Subject: Re: how to develop new target-specific library - autoconf?
- From: Stan Shebs <shebs at apple dot com>
- Date: Fri, 22 Jun 2001 15:05:22 -0700
- CC: GCC List <gcc at gcc dot gnu dot org>
- References: <DOEPLHFPMCACAGIAHNCHIECOCAAA.gary@intrepid.com>
Gary Funck wrote:
>
> My question: in general, does a GCC developer need to manually invoke
> autoconf, when developing a new target-specific library? Or, is there a step
> missing in some other config file, or Makefile that would've built
> "configure" automatically in the top-level library directory?
The general rule is to run autoconf manually, and add "configure"
as a new source file. To me, the main reason to do this is that
the configure script is the root of the build process; if you try
to auto-tinker with it, you can get into completely mystifying
dependency loops. So it's more reliable to require a conscious
decision to modify configure.
Not everybody agrees with this though.
Stan