yesterday I installed Dev C++ for the first time, and I was pleasantly surprised: it is a great peace of software!
But now to the problems:
Im working on Windows 2000 and using cygwin tools with gcc 3.2 compiler, so I downloaded devcpp4970exe.exe, the Dev C++ package without a compiler.
I installed Dev C++ to "D:\Program Files\Dev-Cpp" directory.
I opened Tools / Compiler Options / Directories / Libraries dialog, an there were two lines:
D:\Program
Files\Dev-Cpp\lib
The problem is, that white spaces in the path are not treated correctly. The other problem is, that the path itself is incorrect: D:\Program Files\Dev-Cpp\lib directory doesnt exist in my case.
So I removed both lines and I pressed Ok. Now the message You have not indicated the location of your binaries (compiler). Please do sow now appeared. Is this really necessary? Path to the compiler is already specified in the PATH env. variable Ok, I solved this by entering C:\cygwin\bin into Binaries.
Now I loaded a project and tried to compile it, but I received List index out of bounds (0) message, which was probably caused by empty Libraries list. When I added C:\cygwin\lib\mingw to the list, the compilation succeeded.
I did the same with C Includes dialog: I entered C:\cygwin\usr\include\mingw, but I received a warning message:
cc1: warning: changing search order for system directory "/usr/include/mingw"
cc1: warning: as it is the same as non-system directory "C:/cygwin/usr/include/mingw"
So it seems that C Includes list should be empty, because the compiler already knows where to search for header files.
And now one other thing, more a proposition then a bug:
I would like to have two compiler settings: one to compile in cygwin mode, and the other to compile in mingw mode. The difference between this two modes is that the mno-cygwin gcc command line option should be specified for compilation in mingw mode.
But the Compiler Options / Compiler / Add the following commands when calling compiler is global and cant be different for each compiler set. So my proposal is to make it local for each compiler set. The same is for Add these commands to the linker command line.
And now, the last problem:
Dev C++ debugging doesnt work in combination with cygwin gdb. Currently I dont have an idea why
The problems I mentioned are only minor ones and there are already workarounds for them.
Best Regards,
Borut Razem
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1) Do not change the default install path for Dev-C++ from C:\Dev-CPP
2) Cygwin paths are:
bin -> C:\cygwin\bin
lib -> C:\cygwin\lib
C -> C:\cygwin\include
C++ -> C:\cygwin\include\C++;C:\cygwin\include
3) Compiler options are not global in 4.9.7.x. It may not seem that way at first glance but if you set up two different sets and switch between them on the first tab they will correctly keep all their own settings in the other tabs. (I have MinGW and Cygwin, with the latter as the first option--- Dev-C++ uses that as the "default" regardless of the name of the compiler)
4) Cygwin gdb doesn't work because of the new line handling bug. Until then, compile using Cygwin, and switch to MinGW before debugging.
Cheers,
-- Matt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Dev C++ developers,
yesterday I installed Dev C++ for the first time, and I was pleasantly surprised: it is a great peace of software!
But now to the problems:
Im working on Windows 2000 and using cygwin tools with gcc 3.2 compiler, so I downloaded devcpp4970exe.exe, the Dev C++ package without a compiler.
I installed Dev C++ to "D:\Program Files\Dev-Cpp" directory.
I opened Tools / Compiler Options / Directories / Libraries dialog, an there were two lines:
D:\Program
Files\Dev-Cpp\lib
The problem is, that white spaces in the path are not treated correctly. The other problem is, that the path itself is incorrect: D:\Program Files\Dev-Cpp\lib directory doesnt exist in my case.
So I removed both lines and I pressed Ok. Now the message You have not indicated the location of your binaries (compiler). Please do sow now appeared. Is this really necessary? Path to the compiler is already specified in the PATH env. variable Ok, I solved this by entering C:\cygwin\bin into Binaries.
Now I loaded a project and tried to compile it, but I received List index out of bounds (0) message, which was probably caused by empty Libraries list. When I added C:\cygwin\lib\mingw to the list, the compilation succeeded.
I did the same with C Includes dialog: I entered C:\cygwin\usr\include\mingw, but I received a warning message:
cc1: warning: changing search order for system directory "/usr/include/mingw"
cc1: warning: as it is the same as non-system directory "C:/cygwin/usr/include/mingw"
So it seems that C Includes list should be empty, because the compiler already knows where to search for header files.
And now one other thing, more a proposition then a bug:
I would like to have two compiler settings: one to compile in cygwin mode, and the other to compile in mingw mode. The difference between this two modes is that the mno-cygwin gcc command line option should be specified for compilation in mingw mode.
But the Compiler Options / Compiler / Add the following commands when calling compiler is global and cant be different for each compiler set. So my proposal is to make it local for each compiler set. The same is for Add these commands to the linker command line.
And now, the last problem:
Dev C++ debugging doesnt work in combination with cygwin gdb. Currently I dont have an idea why
The problems I mentioned are only minor ones and there are already workarounds for them.
Best Regards,
Borut Razem
1) Do not change the default install path for Dev-C++ from C:\Dev-CPP
2) Cygwin paths are:
bin -> C:\cygwin\bin
lib -> C:\cygwin\lib
C -> C:\cygwin\include
C++ -> C:\cygwin\include\C++;C:\cygwin\include
3) Compiler options are not global in 4.9.7.x. It may not seem that way at first glance but if you set up two different sets and switch between them on the first tab they will correctly keep all their own settings in the other tabs. (I have MinGW and Cygwin, with the latter as the first option--- Dev-C++ uses that as the "default" regardless of the name of the compiler)
4) Cygwin gdb doesn't work because of the new line handling bug. Until then, compile using Cygwin, and switch to MinGW before debugging.
Cheers,
-- Matt