CAPS Universe documentation
1.0.4
All you need to know to be successful
|
Since you define the run-time directory setup when configuring the big bang library libcapsbase, you need to start here and think a while about your requirements. If you run a desktop host the requirements are different from an embedded system. Think about read-only filesystems, security requirements or small filesystem storage for data, configs and executables.
An overview about the filsystem usage (an example):
/ | +--- etc | | | +--- caps (CAPS Configuration Directory) | | | | | +--- drivers (CAPS Printer Driver Configuration Directory) | +--- usr | | | +--- bin (Tools Directory) | | | +--- lib (Library Directory) | | | +--- libexec | | | | | +--- caps (CAPS Printer Driver Executables Directory) | | | | | | +--- include (Header File Directory) | | | +--- sbin (Service Executables Directory) | | | +--- share | | | | | +--- caps | | | | | | | +--- drivers (CAPS Printer Driver Database Directory) | +--- var | | | +--- lib | | | | | +--- caps (CAPS Printer Device Database Directory) | | | | | | | +--- printer_dhfgez (CAPS Printer Device Parameter Directory) | | | +--- spool | | | | | +--- caps (CAPS Document Storage Directory) | | |
The meaning of the various directories: