From http://sourceforge.net/forum/forum.php?thread_id=1036469&forum_id=48211:
"A final note: You are best off establishing a directory like c:\mycstuff and writing and saving stuff there. Don't save your programs in a directory with spaces in them either." [posted by Wayne Keen (drwayne)]
I've been using Dev-C++ 4.9.9.2 for a while now (running on Windows XP Pro, SP2) and I've always saved my .c and .cpp files on my flash drive, buried inside many subfolders all with spaces and I've never had a problem.
So I was wondering, is there any specific advantage that I need to know about that saving stuff in a folder with no spaces brings?
Thank you for your time,
-JaDe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The advantage is this. If you save your projects (single files will work OK, they do not invoke "make") in a folder with spaces in it, eventually, it will stop working correctly. As I state somewhere in the "Please Read" thread, we have dealt with a lot of "But it used to work!" type questions in this area.
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah, I see. So it's projects that mess up. Cool, cool. Thanks for telling me. :-)
Quick question, though: What exactly are projects? I've been using Dev-Cpp for about a year in my programming classes, but our teachers haven't told us anything about projects. Are projects just a group of single files all pulled together? Or is there other stuff to it?
-JaDe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've only had two programming classes, Intro to Programming Concepts (using C++) and C Programming. So I don't know much about programming. So I ask you, what are link parameters? (AKA How would it be useful/a good idea to "do it" for a single file?)
Thanks for the fast replies,
-JaDe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
They tell the linker where to find libraries, and which libraries to link and the like.
The project enables you to set these, and other parameters as needed for your code,
and have that information go along with the project, rather than having to be set
and unset at the master "compiler options" level. That is why Clifford tirelessly
tells people that they should use a project, even for a single file program.
Want to know more about "libraries" and such? There is a section in the thread
titled "Please Read Before Posting a Question" on the compile log, including headers,
and linking libraries. There is a lot of good material in there, graciously donated
by users.
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From http://sourceforge.net/forum/forum.php?thread_id=1036469&forum_id=48211:
"A final note: You are best off establishing a directory like c:\mycstuff and writing and saving stuff there. Don't save your programs in a directory with spaces in them either." [posted by Wayne Keen (drwayne)]
I've been using Dev-C++ 4.9.9.2 for a while now (running on Windows XP Pro, SP2) and I've always saved my .c and .cpp files on my flash drive, buried inside many subfolders all with spaces and I've never had a problem.
So I was wondering, is there any specific advantage that I need to know about that saving stuff in a folder with no spaces brings?
Thank you for your time,
-JaDe
The advantage is this. If you save your projects (single files will work OK, they do not invoke "make") in a folder with spaces in it, eventually, it will stop working correctly. As I state somewhere in the "Please Read" thread, we have dealt with a lot of "But it used to work!" type questions in this area.
Wayne
Ah, I see. So it's projects that mess up. Cool, cool. Thanks for telling me. :-)
Quick question, though: What exactly are projects? I've been using Dev-Cpp for about a year in my programming classes, but our teachers haven't told us anything about projects. Are projects just a group of single files all pulled together? Or is there other stuff to it?
-JaDe
A project is a means for bringing together multiple files, creating what
is called a makefile to compile and link together all of the source.
You can also do it for a single file - it can be a good idea as it allows
you to set your compile and link parameters uniquely to the file.
Wayne
p.s. I don't even keep my single files in space directories.
I've only had two programming classes, Intro to Programming Concepts (using C++) and C Programming. So I don't know much about programming. So I ask you, what are link parameters? (AKA How would it be useful/a good idea to "do it" for a single file?)
Thanks for the fast replies,
-JaDe
They tell the linker where to find libraries, and which libraries to link and the like.
The project enables you to set these, and other parameters as needed for your code,
and have that information go along with the project, rather than having to be set
and unset at the master "compiler options" level. That is why Clifford tirelessly
tells people that they should use a project, even for a single file program.
Want to know more about "libraries" and such? There is a section in the thread
titled "Please Read Before Posting a Question" on the compile log, including headers,
and linking libraries. There is a lot of good material in there, graciously donated
by users.
Wayne
FYI: http://sourceforge.net/forum/message.php?msg_id=2670009
I'm going to rewrite that one day without the typos.