Managing programming source code with make
Last revision August 4, 2004
Table of contents:
|
It is best to split large programs into individual routine files so when changes need to be made, only portions of the program need to be edited and re-compiled.
The problem with this is that it is easy to lose track of which portions need re-compilation or what specific sequence of commands is needed to make the final executable.
The make program is designed to track changes for you automatically so the final program can be re-made at any time with the correct routines and minimum re-processing.
make also provides a convenient way to document and save any special compiler or loader options that are needed to create your program so you don't have to remember them each time you make it.
make works best on medium-sized programming projects. It does not provide any convenient "change control" facilities for maintaining multiple versions of a program or documenting the purpose and nature of revisions.
Change control functions, usually needed for large programming projects or programs maintained for multiple hardware platforms, are provided by the Source Code Control System (SCCS) or Revision Control System (RCS), which can work in conjunction with make. The RCS program is recommended because it is free software that is continually maintained and improved by the Free Software Foundation. On pangea, use the command man rcsintro to learn about RCS, and man sccs to learn about SCCS.