From: Earnie B. <ear...@ya...> - 2002-11-27 18:02:59
|
Igor Mikolic-Torreira wrote: > Hi, > > I have always worked with mingw installed component-wise. My colleague > works with the MinGW-2.0.0 "all-in-one" installation. > > I recently noticed that he has a mingw32 subdirectory within his MinGW > directory. The mingw32 directory includes a bin subdirectory containing > a few basic tools such as ar.exe, as.exe (these appear to duplicate > *.exes in the MinGW/bin directory); and a lib subdirectory containing > the ldscripts. > > In my hand-made, component-wise mingw installation, I only have the main > bin directory (which has the *.exes that appear in the mingw32/bin > directory) and I have ldscripts in the main lib directory (i.e., in > MinGW/lib instead of MinGW/mingw32/lib). > > Everything has always worked great for me. But will this bite some > day? It's one of those, maybe types. If you plan to do cross compile builds at any point then, yes, otherwise no. > Do I need a mingw32 subdirectory with bin and lib? And if so, why > duplicate ar.exe, as.exe, etc in both bin and mingw32/bin? > Because that's the way that the configury for GCC installs it and the way the developers of GCC expect it for cross tooling support. Earnie. |