|
From: <sp...@po...> - 2004-05-12 18:32:47
|
OROSZI Balázs wrote: > Guillermo Gutierrez wrote: > >> is there any thing else that would need to be updated for mingw to work? > > > No. > > Here's what you can do, as a last resort: > Completely delete everything from > Dev-Cpp/bin > Dev-Cpp/lib > Dev-Cpp/include there's also Dev-Cpp\mingw > > Download the latest installer version of MinGW. Install it. > Add <MinGW installation path>/bin to you PATH environment variable. > > Now, unpack the two gcc 3.4 upgrades (gcc-g++-3.4.0-*** and > gcc-core-3.4.0-***) into the MinGW install, overwriting everything. > I also recommend to download the latest W32Api (2.5 is the latest, as > I remember), and also unpack it (though it is not needed for gcc 3.4 > to work). > > That's it. Now you don't even any compilers to be set up in Dev-C++, > as it will be automatically found, because <MinGW>/bin is added to the > path, and gcc will find it's own includes and libs automatically. AFAIK when you create a c++ project you have to adjust your include paths to match mingw version (currently it's 3.2) According to this page: http://www.bloodshed.net/dev/devcpp.html this is the mingw that was used: ftp://ftp.nanotech.wisc.edu/pub/khan/gnu-win32/mingw32/snapshots/gcc-3.0-1/ AFAIK those components were used in current dev-cpp 5: gdb-5.1.1-1-mingw.tar.gz w32api-2.2.tar.gz mingw-runtime-2.4.tar.gz make-3.79.1-20010722.tar.gz one of gcc-3.2 releases (with patches?) one of binutils-2.13.90 releases (with patches?) so basicly you would need to update those. I think it would be good to start testing those and see the what's happening. mingw gcc 3.4.0 is still a cadidate. I think it would be fairly easy to create a packman entries and then devpaks for with mingw components and then just upgrade them. This wouldn't make as big of a mess than just unzipping the components. Maybe I'll spend some thime on that and post the results later here.... -- Marek Januszewski |