From: Daniel R. <da...@pc...> - 2004-01-19 22:00:00
|
In my opinion this is not clear at all. I had to read it very carefully three times before (I think) I understood it. I'm still left with the question: Why would I choose one over the other? If both executables are targeted for a Windows PC running the MinGW suite then what difference does it make which one I use? If it doesn't matter then why provide both? > Repeating does not necessarily clarify the entry. > > I the point this FAQ entry tries to explain is that mingw32-gcc.exe was > not compiled natively using a mingw32 compiler and was actually built > using a non-mingw32 hosted distribution of gcc etc. I do not think the > FAQ entry makes this point successfully. People reading this are likely > not going to be gcc developers, thus I think it should be made clearer. > > > I propose a revision to this FAQ entry: > > __________________________________________________________ > What's the difference between gcc.exe and mingw32-gcc.exe? > > The mingw32-gcc.exe, mingw32-g++.exe, etc. binaries, were compiled using > a cross compiler targeting mingw32, from a non-mingw32 build of gcc. > These binaries produce binaries to be executed on the mingw32 target. > They are therefore distributed as the maintainers of GCC meant them to > be. The gcc.exe, g++.exe, etc. binaries were actually compiled from a > mingw32 gcc build environment, as well as themselves targeting mingw32. > Typically these binaries are identical sizes. > __________________________________________________________ > > > I think this is clearer, would you consider using this entry please? > > Kind regards > > > JG > > > > on the 19/01/04 12:56, Earnie Boyd wrote: > > That would be "a target environment equal to the build environment". |