|
From: <sp...@po...> - 2004-05-12 21:19:54
|
OROSZI Balázs wrote: [..] > Due to the stupid layout of Dev-C++'s MinGW "bundle", paths have to be > adjusted, otherwise the compiler will not find it's headers and libraries. dev-cpp doesn't have a layout any other than standar mingw bins. The .tar.gz's provided by them were just untarred to c:\dev-cpp directory. No paths were changed. [..] > Those are separate packages, not needed to be upgraded to use gcc 3.4 > Besides, the right way of upgrading is unzipping. If you ever took a > look at the inner layout of the .tar.gz archives of the MinGW > packages, you would have noticed, that they all have the same > directory layout, which is the same, that is created by the installer, > so unzipping will not create any mess anywhere. It will make > everything get to the right place. > yes. but some c++ programs will require paths like: lib\gcc\mingw32\3.4.0\include (this one is in gcc-core-3.4) which contains mingw version - currently in dev-cpp it's by default hard set to: lib\gcc-lib\mingw32\3.2\include For more details look at bug 910098 reported by kidkat and links to mingw from there. -- Marek Januszewski |