| Originally posted by ClayDowling |
I'm running Dev-C++ on WinXP Pro quite happily. There are some tricks though, and they aren't necessarily obvious.
First, you can't use the GCC 3.2 toolchain, you'll need to use the older version (2.9x). 3.2 is annoying on UNIX (where I am using it) and completely broken under Windows. To get rid of it, you'll have to uninstall the application, then manually delete the folder that you installed it into. If you don't do both, you'll get exactly the ugly errors that you're receiving.
The second step is to download the new IDE with the older GCC toolchain. They you should be running without any problems.
Well. This is actually wrong.
Disregard this please.
Essentially when choosing the dev-cpp flavour you have three options:
1) Stick with the old non-beta: Download version 4.
2) Use the newest beta with the old 2.95 gcc: Download 22.214.171.124/2.95.
3) Use the newest beta with the new 3.2 gcc: Download 126.96.36.199/3.2
The beta versions allows you to add 'devpacks' to your compiler.
A devpack generally expands your possibilities.
For example: If you want to program a graphical Windows game you'd most likely use one or more of the following: Allegro, Direct-X, SDL, OpenGL.
The beta versions are exactly that. Beta versions.
This means, that you'd better watch the dev-cpp forum for information on your version. And you'd better use vUpdate to download updates (and devpacks).
The two most often brought up errors right now
1) The C++ include path is incomplete.
You must manually patch this by including
C:\dev-cpp\include\c++\mingw32 to your C++ include directory list.
2) Compliancy to the C++ language specification. Specifically deprecation of iostream.h.
Basically code like this
cout << "This won't work";
Must be replace with code like this
std::cout << "This will work";
using namespace std;
cout << "This will also work";
Hope it works out for you now.