Trinity Desktop Environment Packaging - Slackware slackbuilds
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ray-V 0675d7d79b Updates for development builds: 4 weeks ago
Apps Updates for development builds: 4 weeks ago
Core Updates for development builds: 4 weeks ago
Deps Updates for Slackware current 1 month ago
Libs Removals, revisions and patches .. 1 year ago
Misc Updates for Slackware current 1 month ago
src Updates 1 year ago Updates for Slackware current 1 month ago Added option to build pre-release snapshot 2 years ago Updates for Slackware current 1 month ago Updates for Slackware current 1 month ago

... a TDE desktop, cross compiled for aarch64, running on a RPi3.

Build TDE [Trinity Desktop Environment]
.. for Slackware 14.2 or current on i586+ and x86_64.
.. see 'Cross compiling for RPi3' for building for armv7/aarch64.

Build the release version 14.0.9 from tar archives; or the development versions 14.0.10, 14.1.0 from trinitydesktop cgit.
For a native build, run ./ - a dialog based script with a series of screens for user input.

The default is to install the packages as they are built, which is necessary initially for the required packages and for some interdependencies [for example, tdesdk requires tdepim].

Run INST=0 ./ to build only.
This is a global option so can't be used where the build list includes packages which will need to be installed as dependencies for other packages in the build list.

Any package, or set of packages, can be selected in the 'TDE Packages Selection' screen.
Information about dependencies for some packages has been added at the bottom of the dialog screen.

14.0.9 source archives will be downloaded from a geoIP located mirror site, or the development sources [14.0.10/14.1.0] cloned or updated from cgit.
Downloading can be done pre-build [useful for an off-line build], or during the build.

If you're curious about what this might involve, take a look at a sample build set up.

Other command line options that can be used to set some build parameters:

The directory structure for the SlackBuild scripts is in line with the Trinity release source repositories:

Deps [dependencies/]
Core []
Libs [libraries/]
Apps [applications/]

Other directories are:

Misc - for non-Trinity package builds
src - to hold all the sources, either pre-downloaded or downloaded during the build.

Other scripts: - a chunk of common code for the SlackBuilds
              - used for getting the sources, setting FLAGS, creating build directories, ...

There is an override in the Misc SlackBuilds for non-trinity source archive URLs. Non-trinity builds have been included where a TDE package requires a dependency that is not in Slackware, or where it's an alternative to a TDE package.

Required packages for a basic working TDE are:



i18n support [locale and html/help docs] in the packages is restricted to whatever is selected in the ./ 'Select Additional Languages' screen and, of that, to whatever is available in any individual package source.

Additionally for the development builds, translations for the .desktop files are determined from the LINGUAS variable which is set in this build shell to the additional languages selected.

There is an option in tde-i18n.SlackBuild to include a user created language specific patch file in the build.
It needs to be named tde-i18n-{lang}-patch and will then automatically be included for the build for that language.
Because of its position in the Slackbuild and the patch -p0 option, the path to the patched file must start with 'tde-i18n-{lang}' - see tde-i18n-en_GB-patch for an example.

Building the development versions from git sources

The individual TDE apps can be cloned from Trinity git, so the build is set up to do that - except for individual language packs of tde-i18n. The whole tde-i18n download is ~1x10^6 bytes, so to reduce that, wget is used to download individual tde-i18n-$lang packs as they are not git repositories.

Once any git repository has been cloned, further downloads are updates only[2], giving the best options - only fetching what is needed, and incremental updates.

The git repositories are cloned to 'src/cgit'

Cross compiling for RPi3

Cross compiling a number of packages for the Raspberry Pi3 based on these scripts is detailed in the html page in the gh-pages branch:

git clone  
cd tde-slackbuilds  
git checkout gh-pages

which can be viewed online.


  • Setting parameters for a 32-bit [armv7 hard float], or 64-bit [aarch64], build,
    .. and building ..
  • a cross compiler toolchain
  • a 64-bit kernel which can be used for the 32-bit system
  • qemu to run the TDE binaries built and used during compilation
  • the required TDE apps
  • a few other TDE and non-TDE apps to provide a basic, but useful, TDE desktop.

Known issues

[1] TDM may need some manual setting up - see Core/tdebase/README, which can also be viewed while running ./ if tdebase is selected.

[2] The i18n downloads with wget can't be updated because cgit produces 'current time' timestamps. The consequence is that if tde-i18n-$lang is a part of the build after its initial download, it will be downloaded again. As updates are infrequent, once built, there will probably be no need to do so again and so tde-i18n for a particular language will probably only be run once. On that basis I don't see this being a significant issue.

[3] The Misc directory contains SlackBuilds for software that might already be installed from other sources. Please check because any misc builds selected here could overwrite them.

[4] The README for a native build for Raspberry Pi3 [] is now rather dated and cross compiling is a better option.

[5] Building the kalzium equation solver needs ocaml and facile installed. They will be built, packaged, and installed during the tdeedu build if the source archives are pre-downloaded to the 'src' directory.

See for more information