Differences between version 4 and predecessor to the previous major change of MakeToSCons.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Tuesday, June 1, 2004 9:57:40 am | by DanielLawson | Revert |
| Older page: | version 3 | Last edited on Monday, May 31, 2004 9:29:06 pm | by SamJansen | Revert |
@@ -27,9 +27,9 @@
Both of these work the same at the first glance, though I believe the SConstruct (yes, SConstruct is the name of the file that replaces your Makefile) file a lot more readable. However the SCons file has the following extra features:
* Proper dependency tracking. SCons scans the source file for headers so it knows when each file needs to be compiled. Make has no knowledge of this by default, and doing proper dependency tracking in make is quite a nightmare (but possible).
* MD5Sum based checking of the source files to see which ones need to be recompiled. Make uses timestamps, which is also an option for SCons.
-* No explicit rules needed for this simple example. In the makefile the linking line was still necessary (along with the strange syntax: a casual reader has no idea what $@ and $^ mean).
+* No explicit rules needed for this simple example. In the makefile the linking line was still necessary (along with the strange syntax: a casual reader has no idea what $@ and $^ mean). ''Note, the linking line isn't needed in a Makefile -- DanielLawson''
* You can automatically clean the build with __scons -c__. This cleans only the files generated in the build. Clean rules have to be specified by the programmer in makefiles.
* Even works in Windows with the MicrosoftVisualStudio C Compiler.
!! Setting CFLAGS and similar
