@ -206,20 +200,20 @@ When building sets of modules or the whole TDE, a global build summary is automa
Script used to build the complete TDE at once. Calls the dd_setname.sh set scripts in order.
Script used to build the complete TDE at once. Calls the dd_setname.sh set scripts in order.
Usage:
Usage:
build_TDE.sh
build_TDE.sh
- create_repo.sh
- create_repo.sh
Creates a local repository from the .deb files currently stored in TDE_DIR/2_build/debs.
Creates a local repository from the .deb files currently stored in TDE_DIR/2_build/debs.
Usage:
Usage:
[sudo] create_repo.sh [options]
[sudo] create_repo.sh [options]
Options:
Options:
-b (Backup) : create a backup of the existing repository in TDE_DIR/CFG_REPO_DIR.backup
-b (Backup) : create a backup of the existing repository in TDE_DIR/CFG_REPO_DIR.backup
3) * Building hooks *
3) * Building hooks *
Hooks are available to execute ad-hoc code before and after the build process. For example this is very useful to automatically apply patches.
Hooks are available to execute ad-hoc code before and after the build process. For example this is very useful to automatically apply patches.
There are two type of hooks:
There are two type of hooks:
- pre_build : applied before switching the module to quilt format and build
- pre_build : applied before switching the module to quilt format and build
- post_build: applied after the build (dpkg-buildpackage or pbuilder) has terminated
- post_build: applied after the build (dpkg-buildpackage or pbuilder) has terminated
To use a hook, create an executable script (pre_build.sh and/or post_build.sh) in the TDE_DIR/1_git/hooks/<MODULE NAME> folder. The scripts are executed in the build_module.sh environment, so have access to all the variables defined in that file. See the files in the "hook examples" folder for real usage samples.
To use a hook, create an executable script (pre_build.sh and/or post_build.sh) in the TDE_DIR/1_git/hooks/<MODULE NAME> folder. The scripts are executed in the build_module.sh environment, so have access to all the variables defined in that file. See the files in the "hook examples" folder for real usage samples.
@ -235,7 +229,7 @@ C) How to use the scripts
the process when building several modules in sequence.
the process when building several modules in sequence.
5) Build modules as per your needs. You don't need to use "sudo" directly since the scripts will do that automatically if
5) Build modules as per your needs. You don't need to use "sudo" directly since the scripts will do that automatically if
required. Just type your sudo password when prompted to do so.
required. Just type your sudo password when prompted to do so.
6) Create a local repository from the packages you have just built, to be used as installation repository.
6) Create a local repository from the packages you have just built, to be used as installation repository.
[sudo] ./create_repo.sh
[sudo] ./create_repo.sh
7) Install TDE as you usually do. For example as follow:
7) Install TDE as you usually do. For example as follow:
- sudo apt-get update
- sudo apt-get update
@ -243,15 +237,15 @@ C) How to use the scripts
or
or
sudo aptitude install tde-trinity (for a standard TDE environment)
sudo aptitude install tde-trinity (for a standard TDE environment)
Examples of real usage:
Examples of real usage:
1) build a single module
1) build a single module
- ./build_module.sh -g -sl "dependencies/libr" -> build libr package. This is a good test to check
- ./build_module.sh -g -sl "dependencies/libr" -> build libr package. This is a good test to check
whether everything is working fine
whether everything is working fine
- ./build_module.sh -g "tdelibs" -> build "tdelibs" from git sources in a clean chroot environment
- ./build_module.sh -g "tdelibs" -> build "tdelibs" from git sources in a clean chroot environment
- ./build_module.sh -g -l -sl "applications/amarok" -> build "amarok" locally from git sources and
- ./build_module.sh -g -l -sl "applications/amarok" -> build "amarok" locally from git sources and
display building logs during building
display building logs during building
- ./build_module.sh -sh -lr "tdebase" -> build "tdebase" from the local sources (in TDE_DIR/2_build/build/tdebase)
- ./build_module.sh -sh -lr "tdebase" -> build "tdebase" from the local sources (in TDE_DIR/2_build/build/tdebase)
in a clean chroot environment and launch a shell in case of building failure.
in a clean chroot environment and launch a shell in case of building failure.
@ -259,13 +253,13 @@ Examples of real usage:
- ./build_module.sh -g -po "tdelibs" -> prepare "tdelibs" for building from git sources. Source code will be available
- ./build_module.sh -g -po "tdelibs" -> prepare "tdelibs" for building from git sources. Source code will be available
in TDE_DIR/2_build/build/tdelibs. After you have made changes to the source and
in TDE_DIR/2_build/build/tdelibs. After you have made changes to the source and
want to build the modified package, run './build_module.sh "tdelibs"'
want to build the modified package, run './build_module.sh "tdelibs"'
2) build a single set
2) build a single set
(optional) delete the TDE_DIR/0_logs/build_result.log file
(optional) delete the TDE_DIR/0_logs/build_result.log file
./01_base_01.sh -> build this set.
./01_base_01.sh -> build this set.
./03_base_03.sh -s 3 -> build this set but skip the first 3 modules of the set.
./03_base_03.sh -s 3 -> build this set but skip the first 3 modules of the set.
3) build all TDE
3) build all TDE
./99_build_TDE.sh -> build all TDE
./99_build_TDE.sh -> build all TDE
4) [sudo] ./create_repo.sh -> build or update your local TDE repository
4) [sudo] ./create_repo.sh -> build or update your local TDE repository