|
|
|
|
|
|
|
|
(e.g. SNFMilter), and which extra files are to be part of the |
|
|
(e.g. SNFMilter), and which extra files are to be part of the |
|
|
distribution (e.g. BUGS, README, etc). |
|
|
distribution (e.g. BUGS, README, etc). |
|
|
|
|
|
|
|
|
3) Makefile.am in each directory: SNFMilter, SNFClient, SNF2Check, |
|
|
|
|
|
CodeDweller, SNFMulti, Scripts, Tests, and config_files. These are |
|
|
|
|
|
used to create the Makefile files for building, configuring and |
|
|
|
|
|
installing the software. These Makefile.am files contain lists |
|
|
|
|
|
which source files are to be used for building, and directions to |
|
|
|
|
|
generate the configuration files. |
|
|
|
|
|
|
|
|
|
|
|
In addition, the distribution includes the source files and |
|
|
|
|
|
configuration files for each of the applications. |
|
|
|
|
|
|
|
|
|
|
|
During the build process, the files in SNFMulti and CodeDweller are |
|
|
|
|
|
compiled into a static library. The applications SNF4CGP, SNFClient, |
|
|
|
|
|
and SNF2Check link with these libraries. These libraries are not |
|
|
|
|
|
installed. The system checks the dates of the files, and recompiles |
|
|
|
|
|
and relinks as necessary. |
|
|
|
|
|
|
|
|
3) Makefile.am in each directory: binary/SNF4CGP, binary/SNFClient, |
|
|
|
|
|
binary/SNF2Check, Scripts, Doc, and config_files. These are used to |
|
|
|
|
|
create the Makefile files for building, configuring and installing |
|
|
|
|
|
the software. These Makefile.am files contain lists which source |
|
|
|
|
|
files are to be used for building, and directions to generate the |
|
|
|
|
|
configuration files. |
|
|
|
|
|
|
|
|
|
|
|
During the build process, the binary/<AppName> directories (where |
|
|
|
|
|
<AppName> is the name of the executable) are populated with the object |
|
|
|
|
|
files and executable. The system checks the dates of the files, and |
|
|
|
|
|
recompiles and relinks as necessary. |
|
|
|
|
|
|
|
|
To add an additional source file , edit the appropriate Makefile.am. |
|
|
To add an additional source file , edit the appropriate Makefile.am. |
|
|
Add the source file to the appropriate variable. For example, in |
|
|
Add the source file to the appropriate variable. For example, in |
|
|
SNFMilter/Makefile.am: |
|
|
|
|
|
|
|
|
SNF4CGP/Makefile.am: |
|
|
|
|
|
|
|
|
1) SNFMilter_SOURCES for the cpp files for SNFMilter. |
|
|
|
|
|
|
|
|
1) SNF4CGP_SOURCES for the cpp files for SNF4CGP. |
|
|
|
|
|
|
|
|
2) noinst_HEADERS for the header files for SNFMilter. These are |
|
|
|
|
|
part of the user tarball, but aren't installed into the user system. |
|
|
|
|
|
|
|
|
In the top-level Makefile.am: |
|
|
|
|
|
|
|
|
|
|
|
1) noinst_HEADERS for the header files for SNF4CGP. These are part |
|
|
|
|
|
of the user tarball, but aren't installed into the user system. |
|
|
|
|
|
|
|
|
Note that files that are not listed will not be included in the |
|
|
Note that files that are not listed will not be included in the |
|
|
distribution tarball. This allows you to have additional files in |
|
|
distribution tarball. This allows you to have additional files in |