Extend.conf: Difference between revisions
→Build flags: Update for rev 21 |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Documentation]] | |||
Inside the scripts directory, there is a file present which is called <code>extend.conf</code>. This file was introduced in LFScript 4, to seperate BLFS specific instructions from the main executable. | Inside the scripts directory, there is a file present which is called <code>extend.conf</code>. This file was introduced in LFScript 4, to seperate BLFS specific instructions from the main executable. | ||
| Line 8: | Line 9: | ||
=== Build flags === | === Build flags === | ||
If you want to set additional environment variables to be used during the build of '''all''' packages (like build flags), you should specify them in | If you want to set additional environment variables to be used during the build of '''all''' packages (like build flags), you should specify them in <code>extend.conf</code> too. | ||
Starting with LFScript 4r21, the '''MAKEFLAGS''' variable is set by default, to ensure that all CPU cores are utilised during the build of your system. | Starting with LFScript 4r21, the '''MAKEFLAGS''' variable is set by default, to ensure that all CPU cores are utilised during the build of your system. Setting the variable again in <code>extend.conf</code> will override this behaviour. | ||
== BLFS Bootscripts == | == BLFS Bootscripts == | ||
Latest revision as of 14:03, 14 June 2014
Inside the scripts directory, there is a file present which is called extend.conf. This file was introduced in LFScript 4, to seperate BLFS specific instructions from the main executable.
The file is sourced at the start of each package build.
Additional environment variables
BLFS
At the top of the file, additional environment variables are defined and exported. Among these are XORG_PREFIX, XORG_CONFIG, KDE_PREFIX and more. These variables are used throughout BLFS, to make the build more dynamic.
Build flags
If you want to set additional environment variables to be used during the build of all packages (like build flags), you should specify them in extend.conf too.
Starting with LFScript 4r21, the MAKEFLAGS variable is set by default, to ensure that all CPU cores are utilised during the build of your system. Setting the variable again in extend.conf will override this behaviour.
BLFS Bootscripts
extend.conf contains a custom shell function called includeBootscript. This function takes one argument; The name of a BLFS Bootscript which needs to be installed.
This function makes it possible to install a bootscript using a single command in the package script. For example, in alsa-utils the bootscript is installed with:
includeBootscript alsa
Scripts requiring a BLFS Bootscript must have the bootscripts source in their Script layout.
Mate
A more recent addition to extend.conf is the convertToMate function. This function adjusts source code designed for Gnome, so that it can use Mate in stead.
This function is still in development and may not work properly.
