both the includes and the libs list require full paths,
which isn't very useful when your project is stored on a
flash drive and moves from computer to computer, often
taking different drive letters.
I support the idea. Currently it's impossible to move
project from one place on disk to another, you have to edit .dev file manually. Storing relative paths to .dev file
path would solve the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I may be blind, but it looks like the issue about the
relative paths is still an open one. I downloaded the 4992
preview as you suggested and created two new files in my
project: camera.h and camera.cpp. The resulting .dev file
was (sadly) like this (paths in Units 1..4 were previously
edited manually, .dev file is in D:\Program
Files\DevCpp\Projects\Shooter):
Anyway - is it me, who's doing something wrong or this bug,
or rather inconveniece, really exists? I would expect the
path to look like in the above units 1 to 4. I sometimes
take projects to my workplace and then I have to edit the
paths in *.dev to point to files in the project.
Thanks for your prompt reply, don't bother with this problem
if you have more interesting tasks to do :)
Regards,
ptysio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Err...um... looks like I'm the idiot here. I just downloaded
the devcpp.exe pointed by you ("...overwrite devcpp.exe with
the newest build: http://www.castlesofpoland.com/dev-cpp/devcpp.exe") - I got
scared by the initial message of the installer "please do
not install it over an existing installation" and exited it.
So the answer to your question would be negative: I didn't
check anything because I didn't actually install the
complete 4992. I guess I should, shouldn't I? I'm feeling so
stupid but I'm quite new to this tool, this is the only
excuse I have...
Best regards,
ptysio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Afraid not, Installed in a seperate folder and overwrote as per
instructions, but unlike ptysio, my issue was less with the files
in the project, and more with the libraries, includes and
resources list in the [Project] section of the dev file.
Whenever I try to give it a relative path there the valid path
test deems it invalid.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1221419
I support the idea. Currently it's impossible to move
project from one place on disk to another, you have to edit
.dev file manually. Storing relative paths to .dev file
path would solve the problem.
Logged In: YES
user_id=609236
try the 4992 preview:
http://sourceforge.net/forum/forum.php?thread_id=1220176&forum_id=33286
and
overwrite devcpp.exe with the newest build:
http://www.castlesofpoland.com/dev-cpp/devcpp.exe
http://www.castlesofpoland.com/dev-cpp/devcpp.map
and let me know what you think
Logged In: YES
user_id=1221419
hi Specu,
Well, I may be blind, but it looks like the issue about the
relative paths is still an open one. I downloaded the 4992
preview as you suggested and created two new files in my
project: camera.h and camera.cpp. The resulting .dev file
was (sadly) like this (paths in Units 1..4 were previously
edited manually, .dev file is in D:\Program
Files\DevCpp\Projects\Shooter):
[Unit1]
FileName=main.cpp
[Unit2]
FileName=includes\vector.h
[Unit3]
FileName=tga.cpp
[Unit4]
FileName=includes\tga.h
...
[Unit11]
FileName=........\Program
Files\DevCpp\Projects\Shooter\includes\camera.h
[Unit12]
FileName=........\Program
Files\DevCpp\Projects\Shooter\camera.cpp
After moving this project to drive C: we got:
...
[Unit7]
FileName=D:\Program
Files\DevCpp\Projects\Shooter\includes\camera.h
...
[Unit11]
FileName=D:\Program Files\DevCpp\Projects\Shooter\camera.cpp
Anyway - is it me, who's doing something wrong or this bug,
or rather inconveniece, really exists? I would expect the
path to look like in the above units 1 to 4. I sometimes
take projects to my workplace and then I have to edit the
paths in *.dev to point to files in the project.
Thanks for your prompt reply, don't bother with this problem
if you have more interesting tasks to do :)
Regards,
ptysio
Logged In: YES
user_id=609236
just one question: during the installation did you check the
option "remove previous settings" (or whatever that was on
the very bottom)?
Logged In: YES
user_id=1221419
Err...um... looks like I'm the idiot here. I just downloaded
the devcpp.exe pointed by you ("...overwrite devcpp.exe with
the newest build:
http://www.castlesofpoland.com/dev-cpp/devcpp.exe") - I got
scared by the initial message of the installer "please do
not install it over an existing installation" and exited it.
So the answer to your question would be negative: I didn't
check anything because I didn't actually install the
complete 4992. I guess I should, shouldn't I? I'm feeling so
stupid but I'm quite new to this tool, this is the only
excuse I have...
Best regards,
ptysio
Logged In: YES
user_id=1221419
OK, installed in new place, updated, ran... and it seems to
work fine, as I wanted. My fault was not to reinstall.
Thanks, the case is closed :)
Best regards,
ptysio
Logged In: YES
user_id=609236
ok great.
Stephen does 4992 solve the problem for you?
Logged In: YES
user_id=467684
Afraid not, Installed in a seperate folder and overwrote as per
instructions, but unlike ptysio, my issue was less with the files
in the project, and more with the libraries, includes and
resources list in the [Project] section of the dev file.
Whenever I try to give it a relative path there the valid path
test deems it invalid.