spac: Simple Package Configuration

Other Tools:

spac-dist: Build distributable packages

Files:

dist: Rules describing distributable packages
files: Automatically installed files
rules: Rules describing building targets

Notes:

System Dependancies

Jiffy Howto:

1. Identify all the executables you want to build.
2. For each executable, create a file named BASE=x, where BASE is the name of the executable. This will instruct spac to translate BASE.o into an executable by linking it with all the other object files and libraries in the created file.
3. Identify all the libraries used by the above step.
4. For each library, create a file named BASE=l, where the library is named BASE.a, which lists all the object files required by that library.
5. Dependancy files for the object files will be automatically created internally by spac.
6. Dependancies for object targets and system-dependant header files will be automatically created.

Processing:

1. Starts by examining the "all" rule. This rule will produce a list of top-level targets.
2. The rules are examined to satisfy the top-level targets, which produces more dependancies.
3. The remaining dependancies are recursivly satisfied until no dependancies remain.
4. If any dependancies could not be satisfied, the program exits.
5. All the targets are sorted into a Makefile.
6. A list of all the files that will be generated during the build process is written into TARGETS.
7. A list of all source files used to produce the above targets is written into SRCFILES.
8. A list of all the files that were automatically generated is written into AUTOFILES.

Special targets and files:

See the documentation on files and rules for more information.

Compatibility notes:

• The BASE=x, BASE=l, FILES, and TARGETS file names were taken from evidence in the distributed ezmlm-0.53.tar.gz source package.
• Many of the system dependancy tests have been lifted either as-is or with minor modifications from ezmlm, checkpassword, and other DJB packages.

To Do:

• Does not handle documentation in any form. It should be made to handle man pages, HTML documents, plain text files, and a set of pre-named files including (but not limited to) AUTHORS, NEWS, README, THANKS, TODO, and VERSION.
• Does not handle directories. Targets within directories (ie libraries) should produce both additional targets within the top-level Makefile so that they can be built without recursion, as well as a Makefile within the directories so they can be built seperately.
• Does not handle shell scripts.
• Needs to write out another file containing a list of all the dependancy list files used by the package, to aid with source code management.