Extend.conf - Revision history

Marcel at 14:03, 14 June 2014

2014-06-14T14:03:24Z

← Older revision		Revision as of 14:03, 14 June 2014
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.

Marcel: /* Build flags */ ...finish paragraph -_-

2012-02-10T23:12:55Z

Build flags: ...finish paragraph -_-

← Older revision		Revision as of 23:12, 10 February 2012
Line 8:		Line 8:

	=== 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 [[extend.conf]] too.		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 ==

Marcel: /* Build flags */ Update for rev 21

2012-02-10T23:09:30Z

Build flags: Update for rev 21

← Older revision		Revision as of 23:09, 10 February 2012
Line 8:		Line 8:

	=== Build flags ===		=== Build flags ===
	If you want to set additional environment variables to be used during the build of '''all''' packages, you should specify them ~~here~~.		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.

	~~For example~~, by default ~~packages are built using only one processor core. If you want~~ to ~~utilise multiple~~ cores~~, you should add the following line to the top of <code>extend.conf</code>:~~		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.

	~~<pre>export MAKEFLAGS="-j 8"</pre>~~

	~~Replace the <code>8</code> with~~ the ~~number~~ of ~~cores you want to use~~.

	== BLFS Bootscripts ==		== BLFS Bootscripts ==

Marcel: Created page with "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 ..."

2012-02-07T13:42:03Z

Created page with "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 ..."

New page

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.

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 <code>XORG_PREFIX</code>, <code>XORG_CONFIG</code>, <code>KDE_PREFIX</code> 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, you should specify them here.

For example, by default packages are built using only one processor core. If you want to utilise multiple cores, you should add the following line to the top of <code>extend.conf</code>:

<pre>export MAKEFLAGS="-j 8"</pre>

Replace the <code>8</code> with the number of cores you want to use.

== BLFS Bootscripts ==
<code>extend.conf</code> contains a custom shell function called <code>includeBootscript</code>. 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 <code>alsa-utils</code> the bootscript is installed with:

<pre>includeBootscript alsa</pre>

Scripts requiring a BLFS Bootscript must have the bootscripts source in their [[WGETLIST | Script layout]].

== Mate ==
A more recent addition to <code>extend.conf</code> is the <code>convertToMate</code> 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.

Extend.conf - Revision history

Marcel at 14:03, 14 June 2014

Marcel: /* Build flags */ ...finish paragraph -_-

Marcel: /* Build flags */ Update for rev 21

Marcel: Created page with "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 ..."

Marcel: Created page with "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 ..."