1,415
edits
Changes
From Studiosg
Jump to navigationJump to searchEn/Trinity desktop environment faq (view source)
Revision as of 10:40, 13 November 2017
, 10:40, 13 November 2017Some questions and answers about TDE building were added
* Move each source code archive in its proper directory inside the build tree for example '''tdebase-R14.0.4.tar.bz2''' in ''/usr/src/tde/base/tdebase/''.
* Move each source code archive in its proper directory inside the build tree for example '''tdebase-R14.0.4.tar.bz2''' in ''/usr/src/tde/base/tdebase/''.
* Update the ''TDE.options'' configuration file setting the target architecture: i486, x86_64 or arm.
* Update the ''TDE.options'' configuration file setting the target architecture: i486, x86_64 or arm.
* Run the main script: '''sh''' ''/usr/src/tde/tde_build_script/bin/TDE.SlackBuild'' .
* Run the main script: '''sh''' '''/usr/src/tde/tde_build_script/bin/TDE.SlackBuild''' .
* Wait for the build procedure to conclude returning message: "'''TDE full build successfully concluded'''".
* Wait for the build procedure to conclude returning message: "'''TDE full build successfully concluded'''".
For more information please read the articles available in this very web site.
For more information please read the articles available in this very web site.
===== Which Ruby Version Is Supported ? =====
===== Which Ruby Version Is Supported ? =====
The last available Slackware Linux release includes packages for '''Ruby 2.2''' that seem to work perfectly with TDE.
The last available Slackware Linux release includes packages for '''Ruby 2.2''' that seem to work perfectly with TDE.
=== Why Are Localization Packages Not Built by the Build Tree ? ===
Building the TDE localization packages requires a lot of time and the saved packages require a lot of disk space. Moreover very few people install 50 different languages on their systems; usually users install the TDE predefined language, English, and their native one. That said the build tree does not build automatically all localization packages to spare time and resources. Build instructions are commented and should be enabled editing the main script: '''/usr/src/tde/tde_build_script/bin/TDE.SlackBuild'''.
=== How Can I Install Localization Packages ? ===
The build tree '''automatically builds and installs''' the localization packages '''when the proper lines of code are enabled''' in the main script: '''/usr/src/tde/tde_build_script/bin/TDE.SlackBuild'''. To enable localization packages building and installing you should:
# Copy source code archives in directory ''/usr/src/tde/base/tde-i18n/''.
# Remove the leading comment in '''line 320''' of the '''/usr/src/tde/tde_build_script/bin/TDE.SlackBuild''' script as in the following example.
<syntaxhighlight lang="bash">
SOURCE_SUBDIR=\".\"" > ./local.options
# Build package
# bash ./${PKG}.SlackBuild
if [[ 0 = ${?} ]]; then
</syntaxhighlight>
Edit it into:
<syntaxhighlight lang="bash">
SOURCE_SUBDIR=\".\"" > ./local.options
# Build package
bash ./${PKG}.SlackBuild
if [[ 0 = ${?} ]]; then
</syntaxhighlight>
=== I Need Only One Localization Package. How Can I Alter the Script to Build Only One ? ===
There are 2 ways to build only one localization package. The first and easier one consists of populating the ''/usr/src/tde/base/tde-i18n/'' directory with but the desired language tarball. The second way consists in editing '''/usr/src/tde/tde_build_script/bin/TDE.SlackBuild''' script and is way trickier.
If you want to permanently update the script just edit the '''for cycle''' responsible for selecting localization tarballs and remove the asterisk character. For example edit line:
<syntaxhighlight lang="bash">
for LC_PACK_PATH in ${TMP}/tmp-${PRGNAM}/${DIR_SRC}/${PRGNAM}-* ; do
</syntaxhighlight>
changing it into
<syntaxhighlight lang="bash">
for LC_PACK_PATH in ${TMP}/tmp-${PRGNAM}/${DIR_SRC}/${PRGNAM}-nds ; do
</syntaxhighlight>
this way only the '''tde-i18n-nds''' localization package will be built while every other will be ignored.
If you wish to add a parameter for language selection to the script replace the asterisk character with a new variable. Assign a value to the newly added variable when running the script or add it to the option file. For example suppose to introduce variable '''LOCALE''' as follows:
<syntaxhighlight lang="bash">
for LC_PACK_PATH in ${TMP}/tmp-${PRGNAM}/${DIR_SRC}/${PRGNAM}-${LOCALE} ; do
</syntaxhighlight>
then add the following lines somewhere at the beginning of the script:
<syntaxhighlight lang="bash">
LOCALE=${1}
# Check for command line parameter.
if [[ -z ${LOCALE} ]]; then
echo "(EE) missing locale."
exit -1
fi
</syntaxhighlight>
The '''LOCALE''' variable is assigned the first parameter passed to the '''/usr/src/tde/tde_build_script/bin/TDE.SlackBuild''' script.
To build the '''tde-i18n-nds''' package, for example, you should invoke the script as follows:
'''sh''' '''/usr/src/tde/tde_build_script/bin/TDE.SlackBuild''' tde-i18n-nds
=== Where Is TDE Installed ? ===
All packages making up TDE are configured to install in directory ''/opt/trinity'' in order to ensure a pacific coexistence of TDE and KDE.
=== Can I Change the Installation Directory ? ===
Of course. Please edit the configuration file ''TDE.options'' and change the '''PREFIX''' value. For example to install TDE in directory ''/usr/bin'' set the following value for '''PREFIX''':
<syntaxhighlight lang="bash">
PREFIX="/usr/bin"
</syntaxhighlight>
=== How Much Storage Installing TDE Takes ? ===
The base packages, the prerequisites and the extension libraries add up to:
* '''700 Mb''' for the 32 bit version.
* '''750 Mb''' for the 64 bit version.
Localization packages and applications are excluded.
=== Where Is TDE built ? ===
The build tree scripts all write temporary files in directory ''/tmp/build/'' while the installation packages are saved in directory ''/tmp/''.
=== How Much Storage Building TDE Requires ? ===
The base environment requires more or less '''1 Gb''' of storage for temporary files written by some of the largest packages while building. Add '''300 Mb''' to store the output packages. Localization packages require a lot disk space more. The one time I built them all it used '''4 Gb''' of free space in directory ''/tmp''. Sadly I cannot provide you data regarding the applications and extensions because I never tried to build them all.
=== Why Is Directory ''/tmp/build/'' Always Empty ? ===
Temporary files are deleted every time a package finishes building in order to save disk space otherwise the 1 Gb value suggested above will not suffice.
