This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
configuration options policy (at toplevel or only inside gcc/)?
- From: Basile STARYNKEVITCH <basile at starynkevitch dot net>
- To: gcc at gcc dot gnu dot org
- Date: Thu, 14 Dec 2006 10:19:12 +0100
- Subject: configuration options policy (at toplevel or only inside gcc/)?
Hello,
Most options of GCC (like --enable-werror --with-gmp ...) are configure-able
at its toplevel source directory while others ( --enable-mapped-location
.... ) are configure-able with the configure script inside its gcc/ source
subdirectory
Of course, some options are for the whole toplevel.
When adding a new option, should I always add it at the toplevel or not?
Some options (like --enable-mapped-location or --with-gc=zone) seems to be
only usable with the gcc/configure script which seems usually to be run by
the build procedure (ie by the make at build).
Actually, I don't fully understand what might go inside the toplevel. I
believed that once perhaps even gdb or binutils could go there but I might
be wrong...
In other words, should I make all my configurable flag visible by the
toplevel configure and propagated (thru Makefile.tpl) to gcc/ or not?
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faïencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***