Download Salvo User Manual

Note The
free/lib/ilib/(blank)
naming convention was used
up to and including Salvo v3.0.5. As of v3.0.6, the
lite/le/pro/prolib convention is used.
In many instances, a project may contain multiple project files, all
using a single salvocfg.h.
Wherever possible, relative pathnames have been used in the project files to accommodate installations that do not use Salvo's default installation directory.
Note Programs built with freeware libraries are marked with a '†'.
Source Files
In most cases, we have avoided creating projects with identical or
redundant source files. Each project generally contains the following:
project_dir\main.c
project_dir\main.h
project_dir\other_source_files.c
project_dir\other_header_files.h
project_dir\test_system_dir\salvocfg.h
contains the source for the program. There may be additional source files in the project directory and / or in its test system
subdirectories. main.h contains compiler- and target-specific symbols (if required). salvocfg.h contains the project-specific Salvo
configuration.
main.c
Additionally, where several projects are grouped together (e.g. the
tutorial projects salvo\tut\tu1-tu6), files that are common to all
of the projects are located in the first project, even if they are not
used by the first project in the group. Files that are common to a
particular test system will be found in the associated folder (e.g.
salvo\tut\tu1\sysi).
SYS Predefined Symbols
Preprocessor symbols in the form SYSA, SYSB, … (see Table 103)
are used liberally within projects to control the conditional compilation of a project's header files. This is why a header file may con-
526
Appendix C • File and Program Descriptions
Salvo User Manual