Sign In
Create Account
Follow Us on Twitter
Subscribe on Youtube
I know many will shake their heads, stroke their fine white beards and say "what is to be done with this boy still wet behind the ears", but what on earth is the point of the "clean" execution in Dev-C++? :confused:
1 reply to this topic
#1
Posted 04 April 2007 - 02:50 PM
phantom3380
-
- Members
-
- 15 posts
Newbie
Yea as it was writ: "Compile and Run" :p
Back to top|
|
|
#2
Posted 12 July 2010 - 02:14 PM
sea
-
- Members
-
- 7 posts
Newbie
Do you know how makefiles work?
Basically, if you use a fancy 'project' or whatever it's called in Dev-C++ then it usually compiles the code in sources, i.e.:
Each source file (.c file) is compiled into an object file (.o file), which is basically an unlinked executable. (It can't run)
So that the overall compile time is reduced, only the source files which have changed need to be recompiled.
Finally, all of the object files are combined and linked to generate the output executable file. (.exe on windows)
The 'clean' command removes all of the object files (.o files) and temporary bits that get generated, leaving you with a 'clean slate'.
This is only necessary if something goes wrong with timestamps and so on, or if you want things to be nice and clean before compiling.
Basically, if you use a fancy 'project' or whatever it's called in Dev-C++ then it usually compiles the code in sources, i.e.:
Each source file (.c file) is compiled into an object file (.o file), which is basically an unlinked executable. (It can't run)
So that the overall compile time is reduced, only the source files which have changed need to be recompiled.
Finally, all of the object files are combined and linked to generate the output executable file. (.exe on windows)
The 'clean' command removes all of the object files (.o files) and temporary bits that get generated, leaving you with a 'clean slate'.
This is only necessary if something goes wrong with timestamps and so on, or if you want things to be nice and clean before compiling.
