This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: Removing --enable-win32-registry?
- From: "Stephan T. Lavavej" <stl at caltech dot edu>
- To: "GCC" <gcc at gcc dot gnu dot org>
- Date: Thu, 8 Apr 2004 23:10:27 -0700
- Subject: Re: RFC: Removing --enable-win32-registry?
- Reply-to: <stl at caltech dot edu>
[E. Weddington]
> As long as GCC can successfully detect it's components when
> it relocated (i.e. re-installed) to a different directory
> (and drive) other than --prefix, whether built with
> host=cygwin or host=mingw32, then I don't see a particular
> need for it. But the above *has* to work.
gcc 3.3.3 can be bootstrapped with MinGW/MSYS, producing a
directory-independent executable (at least as far as staying on the same
drive is concerned; I myself am not interested in drive independence, though
I guess it would work).
I'm guessing that --enable-win32-registry was a morally bankrupt idea in the
first place. A program should be able to find its components no matter what
directory it is installed in, without reference to the registry, as long as
no one has fooled with its subdirectories. (Furthermore, if you ask me, a
program should be installable simply by unzipping, and removable by nuking
its directory.)
Stephan T. Lavavej
http://nuwen.net