I have been experimenting for a while with Dev-Cpp and I
think I
discovered a bug. It goes like this... I have the following
directory tree:
C:\
| DeveloperTools
| |Dev-Cpp
|
| Temp
| | myproject
| | | doc
| | | install
| | | proj
| | | | proj1
| | | | Project1.dev
| | | src
No directories contain spaces in whole tree.
Now, I keep my source files in "src". Under
"Project Options -> Build Options -> Executable output
directory"
I have configured path to "install" which gets
automatically
converted to relative path (relative to project
file "Project1.dev").
The same goes for
"Project Options -> Build Options -> Object file output
directory"
which is configured to be "proj1" and then also
automatically
converted to relative path. So far so good, and I
definitelly
like things like relative paths because of future source
distribution. But here's the problem. When I build my
project
(Execute -> Compile) somehow "install" directory gets
created
in "C:\" (root) directory resulting in tree that looks like
this:
C:\
| DeveloperTools
| |Dev-Cpp
|
| Install
|
| Temp
| | myproject
| | | doc
| | | install
| | | proj
| | | | proj1
| | | | Project1.dev
| | | src
Objects files and executable are created in the
directories
that I specified, and newly created "install" directory
stays
empty after build. So, although Makefile.win handles
relative
paths as it should, Dev-Cpp does not.
If I put my project file in "myproject" directory everything
works fine, because there are no relative paths that
begin with
".." sequence in that case.
Simple example project for this problem is atached to
this report...
Logged In: NO
are you runnning 4.9.9.2?