Nemo DJB Library (libdjb) - Installation
Install the second generation of core routines.
Requirements
General Requirements
- BSD/Linux/Unix based system,
- C compiler that understands prototypes,
- mdoc publishing system for processing manual pages,
- A basic 'make' utility.
Package Requirements
None.
Preferable
<stdint.h> ,
malloc(3) that returns aligned memory.
Preparation
- Download the compressed archive.
- Decompress the archive.
- Change directory to the uncompressed package.
Review the following files - these provide build time configuration options. Only the first line is used for the configuration parameter, the remainder of the file may contain comments.
Configuration files
File name |
Type |
Description |
conf-ar |
text |
The command that will be used to create archives (libraries). |
conf-cc |
text |
The command that will be used to compile .c files. |
conf-devtcp |
integer |
Flag indicating the presence of TCP device node in the system (SunOS 5). |
conf-ld |
text |
The command that will be used to link .o files into an executable. |
conf‑malloc‑aligned |
integer |
Flag indicating that malloc(3) returns pointers to aligned memory. |
conf-manuser |
text |
Owner (username) of the installed manual pages and directories. |
conf-noreturn |
text |
Value of the macro "__NORETURN__ ". Used to indicate that a function will not return. |
conf-prefix |
text |
Path to the nemo-libdjb prefix directory. |
conf-stdint |
integer |
Flag to indicate the presence of "standard integers" present in the development system. Typically stdint.h must exist for standard integers. |
conf-unused |
text |
Value of the macro "__UNUSED__ ". Used to indicate unused function parameters; only comes to light if using strict compiler settings. |
How to Build
Compile the programs and create the libraries and formatted man pages:
The digit 1 can be replaced with a higher number.
How to Install
Install the programs, libraries and manual pages (as super user):
The digit 1 can be replaced with a higher number.
Notice To Package Maintainers
To easily deploy packages, several convenient features are incorporated into the build system.
They are:
- stand alone configuration files - see above,
- install.log - a file detailing the file system changes performed during the install phase.
|