...
Section | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Inherited builds
In essence an inherited build is where the build (i.e. compilation) settings for OpenIFS are not altered but are used or inherited by a new FCM configuration file placed in a separate directory. The new FCM configuration file only needs to specify what's different about the build, either the sources or compilation settings. The rest of the information is obtained by telling FCM to look at the OpenIFS configuration. A user may have a number of these separate configuration files each in separate directories for developing or testing independent code changes.
Example1: Modifying compilation options
In HowTo customise compiling OpenIFS, it's explained explains how environment variables and editing the configuration files can alter the compiler settings for OpenIFS. In this simple example, an inherited build is used to alter the compilation of some source code.Recall the layout of the OpenIFS directories in the directory 'oifs'achieve the same effect by creating a separate configuration file.
Create directories for your own configuration files and source code. For example:
Code Block |
---|
% cd oifs
% mkdir mysrc mymake
% ls
COPYING ChangeLog INSTALL LICENSE NOTICE README html make src t21test |
...