Trinity Desktop Project Wiki - User contributions [en]

How to Build TDE Core Modules

2021-06-27T12:03:15Z

Cethyel: /* Performing a cmake Build with Ninja */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

Starting from TDE version R14.0.11, the package cmake-trinity is mandatory prior to building, this package includes the required macros for the build.

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build with Ninja====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=$PREFIX/lib
export MANDIR=$PREFIX/man
export TQTDIR=$PREFIX/tqt3
export PATH=$TQTDIR/bin:$PREFIX/bin:$PATH
export LD_LIBRARY_PATH=$LIBDIR:$LIBDIR/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:$LIBDIR/pkgconfig:$TQTDIR/lib/pkgconfig:$PKG_CONFIG_PATH
# for lib64:
# export LIBDIRSUFFIX=64
#
from the Trinity module:
mkdir -p build && cd build
cmake -G "Ninja" \
-DCMAKE_EXPORT_COMPILE_COMMANDS="ON" \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_SKIP_RPATH="OFF" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL="ON" \
-DWITH_ALL_OPTIONS="ON" ..
cmake --build . -- -v

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-09T22:21:00Z

Cethyel: /* Performing a cmake Build with Ninja */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

Starting from TDE version R14.0.11, the package cmake-trinity is mandatory prior to building, this package includes the required macros for the build.

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build with Ninja====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=$PREFIX/lib
export MANDIR=$PREFIX/man
export TQTDIR=$PREFIX/tqt3
export PATH=$TQTDIR/bin:$PREFIX/bin:$PATH
export LD_LIBRARY_PATH=$LIBDIR:$LIBDIR/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:$LIBDIR/pkgconfig:$TQTDIR/lib/pkgconfig:$PKG_CONFIG_PATH
# for lib64:
# export LIBDIRSUFFIX=64
#
from the Trinity module:
mkdir -p build && cd build
cmake -G "Ninja" \
-DCMAKE_EXPORT_COMPILE_COMMANDS="ON" \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_SKIP_RPATH="OFF" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL="ON" \
-DWITH_ALL_OPTIONS="ON" ..
cmake --build . -- VERBOSE=1

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-09T22:18:58Z

Cethyel: /* Performing a cmake Build with Ninja */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

Starting from TDE version R14.0.11, the package cmake-trinity is mandatory prior to building, this package includes the required macros for the build.

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build with Ninja====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=$PREFIX/lib
export MANDIR=$PREFIX/man
export TQTDIR=$PREFIX/tqt3
export PATH=$TQTDIR/bin:$PREFIX/bin:$PATH
export LD_LIBRARY_PATH=$LIBDIR:$LIBDIR/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:$LIBDIR/pkgconfig:$TQTDIR/lib/pkgconfig:$PKG_CONFIG_PATH
# for lib64:
# export LIBDIRSUFFIX=64

from the Trinity module:
mkdir -p build && cd build
cmake -G "Ninja" \
-DCMAKE_EXPORT_COMPILE_COMMANDS="ON" \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_SKIP_RPATH="OFF" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL="ON" \
-DWITH_ALL_OPTIONS="ON" ..
cmake --build . -- VERBOSE=1

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-09T22:12:18Z

Cethyel: /* Performing a cmake Build with Ninja */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

Starting from TDE version R14.0.11, the package cmake-trinity is mandatory prior to building, this package includes the required macros for the build.

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build with Ninja====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=$PREFIX/lib
export MANDIR=$PREFIX/man
export TQTDIR=$PREFIX/tqt3
export PATH=$TQTDIR/bin:$PREFIX/bin:$PATH
export LD_LIBRARY_PATH=$LIBDIR:$LIBDIR/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:$LIBDIR/pkgconfig:$TQTDIR/lib/pkgconfig:$PKG_CONFIG_PATH

from the Trinity module:
mkdir -p build && cd build
cmake -G "Ninja" \
-DCMAKE_EXPORT_COMPILE_COMMANDS="ON" \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_SKIP_RPATH="OFF" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL="ON" \
-DWITH_ALL_OPTIONS="ON" ..
cmake --build . -- VERBOSE=1

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-09T22:07:47Z

Cethyel: /* Performing a cmake Build */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

Starting from TDE version R14.0.11, the package cmake-trinity is mandatory prior to building, this package includes the required macros for the build.

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build with Ninja====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=$PREFIX/lib
export MANDIR=$PREFIX/man
export TQTDIR=$PREFIX/tqt3
export PATH=$TQTDIR/bin:$PREFIX/bin:$PATH
export LD_LIBRARY_PATH=$LIBDIR:$LIBDIR/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:$LIBDIR/pkgconfig:$TQTDIR/lib/pkgconfig:$PKG_CONFIG_PATH

from the Trinity module:
mkdir -p build && cd build
cmake -G "Ninja" \
-DCMAKE_EXPORT_COMPILE_COMMANDS="ON" \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_VERBOSE_MAKEFILE="ON" \
-DCMAKE_SKIP_RPATH="OFF" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL="ON" \
-DWITH_ALL_OPTIONS="ON" ../
cmake --build .

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-09T21:50:02Z

Cethyel: /* Performing a cmake Build */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

Starting from TDE version R14.0.11, the package cmake-trinity is mandatory prior to building, this package includes the required macros for the build.

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export TQTDIR=$PREFIX/tqt3
export PATH=$TQDIR/bin:$PREFIX/bin:$PATH
export LD_LIBRARY_PATH=$PREFIX/lib:$PREFIX/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:$PREFIX/lib/pkgconfig:$TQTDIR/lib/pkgconfig:$PKG_CONFIG_PATH

cmake path/to/trinity/module \
-DCMAKE_EXPORT_COMPILE_COMMANDS="ON" \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_VERBOSE_MAKEFILE="ON" \
-DCMAKE_SKIP_RPATH="OFF" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL="ON" \
-DWITH_ALL_OPTIONS="ON"
make

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-09T21:35:44Z

Cethyel: /* Performing a cmake Build */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

Starting from TDE version R14.0.11, the package cmake-trinity is mandatory prior to building, this package includes the required macros for the build.

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/tqt3
export PATH=/opt/trinity/tqt3/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/tqt3/lib/pkgconfig:$PKG_CONFIG_PATH

cmake path/to/trinity/module \
-DCMAKE_EXPORT_COMPILE_COMMANDS="ON" \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_VERBOSE_MAKEFILE="ON" \
-DCMAKE_SKIP_RPATH="OFF" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL="ON" \
-DWITH_ALL_OPTIONS="ON"
make

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-09T20:56:51Z

Cethyel: /* Building Packages with cmake */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

Starting from TDE version R14.0.11, the package cmake-trinity is mandatory prior to building, this package includes the required macros for the build.

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--disable-debug"
export DEBUG_CMAKE_OPT=""

cmake path/to/trinity/module \
-DCMAKE_C_FLAGS:STRING="$CPUOPTIONS" \
-DCMAKE_CXX_FLAGS:STRING="$CPUOPTIONS $DEBUG_CMAKE_OPT" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL=ON
make VERBOSE=1

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-09T20:43:28Z

Cethyel: /* Basic Building Requirements */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.12 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. g++ from the GNU Compiler Collection is the most usual, the current GIT version of Trinity has been tested
against versions up to and including 4.6. clang++ is also supported.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--disable-debug"
export DEBUG_CMAKE_OPT=""

cmake path/to/trinity/module \
-DCMAKE_C_FLAGS:STRING="$CPUOPTIONS" \
-DCMAKE_CXX_FLAGS:STRING="$CPUOPTIONS $DEBUG_CMAKE_OPT" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL=ON
make VERBOSE=1

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

How to Build TDE Core Modules

2021-06-07T20:33:42Z

Cethyel: /* Suggested Build Order */

[[Category:Documentation]]
[[Category:Installation]]
[[Category:Developers]]
This HowTo provides detailed notes and explanations for building the Trinity Desktop Environment base
packages.

==Introduction and Requirements==

===Basic Building Requirements===

Individual Linux distributions might have different build requirements. If these are known they will be available
on the Distribution Specific Builds page.

There is an ongoing effort to convert the build process from autotools to cmake. Until the cmake conversion is
complete, both cmake and autotools are needed to build Trinity packages. cmake 2.8.4 or more recent is expected
when building with cmake.

To build the packages still using autotools, you will need a standard autotools setup (automake, autoconf, etc.)

You'll also need a C++ compiler. GCC/G++ is the most usual, and the current GIT version of Trinity has been tested
against versions up to and including 4.6.

===Other Requirements===

(NOTE: List compiled from old QT3/kdelibs/kde-base ebuilds--will someone please check these?)

Most of the non-build-related mandatory dependencies for the core Trinity packages are pretty basic:

*an X server
*openssl
*fontconfig
*freetype
*ghostscript
*xdg support
*libpng
*libmng

If your Linux distribution came with any kind of graphical environment at all, you should already have
this stuff.

To build tdepim, you will also need libical (standard on many distros).

See Additional Functionality for a list of optional dependencies and what they enable.

===About QT3===

Trinity uses the QT3 widget toolkit. Since Trolltech, the original owners, dropped support for QT3
several years ago, the Trinity Project has taken over QT3's maintenance. In other words, we're now
QT3 upstream, and you should be obtaining your QT3 sources from the Trinity package tarballs or GIT repository.

The version of QT3 used with Trinity 3.5.13 and later incorporates numerous patches. If you're trying to
use an old QT3/KDE3 packaging build setup for your distribution with Trinity's QT3, don't be too surprised
if some patches don't apply. Unless the patch is distribution-specific, chances are that it's been added
to the main source tree.

===About libart===

libart-lgpl is another dependency package that the Trinity Project has taken over after it was
[https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4 dropped] by its original maintainer, because
it needed several [http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1bb837a09f8b84bf6e49ec patches]
to prevent crashes. The version of libart provided by the Trinity Project includes those patches and is
intended to be a replacement for any version of libart currently installed by any distro. Build this patched version
of libart and replace the stock libart installed with the distro.

===Coexisting with QT4/KDE4===

Trinity is intended to be able to run on computers that also have KDE4 installed. Originally, a lot of
Trinity applications had the same names as their KDE4 counterparts, which was problematic. All of
those have been renamed. In general, this was accomplished by changing the old KDE "K" prefix to a
"T" ("kwin" -> "twin"). Applications that don't match anything currently part of KDE4 have retained their
old names.

To avoid stepping on KDE4's toes, we ''strongly'' suggest picking a specific subdirectory prefix to install Trinity
to--the one used in these directions is $PREFIX=/opt/trinity.

==Preparing the Source==

To use the release tarballs, just untar them somewhere.

To live dangerously and use the GIT sources, read [[Notes on GIT Sources]] first.

==Building==

===Suggested Build Order===

A lot of the Trinity core packages depend on one another (in particular, everything depends on tdelibs).
Follow this build order to prevent problems.

Start with the required core packages:

#tqt3 (replaces Qt3; Qt3 without the tqtinterface layer remains available)
#cmake-trinity
#tqtinterface
#arts
#dbus-tqt
#dbus-1-tqt
#tqca-tls (Recommended but required for some applications, such as the Kopete OTR add-on)
#libart-lgpl
#avahi-tqt (Recommended but required when supporting DNS discovery services)
#tdelibs
#tdebase

At this point, you should have a functioning TDE desktop with basic utilities (terminal, file manager,
text/source editors, etc.) If you're going to build tdebindings and want Python support available,
continue with the Python linking packages (or skip over them if you don't care about Python support):

#sip4-tqt
#python-tqt
#pytdeextensions
#python-trinity
#tqscintilla

The following build order seems to work well for the remaining core packages when building the stable release.
You don't have to install everything, though, unless you're packaging TDE for your distribution--pick the packages
that suit your use case.

#tdebindings
#tdeaccessibility
#tdeutils
#tdemultimedia
#tdenetwork
#tdeadmin
#tdeartwork
#tdegames
#tdetoys
#tdeedu
#tdegraphics
#tdepim
#tdesdk (Build tdesdk after installing tdepim. tdepim provides libkcal (bugzilla) hooks for tdesdk.)
#tdevelop (Build tdevelop after tdesdk. tdesdk provides cvs support for tdevelop.)
#tdeaddons

Once that's done, you may want to add [[How to Build Extra Applications|some extra applications]] on top.

===Building Packages with cmake===

====List of Packages Building with cmake====

cmake is the newer, easier, and more maintainable build system the Trinity Project is in the process of porting TDE source to.

The list of modules maintained as an [https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/9 issue #9 in the TGW] indicates which core and dependency packages have already been converted, and their autotools build scripts are no longer maintained. Some other packages are in the process of conversion, but do not have complete cmake build scripts yet. Build everything not in the list above with autotools.

Read the notes section below for individual package requirements before trying to build anything.

====Performing a cmake Build====

The command listing below is only an example. You will wish to edit the exports if your distribution
puts things in unusual locations or if you wish to install to somewhere other than /opt/trinity (tqtinterface
has special requirements--see the Notes). Not all exports will be needed on all systems.

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--disable-debug"
export DEBUG_CMAKE_OPT=""

cmake path/to/trinity/module \
-DCMAKE_C_FLAGS:STRING="$CPUOPTIONS" \
-DCMAKE_CXX_FLAGS:STRING="$CPUOPTIONS $DEBUG_CMAKE_OPT" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DBUILD_ALL=ON
make VERBOSE=1

====Notes====

*Until the cmake migration is fully completed, tqtinterface should be built to install with a $PREFIX of /usr rather than /opt/trinity, even if you are installing everything else to /opt/trinity.

*tqtinterface requires the following additional QT-related build option:

-DQT_VERSION=3

*arts and tdelibs execute compiled binaries as part of the build process. Therefore they need to have -DCMAKE_SKIP_RPATH="OFF" set. All other modules do not need the RPATH set.

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux-g++-64 (rather than linux-g++ (notice the dash!))

*If class constructor issues surface during the build, please post the error to the trinity-users list.

===Building Packages with Autoconf===

====Introduction====

If the package you're trying to build is on the list of those that will build with cmake, try that first, because
its autotools files will be unmaintained, bit-rotted, and possibly outright broken.

Please read the notes section below for individual package requirements before trying to build anything.

For those packages that still need to be built with autotools, the following steps must be run for each affected
Trinity module, including tarball snapshots.

====Regenerate Autoconf/Automake files====

cd to the desired module to build, then run:

cp -Rp <path to your system's libtool.m4 file> admin/libtool.m4.in
cp -Rp <path to your system's ltmain.sh file> admin/ltmain.sh
make -f admin/Makefile.common

====Configure and Build====

export PREFIX=/opt/trinity
export SYSCONFDIR=/etc/trinity
export LIBDIR=/opt/trinity/lib
export MANDIR=/opt/trinity/man
export QTDIR=/opt/trinity/lib/qt3-3.3.8.d
export PATH=/opt/trinity/qt3-3.3.8.d/bin:/opt/trinity/bin:$PATH
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/qt3-3.3.8.d/lib/pkgconfig:$PKG_CONFIG_PATH
# Enable only one of the following:
# export DEBUG_AUTOTOOL_OPT="--enable-debug=full"
export DEBUG_AUTOTOOL_OPT="--disable-debug"

CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
$DEBUG_AUTOTOOL_OPT

View the Distribution Specific Builds page for additional configure options.

====Notes====

*Certain modules will not build across multiple cores in parallel. That is, with a "make -j" flag set to anything greater than 1. These packages are:
**tdebindings (some people have no problems with this package and parallel processing)
**tdemultimedia (some people have no problems with this package and parallel processing)

*Not well documented anywhere, but when building with automake several packages need the --enable-closure configure option:
**tdeaccessibility
**tdeaddons
**tdeadmin
**tdebindings
**tdeedu
**tdegames
**tdemultimedia
**tdesdk

*When building on 64-bit, the following (T)Qt3 configuration option might need to be explicitly declared in some distro build scripts:

-platform linux=g++-64 (rather than linux-g++ (notice the dash!))

===Build Times===

Building Trinity requires time and patience. Build times vary. Here are some guidelines from building
Trinity 3.5.12 on a dual core 2.3 GHz AM2 with 4GB of RAM, using tmpfs, 7200 rpm SATA II hard drives;
with Amarok, Firefox, Konsole, Konqueror, Kate, and other various apps often running concurrently. Compile
times will be faster without such overhead, but likely will be longer when building with support package hooks.
Packages using cmake will build faster than those still stuck on autotools.

*tqtinterface: 2 minutes
*arts: 4 minutes
*tdelibs: 44 minutes
*tdebase: 33 minutes
*tdebindings: 36 minutes
*tdeaccessibility: 5 minutes
*tdeutils: 8 minutes
*tdemultimedia: 24 minutes
*tdenetwork: 23 minutes
*tdeadmin: 4 minutes
*tdeartwork: 3 minutes
*tdegames: 8 minutes
*tdetoys: 2 minutes
*tdeedu: 15 minutes
*tdegraphics: 17 minutes
*tdesdk: 14 minutes
*tdevelop: 27 minutes
*tdeaddons: 7 minutes
*tdewebdev: 12 minutes
*tdepim: 63 minutes

Approximate total time: 5 hours 51 minutes

Time to a functional system (basic desktop): 1 hour 23 minutes

==Installing==

The command is the same regardless of whether your package was built with cmake or autotools:

make install || exit 1

==Additional Functionality==

Certain Trinity packages gain additional functionality when compiled with additional dependencies available.
Also, we maintain some libraries which provide purely optional functionality.

===Optional Trinity Libraries===

None of these Trinity libraries are required but all provide additional functionality for a variety of packages.
These libraries must be built and installed before any packages using these libraries can take advantage of the
additional functionality.

*libkipi: required by kipi-plugins
*kipi-plugins: several high-end image viewers such as gwenview and digikam
*libkdcraw: several image viewers and graphics apps, such as chalk and digikam
*libkexiv2: several image viewers
*libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
*libtqt-perl: adept add-on
*mlt: not required or supported at this time
*mlt++: not required or supported at this time
*pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
*python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance

===List of Optional Dependencies by Trinity Package===

====tdelibs====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''hspell''' Hebrew spell checking
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format

====tdebase====

*'''avahi''' DNS discovery
*'''avahi-tqt''' Trinity TQt layer for avahi, available in Trinity libraries
*'''krb5''' Kerberos authentication
*'''openexr''' EXR image format
*'''GraphicsMagick''' image filters

====tdebindings====

*'''Ruby'''
*'''JRE''' Java Runtime Environment
*'''JDK''' Java Development Kit
*'''Python'''
*'''python-trinity''', available in Trinity libraries
*'''pytdeextensions''', available in Trinity libraries

====tdeutils====

*'''xmms''' multimedia player (superkaramba)

====tdemultimedia====

*'''cdparanoia''' digital audio extraction tool (kaudiocreator)
*'''speex''' an audio compression format designed for speech

====tdenetwork====

*'''xmms''' multimedia player (kopete plugins)
*'''ortp''' real-time transport protocol stack under GPL (kopete plugins)
*'''speex''' audio compression format designed for speech (kopete plugins)

====tdeedu====

*'''facile''' functional constraint library (kalzium)
*'''ocaml''' A programming language (kalzium)
*'''boost''' boost C++ Libraries

====tdevelop====

*'''graphviz''' graph visualization

====tdeaddons====

*'''xmms''' multimedia player (kicker applets)

====tdewebdev====

*'''XSLT''' Extensible Stylesheet Language Transformations
*'''DocBook''' text markup

====tdepim====

*'''krb5''' Kerberos authentication
*'''ortp''' real-time transport protocol stack under GPL (kopete)
*'''gnokii''' Nokia mobile phone support
*'''opensync''' data synchronization support
*'''libcaldav''' online calendar support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)
*'''libcarddav''' online address book support, available through Trinity web site (http://www.trinitydesktop.org/relatedprojects.php)

==Quirks and Known Bugs==

===Building Sip===

Sip is available on many/most distros. Sip requires Qt3 to build, but won't build on TQt3, which adds
the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro
maintainers. All of the python-*-tqt-* packages need Sip to build. Build this TQt3 compatible version of Sip
and replace the stock Sip installed with the distro.

===OpenGL and nVidia===

Building many Trinity and related packages depend upon OpenGL, such as
tdegraphics, k3b, koffice, tdenetwork, gwenview, digikam, etc.;

as well as dependency packages such as
libkipi, libkdcraw, libkexiv2, avahi, etc.

If any of those packages are built when the proprietary nvidia drivers are installed, the dependent package will fail to build
with an error about /usr/lib/libGL.la.

That file is installed by the proprietary nvidia package. When building for personal use only, then building those packages with nvidia installed will pose no harm.

When building packages for other users then build the entire suite of packages in a "clean" generic OpenGL environment.

Other users might not use the proprietary nvidia package. This is true of any package that has OpenGL dependencies.

===Tdeartwork and xhack Screensavers===

Before building tdeartwork, install any and all xhack screensavers that might be uses, then

cd <tdeartwork>/kscreensaver/kxsconfig/
./update_hacks.sh

This will generate the TDE bindings required to allow installed screensavers show up in the Trinity
screensaver control panel, along with their configuration options. When adding a new screensaver the
update_hacks command needs to be rerun and tdeartwork recompiled/reinstalled. Distribution maintainers should
install all available screensavers from their distribution and then run update_hacks during the initial build
setup when building redistributable binary packages (see the Debian tdeartwork build scripts in GIT for an
example of how to do this).

===Poppler Support in Tdegraphics===

Building tdegraphics with poppler support requires building a Trinity poppler-tqt support package. With
many distros poppler no longer is built with Qt3 support. The Trinity poppler-tqt provides the necessary hooks for
tdegraphics without rebuilding poppler. The poppler-tqt dependency sources are located in the tdegraphics/kfile-plugins
dependencies directory and are built automatically with the tdegraphics build option -DWITH_PDF=ON.

===Tdesvn/Tdesdk svn-kio Conflict===

tdesvn and tdesdk provide conflicting files for svn-kio services. Neither package is a dependency of the other.
When tdesdk or tdesvn will be installed without the other, then no change is required. When both tdesdk and tdesvn
are to be installed, then to avoid filesystem conflicts the following files must be removed from one of the packages
before installing:

/opt/trinity/share/services/svn+file.protocol
/opt/trinity/share/services/svn+http.protocol
/opt/trinity/share/services/svn+https.protocol
/opt/trinity/share/services/svn+ssh.protocol
/opt/trinity/share/services/svn.protocol

Since tdesvn uses the ksvn kio exclusively, while tdesdk uses the svn kio, consider removing the conflicting files
from tdesdk to eliminate the same services relying on multiple kio service files.

RedHat Trinity Repository Installation Instructions

2021-05-02T20:02:08Z

Cethyel: /* 2. Download and install the configuration package for your distribution: */

==RedHat Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install EPEL repository: http://fedoraproject.org/wiki/EPEL

Install RPMFUSION repository: http://rpmfusion.org/Configuration

===2. Download and install the configuration package for your distribution:===

====For RHEL/CentOS 6 (R14.0.10)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el6/trinity-r14/RPMS/noarch/trinity-repo-14.0.10-1.el6.noarch.rpm</nowiki>

====For RHEL/CentOS 7 (R14.0.10)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el7/trinity-r14/RPMS/noarch/trinity-repo-14.0.10-1.el7.noarch.rpm</nowiki>

====For RHEL/CentOS 8 (R14.0.10)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el8/trinity-r14/RPMS/noarch/trinity-repo-14.0.10-1.el8.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Installing the minimum, basic desktop (about 200 MB disk space required):

yum install trinity-tdebase

Installing the entire Trinity desktop (about 600 MB disk space required):

yum install trinity-desktop

Installing the entire Trinity desktop + all Trinity supported applications (about 1200 MB disk space required):

yum install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

yum install trinity-tde-i18n-French

Koffice translations:

yum install trinity-koffice-i18n-French

K3B translations:

yum install trinity-k3b-i18n-French

Note: you can obtain a list of available TDE packages with the following command:

yum search trinity-

===5. (Optional) Sets TDM as the default display manager===

====For RHEL / CentOS 6====

Edit or create file: /etc/sysconfig/desktop
Add/modify the line:

DISPLAYMANAGER=/opt/trinity/bin/tdm

Save the file then reboot your computer.

====For RHEL / CentOS 7 and 8====

You must disable your current Display Manager in systemd.
E.g:
systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service

Then enable TDM service:
systemctl enable tdm.service

Then reboot your computer.

===7. (Optional) Install missing XINE codecs===

By default, the Xine libraries provided with RHEL/CentOS cannot play some formats like MPEG1/MPEG2.
As a result, Kaffeine cannot playback video DVD (among other problems).
In order to add the missing codecs, you must install the "xine-lib-extra-freeworld" package, by typing the following command.

====For CentOS 6 (i686):====

<nowiki>yum install http://li.nux.ro/download/nux/dextop/el6/i386/xine-lib-extras-freeworld-1.1.18.1-1.el6.nux.i686.rpm</nowiki>

====For CentOS 6 (x86_64):====

<nowiki>yum install http://li.nux.ro/download/nux/dextop/el6/x86_64/xine-lib-extras-freeworld-1.1.18.1-1.el6.nux.x86_64.rpm</nowiki>

Fedora Trinity Repository Installation Instructions

2021-05-01T18:10:14Z

Cethyel: /* 2. Download the repo configuration file corresponding to your distribution (as root user) */

==Fedora Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install RPMFUSION repository: [http://rpmfusion.org/Configuration http://rpmfusion.org/Configuration]

===2. Download the repo configuration file corresponding to your distribution (as root user)===

====For Fedora 32 (R14.0.10)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f32/trinity-r14/RPMS/noarch/trinity-repo-14.0.10-1.fc32.noarch.rpm</nowiki>

====For Fedora 33 (R14.0.10)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f33/trinity-r14/RPMS/noarch/trinity-repo-14.0.10-1.fc33.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Choose one of the following scenarios.

Install the minimalistic Trinity Desktop Environment:

dnf install trinity-tdebase

Install the entire Trinity Desktop Environment, without applications:

dnf install trinity-desktop

Install the entire Trinity Desktop Environment, with all applications:

dnf install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

dnf install trinity-tde-i18n-French

Koffice translations:

dnf install trinity-koffice-i18n-French

K3B translations:

dnf install trinity-k3b-i18n-French

Gwenview translations (all languages):

dnf install trinity-gwenview-i18n

Note: you can obtain a list of available TDE packages with the following command:

dnf search trinity-

===5. (Optional) Sets TDM as the default display manager===

You must disable your current DM (e.g. KDM, GDM, XDM ...) service and then enable the TDM service.

systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service
systemctl disable lightdm.service
systemctl disable lxdm.service
systemctl enable tdm.service

Then reboot your computer.

Category:Developers

2021-03-20T03:15:13Z

Cethyel:

This category contains development-related and API documentation for the Trinity Desktop Environment.

==Building and Distributing Trinity==

[[Nightly Builds|Installing Nightly Builds]]

[[How to Build TDE Core Modules]]

[[How to Build Extra Applications]]

[[Package Building QA Check List]]

==Developing for Trinity==

[[TDE Gitea Workspace]]

[[TDE Weblate Translation Workspace]]

[[Project GIT Information]]

[[Project RoadMap]]

[[DevelopmentSpecifications]]

===Tutorials and Documentation for QT and TQT===

[[Understanding the TQT Interface]]

[https://www.trinitydesktop.org/docs/qt3 QT3 API Documentation]

[https://www.trinitydesktop.org/docs/qt4 QT4 API Documentation]

[https://www.trinitydesktop.org/docs/qt4/porting4.html Qt3 to Qt4 porting guide]

===Tutorials and Documentation for Trinity===

[https://www.trinitydesktop.org/docs/trinity/index.html Trinity API Documentation]

[[Sample Applications]]

===Tutorials and Documentation for KDE3===

Information in this section should be used with care, as it was not written for the current version of Trinity. However, much of it still applies. If you know of any other interesting KDE3 documentation or tutorials, please add them to this section.

[http://api.kde.org/3.5-api/kdelibs-apidocs/index.html KDE 3.5 API Reference]

The original API reference, at kde.org

[[KDE3 Architecture]]

The architecture pages detail how everything was originally supposed to fit together. Ported from the KDE wiki.

[[KDE3 Tutorials]]

On everything from using kdevelop to writing dcop-aware applications to creating window themes. Ported from the KDE wiki.

[[KDE3 Filesystem Hierarchy]]

Ported from the KDE wiki and verified against a working KDE3 instance.

[http://www.kde.org/info/requirements/3.5.php KDE3 Compilation Requirements]

Mandatory and optional packages for building KDE3, most of which are still used by Trinity.

[[Building KDE 3.5]]

Build instructions for using the pre-cmake system.

===GUI Programming with Python: QT Edition===

Boudewijn Rempt - Copyright © 2001 by Commandprompt, Inc

The main topic of this book is [http://nclairon.free.fr/documentation/pyqt/book1.htm application development using PyQt.]

Fedora Trinity Repository Installation Instructions

2021-03-03T12:53:27Z

Cethyel: /* 2. Download the repo configuration file corresponding to your distribution (as root user) */

==Fedora Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install RPMFUSION repository: [http://rpmfusion.org/Configuration http://rpmfusion.org/Configuration]

===2. Download the repo configuration file corresponding to your distribution (as root user)===

====For Fedora 30 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f30/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.fc30.noarch.rpm</nowiki>

====For Fedora 31 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f31/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.fc31.noarch.rpm</nowiki>

====For Fedora 32 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f32/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.fc32.noarch.rpm</nowiki>

====For Fedora 33 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f33/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.fc33.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Choose one of the following scenarios.

Install the minimalistic Trinity Desktop Environment:

dnf install trinity-tdebase

Install the entire Trinity Desktop Environment, without applications:

dnf install trinity-desktop

Install the entire Trinity Desktop Environment, with all applications:

dnf install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

dnf install trinity-tde-i18n-French

Koffice translations:

dnf install trinity-koffice-i18n-French

K3B translations:

dnf install trinity-k3b-i18n-French

Gwenview translations (all languages):

dnf install trinity-gwenview-i18n

Note: you can obtain a list of available TDE packages with the following command:

dnf search trinity-

===5. (Optional) Sets TDM as the default display manager===

You must disable your current DM (e.g. KDM, GDM, XDM ...) service and then enable the TDM service.

systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service
systemctl disable lightdm.service
systemctl disable lxdm.service
systemctl enable tdm.service

Then reboot your computer.

Fedora Trinity Repository Installation Instructions

2021-03-03T12:49:51Z

Cethyel: /* For Fedora 31 (R14.0.9) */

==Fedora Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install RPMFUSION repository: [http://rpmfusion.org/Configuration http://rpmfusion.org/Configuration]

===2. Download the repo configuration file corresponding to your distribution (as root user)===

====For Fedora 30 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f30/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.fc30.noarch.rpm</nowiki>

====For Fedora 31 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f31/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.fc31.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Choose one of the following scenarios.

Install the minimalistic Trinity Desktop Environment:

dnf install trinity-tdebase

Install the entire Trinity Desktop Environment, without applications:

dnf install trinity-desktop

Install the entire Trinity Desktop Environment, with all applications:

dnf install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

dnf install trinity-tde-i18n-French

Koffice translations:

dnf install trinity-koffice-i18n-French

K3B translations:

dnf install trinity-k3b-i18n-French

Gwenview translations (all languages):

dnf install trinity-gwenview-i18n

Note: you can obtain a list of available TDE packages with the following command:

dnf search trinity-

===5. (Optional) Sets TDM as the default display manager===

You must disable your current DM (e.g. KDM, GDM, XDM ...) service and then enable the TDM service.

systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service
systemctl disable lightdm.service
systemctl disable lxdm.service
systemctl enable tdm.service

Then reboot your computer.

RedHat Trinity Repository Installation Instructions

2021-03-03T12:43:43Z

Cethyel: /* For RHEL/CentOS 8 (R14.0.9) */

==RedHat Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install EPEL repository: http://fedoraproject.org/wiki/EPEL

Install RPMFUSION repository: http://rpmfusion.org/Configuration

===2. Download and install the configuration package for your distribution:===

====For RHEL/CentOS 6 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el6/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.el6.noarch.rpm</nowiki>

====For RHEL/CentOS 7 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el7/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.el7.noarch.rpm</nowiki>

====For RHEL/CentOS 8 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el8/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.el8.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Installing the minimum, basic desktop (about 200 MB disk space required):

yum install trinity-tdebase

Installing the entire Trinity desktop (about 600 MB disk space required):

yum install trinity-desktop

Installing the entire Trinity desktop + all Trinity supported applications (about 1200 MB disk space required):

yum install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

yum install trinity-tde-i18n-French

Koffice translations:

yum install trinity-koffice-i18n-French

K3B translations:

yum install trinity-k3b-i18n-French

Note: you can obtain a list of available TDE packages with the following command:

yum search trinity-

===5. (Optional) Sets TDM as the default display manager===

====For RHEL / CentOS 6====

Edit or create file: /etc/sysconfig/desktop
Add/modify the line:

DISPLAYMANAGER=/opt/trinity/bin/tdm

Save the file then reboot your computer.

====For RHEL / CentOS 7====

You must disable your current Display Manager in systemd.
E.g:
systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service

Then enable TDM service:
systemctl enable tdm.service

Then reboot your computer.

===7. (Optional) Install missing XINE codecs===

By default, the Xine libraries provided with RHEL/CentOS cannot play some formats like MPEG1/MPEG2.
As a result, Kaffeine cannot playback video DVD (among other problems).
In order to add the missing codecs, you must install the "xine-lib-extra-freeworld" package, by typing the following command.

====For CentOS 6 (i686):====

<nowiki>yum install http://li.nux.ro/download/nux/dextop/el6/i386/xine-lib-extras-freeworld-1.1.18.1-1.el6.nux.i686.rpm</nowiki>

====For CentOS 6 (x86_64):====

<nowiki>yum install http://li.nux.ro/download/nux/dextop/el6/x86_64/xine-lib-extras-freeworld-1.1.18.1-1.el6.nux.x86_64.rpm</nowiki>

RedHat Trinity Repository Installation Instructions

2021-03-03T12:41:27Z

Cethyel: /* For RHEL/CentOS 7 (R14.0.9) */

==RedHat Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install EPEL repository: http://fedoraproject.org/wiki/EPEL

Install RPMFUSION repository: http://rpmfusion.org/Configuration

===2. Download and install the configuration package for your distribution:===

====For RHEL/CentOS 6 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el6/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.el6.noarch.rpm</nowiki>

====For RHEL/CentOS 7 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el7/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.el7.noarch.rpm</nowiki>

====For RHEL/CentOS 8 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/el8/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.el8.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Installing the minimum, basic desktop (about 200 MB disk space required):

yum install trinity-tdebase

Installing the entire Trinity desktop (about 600 MB disk space required):

yum install trinity-desktop

Installing the entire Trinity desktop + all Trinity supported applications (about 1200 MB disk space required):

yum install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

yum install trinity-tde-i18n-French

Koffice translations:

yum install trinity-koffice-i18n-French

K3B translations:

yum install trinity-k3b-i18n-French

Note: you can obtain a list of available TDE packages with the following command:

yum search trinity-

===5. (Optional) Sets TDM as the default display manager===

====For RHEL / CentOS 6====

Edit or create file: /etc/sysconfig/desktop
Add/modify the line:

DISPLAYMANAGER=/opt/trinity/bin/tdm

Save the file then reboot your computer.

====For RHEL / CentOS 7====

You must disable your current Display Manager in systemd.
E.g:
systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service

Then enable TDM service:
systemctl enable tdm.service

Then reboot your computer.

===7. (Optional) Install missing XINE codecs===

By default, the Xine libraries provided with RHEL/CentOS cannot play some formats like MPEG1/MPEG2.
As a result, Kaffeine cannot playback video DVD (among other problems).
In order to add the missing codecs, you must install the "xine-lib-extra-freeworld" package, by typing the following command.

====For CentOS 6 (i686):====

<nowiki>yum install http://li.nux.ro/download/nux/dextop/el6/i386/xine-lib-extras-freeworld-1.1.18.1-1.el6.nux.i686.rpm</nowiki>

====For CentOS 6 (x86_64):====

<nowiki>yum install http://li.nux.ro/download/nux/dextop/el6/x86_64/xine-lib-extras-freeworld-1.1.18.1-1.el6.nux.x86_64.rpm</nowiki>

RedHat Trinity Repository Installation Instructions

2021-03-03T12:39:50Z

Cethyel: /* For RHEL/CentOS 6 (R14.0.7) */

==RedHat Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install EPEL repository: http://fedoraproject.org/wiki/EPEL

Install RPMFUSION repository: http://rpmfusion.org/Configuration

===2. Download and install the configuration package for your distribution:===

====For RHEL/CentOS 6 (R14.0.9)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/el6/trinity-r14/RPMS/noarch/trinity-repo-14.0.9-1.el6.noarch.rpm</nowiki>

====For RHEL/CentOS 7 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/el7/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.el7.noarch.rpm</nowiki>

====For RHEL/CentOS 8 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/trinity/rpm/el8/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.el8.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Installing the minimum, basic desktop (about 200 MB disk space required):

yum install trinity-tdebase

Installing the entire Trinity desktop (about 600 MB disk space required):

yum install trinity-desktop

Installing the entire Trinity desktop + all Trinity supported applications (about 1200 MB disk space required):

yum install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

yum install trinity-tde-i18n-French

Koffice translations:

yum install trinity-koffice-i18n-French

K3B translations:

yum install trinity-k3b-i18n-French

Note: you can obtain a list of available TDE packages with the following command:

yum search trinity-

===5. (Optional) Sets TDM as the default display manager===

====For RHEL / CentOS 6====

Edit or create file: /etc/sysconfig/desktop
Add/modify the line:

DISPLAYMANAGER=/opt/trinity/bin/tdm

Save the file then reboot your computer.

====For RHEL / CentOS 7====

You must disable your current Display Manager in systemd.
E.g:
systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service

Then enable TDM service:
systemctl enable tdm.service

Then reboot your computer.

===7. (Optional) Install missing XINE codecs===

By default, the Xine libraries provided with RHEL/CentOS cannot play some formats like MPEG1/MPEG2.
As a result, Kaffeine cannot playback video DVD (among other problems).
In order to add the missing codecs, you must install the "xine-lib-extra-freeworld" package, by typing the following command.

====For CentOS 6 (i686):====

<nowiki>yum install http://li.nux.ro/download/nux/dextop/el6/i386/xine-lib-extras-freeworld-1.1.18.1-1.el6.nux.i686.rpm</nowiki>

====For CentOS 6 (x86_64):====

<nowiki>yum install http://li.nux.ro/download/nux/dextop/el6/x86_64/xine-lib-extras-freeworld-1.1.18.1-1.el6.nux.x86_64.rpm</nowiki>

KDE3 Tutorials

2020-11-28T17:40:01Z

Cethyel: /* Scripting and Application Automation */

[[Category:Developers]]
[[Category:KDE3]]
[[Category:Tutorials]]

Note: Some of these tutorials are only available from the Wayback Machine. Attempts have been made to link to the last viable version, but if the document spanned multiple pages, they may not all have been crawled on that date. We apologize for the inconvenience.

====Getting Started====
Anatomy of a Simple KDE3 Designer Application: [https://www.codeproject.com/Articles/27460/Anatomy-of-a-Simple-KDE-Designer-Application] A complete beginners guide to a KDE3 application.

KDE3 programming tutorial using KDevelop: [http://www.dazzle.plus.com/linux/KDE3/index.htm] A programming tutorial by Richard Crook.

[[Qt Designer and KDevelop 3.0 for Beginners]] [http://women.kde.org/articles/tutorials/kdevelop3/index.html (Original Link--now dead)]: Qt is the toolkit used by the KDE project for developing graphical applications. Currently, translations are available through the original link. This paper, written by Anne-Marie Mahfouf, shows a beginner how to create a simple application using Qt Designer 3 and KDevelop 3. This tutorial is based on an application written by Jono Bacon and has been reviewed by Daniel Molkentin (for the KDevelop 2 version) and Thomas Nagy. Translations to German, Russian, French, Italian, and Romanian available at the original site. Brought to you by KDE-Women.

[http://devel-home.kde.org/~larrosa/tutorial/index.html KDE 3.0 Tutorial]: An excellent tutorial by KDE developer Antonio Larrosa Jiménez leading you from nothing to a fairly full featured web browser. Highly recommended for KDE 3.0 developers.

[[Programming Tutorial for KDE 3]]

[[Makefile.am HOWTO]]: Make the KDE 3 build system work for you. This HOWTO shows you how to do most anything you would need to do to get your application to compile and install

====Components and Plugins====

[http://web.archive.org/web/20110131141802/http://developer.kde.org/documentation/tutorials/xmlui/preface.html KDE User Interface Tutorial (XML GUI)]: Tutorial by KDE developer Kurt Granroth showing how to convert an existing KDE application to use the new XML based user interface builder.

[http://web.archive.org/web/20041123015635/http://www-106.ibm.com/developerworks/linux/edu/l-dw-linuxkp1-i.html Creating KParts Components]: Tutorial on IBM DeveloperWorks, by David Faure shows developers how to create KParts components, under KDE 2 and KDE 3.

[http://web.archive.org/web/20100305214125/http://developer.kde.org/documentation/tutorials/developing-a-plugin-structure/index.html Developing a Plugin Structure for a KDE Application]: This tutorial will take you through all the steps needed to write a plugin structure, plus plugins for your KDE application.

[http://web.archive.org/web/20081222231818/http://developer.kde.org/documentation/tutorials/kfile-plugin/t1.html Providing file meta-data support with KFile plugins]: Tutorial by Brad Hards that describes how to write a meta-data plugin for your favourite file format. It is presented as an example based tutorial.

[http://web.archive.org/web/20100806144422/http://developer.kde.org/documentation/tutorials/components/index.html Embedded Components Tutorial]: Tutorial by KDE developer Kurt Granroth showing how to convert an existing KDE application into a component suitable for embedding in Konqueror.

[[How to write Kontact plugins]]

[http://web.archive.org/web/20110407033422/http://developer.kde.org/documentation/other/kcm_howto.html KConfig Module HOWTO]: A small tutorial about writing a module for the KDE Control Center.

[[Using the KDE dock widget]]: Tutorial for creating widgets that dock to other widgets.

[[Introduction to Get Hot New Stuff]]: An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.

====File Access with KIO====

[http://web.archive.org/web/20080921201511/http://www.heise.de/ct/english/01/05/242/ KIO Tutorial] [http://www.heise.de/ct/artikel/Allesfresser-284884.html (German version)]: Tutorial by KDE developers Carsten Pfeiffer and Stephan Kulow for the c't Magazine, giving an introduction into the KDE IO Architecture and an example KIO Slave.

[http://developer.kde.org/documentation/design/kde/ioslaves/index.html Using IOSlaves]: IOSlaves are the subprocesses KDE uses to fetch remote files without blocking the user interface. This document discusses how they work and how to use them. (Somewhat dated, but might still be useful).

====Scripting and Application Automation====

[http://web.archive.org/web/20100126055754/http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface]: This tutorial shows you how to create a DCOP interface to a KDE application.

[https://www.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP]: IBM DeveloperWorks tutorial, shows how to use kdcop and dcop with several examples such as instantly messaging a contact in kopete when he comes online, and also how to create a simple DCOP-aware application.

====Misc.====

[http://www.usermode.org/docs/kwintheme.html KWin decoration styles]: Tutorial on creating decoration plugins for the KWin window manager (KDE 3.2 and later).

[[Creating Konqueror Service Menus]]: This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").

[[KMDI Tutorial]]: Creating a Multi-Document Interface program using the KMDI library and KDevelop.

[[TDE DBus Tutorial]]: Automatically generate and use dbus interfaces, publish services.

KDE3 Tutorials

2020-11-22T17:35:56Z

Cethyel:

[[Category:Developers]]
[[Category:KDE3]]
[[Category:Tutorials]]

Note: Some of these tutorials are only available from the Wayback Machine. Attempts have been made to link to the last viable version, but if the document spanned multiple pages, they may not all have been crawled on that date. We apologize for the inconvenience.

====Getting Started====
Anatomy of a Simple KDE3 Designer Application: [https://www.codeproject.com/Articles/27460/Anatomy-of-a-Simple-KDE-Designer-Application] A complete beginners guide to a KDE3 application.

KDE3 programming tutorial using KDevelop: [http://www.dazzle.plus.com/linux/KDE3/index.htm] A programming tutorial by Richard Crook.

[[Qt Designer and KDevelop 3.0 for Beginners]] [http://women.kde.org/articles/tutorials/kdevelop3/index.html (Original Link--now dead)]: Qt is the toolkit used by the KDE project for developing graphical applications. Currently, translations are available through the original link. This paper, written by Anne-Marie Mahfouf, shows a beginner how to create a simple application using Qt Designer 3 and KDevelop 3. This tutorial is based on an application written by Jono Bacon and has been reviewed by Daniel Molkentin (for the KDevelop 2 version) and Thomas Nagy. Translations to German, Russian, French, Italian, and Romanian available at the original site. Brought to you by KDE-Women.

[http://devel-home.kde.org/~larrosa/tutorial/index.html KDE 3.0 Tutorial]: An excellent tutorial by KDE developer Antonio Larrosa Jiménez leading you from nothing to a fairly full featured web browser. Highly recommended for KDE 3.0 developers.

[[Programming Tutorial for KDE 3]]

[[Makefile.am HOWTO]]: Make the KDE 3 build system work for you. This HOWTO shows you how to do most anything you would need to do to get your application to compile and install

====Components and Plugins====

[http://web.archive.org/web/20110131141802/http://developer.kde.org/documentation/tutorials/xmlui/preface.html KDE User Interface Tutorial (XML GUI)]: Tutorial by KDE developer Kurt Granroth showing how to convert an existing KDE application to use the new XML based user interface builder.

[http://web.archive.org/web/20041123015635/http://www-106.ibm.com/developerworks/linux/edu/l-dw-linuxkp1-i.html Creating KParts Components]: Tutorial on IBM DeveloperWorks, by David Faure shows developers how to create KParts components, under KDE 2 and KDE 3.

[http://web.archive.org/web/20100305214125/http://developer.kde.org/documentation/tutorials/developing-a-plugin-structure/index.html Developing a Plugin Structure for a KDE Application]: This tutorial will take you through all the steps needed to write a plugin structure, plus plugins for your KDE application.

[http://web.archive.org/web/20081222231818/http://developer.kde.org/documentation/tutorials/kfile-plugin/t1.html Providing file meta-data support with KFile plugins]: Tutorial by Brad Hards that describes how to write a meta-data plugin for your favourite file format. It is presented as an example based tutorial.

[http://web.archive.org/web/20100806144422/http://developer.kde.org/documentation/tutorials/components/index.html Embedded Components Tutorial]: Tutorial by KDE developer Kurt Granroth showing how to convert an existing KDE application into a component suitable for embedding in Konqueror.

[[How to write Kontact plugins]]

[http://web.archive.org/web/20110407033422/http://developer.kde.org/documentation/other/kcm_howto.html KConfig Module HOWTO]: A small tutorial about writing a module for the KDE Control Center.

[[Using the KDE dock widget]]: Tutorial for creating widgets that dock to other widgets.

[[Introduction to Get Hot New Stuff]]: An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.

====File Access with KIO====

[http://web.archive.org/web/20080921201511/http://www.heise.de/ct/english/01/05/242/ KIO Tutorial] [http://www.heise.de/ct/artikel/Allesfresser-284884.html (German version)]: Tutorial by KDE developers Carsten Pfeiffer and Stephan Kulow for the c't Magazine, giving an introduction into the KDE IO Architecture and an example KIO Slave.

[http://developer.kde.org/documentation/design/kde/ioslaves/index.html Using IOSlaves]: IOSlaves are the subprocesses KDE uses to fetch remote files without blocking the user interface. This document discusses how they work and how to use them. (Somewhat dated, but might still be useful).

====Scripting and Application Automation====

[http://web.archive.org/web/20100126055754/http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface]: This tutorial shows you how to create a DCOP interface to a KDE application.

[http://www-106.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP]: IBM DeveloperWorks tutorial, shows how to use kdcop and dcop with several examples such as instantly messaging a contact in kopete when he comes online, and also how to create a simple DCOP-aware application.

====Misc.====

[http://www.usermode.org/docs/kwintheme.html KWin decoration styles]: Tutorial on creating decoration plugins for the KWin window manager (KDE 3.2 and later).

[[Creating Konqueror Service Menus]]: This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").

[[KMDI Tutorial]]: Creating a Multi-Document Interface program using the KMDI library and KDevelop.

[[TDE DBus Tutorial]]: Automatically generate and use dbus interfaces, publish services.

KDE3 Tutorials

2020-11-22T17:24:36Z

Cethyel:

[[Category:Developers]]
[[Category:KDE3]]
[[Category:Tutorials]]

Note: Some of these tutorials are only available from the Wayback Machine. Attempts have been made to link to the last viable version, but if the document spanned multiple pages, they may not all have been crawled on that date. We apologize for the inconvenience.

====Getting Started====
KDE3 programming tutorial using KDevelop: [http://www.dazzle.plus.com/linux/KDE3/index.htm] A programming tutorial by Richard Crook.

[[Qt Designer and KDevelop 3.0 for Beginners]] [http://women.kde.org/articles/tutorials/kdevelop3/index.html (Original Link--now dead)]: Qt is the toolkit used by the KDE project for developing graphical applications. Currently, translations are available through the original link. This paper, written by Anne-Marie Mahfouf, shows a beginner how to create a simple application using Qt Designer 3 and KDevelop 3. This tutorial is based on an application written by Jono Bacon and has been reviewed by Daniel Molkentin (for the KDevelop 2 version) and Thomas Nagy. Translations to German, Russian, French, Italian, and Romanian available at the original site. Brought to you by KDE-Women.

[http://devel-home.kde.org/~larrosa/tutorial/index.html KDE 3.0 Tutorial]: An excellent tutorial by KDE developer Antonio Larrosa Jiménez leading you from nothing to a fairly full featured web browser. Highly recommended for KDE 3.0 developers.

[[Programming Tutorial for KDE 3]]

[[Makefile.am HOWTO]]: Make the KDE 3 build system work for you. This HOWTO shows you how to do most anything you would need to do to get your application to compile and install

====Components and Plugins====

[http://web.archive.org/web/20110131141802/http://developer.kde.org/documentation/tutorials/xmlui/preface.html KDE User Interface Tutorial (XML GUI)]: Tutorial by KDE developer Kurt Granroth showing how to convert an existing KDE application to use the new XML based user interface builder.

[http://web.archive.org/web/20041123015635/http://www-106.ibm.com/developerworks/linux/edu/l-dw-linuxkp1-i.html Creating KParts Components]: Tutorial on IBM DeveloperWorks, by David Faure shows developers how to create KParts components, under KDE 2 and KDE 3.

[http://web.archive.org/web/20100305214125/http://developer.kde.org/documentation/tutorials/developing-a-plugin-structure/index.html Developing a Plugin Structure for a KDE Application]: This tutorial will take you through all the steps needed to write a plugin structure, plus plugins for your KDE application.

[http://web.archive.org/web/20081222231818/http://developer.kde.org/documentation/tutorials/kfile-plugin/t1.html Providing file meta-data support with KFile plugins]: Tutorial by Brad Hards that describes how to write a meta-data plugin for your favourite file format. It is presented as an example based tutorial.

[http://web.archive.org/web/20100806144422/http://developer.kde.org/documentation/tutorials/components/index.html Embedded Components Tutorial]: Tutorial by KDE developer Kurt Granroth showing how to convert an existing KDE application into a component suitable for embedding in Konqueror.

[[How to write Kontact plugins]]

[http://web.archive.org/web/20110407033422/http://developer.kde.org/documentation/other/kcm_howto.html KConfig Module HOWTO]: A small tutorial about writing a module for the KDE Control Center.

[[Using the KDE dock widget]]: Tutorial for creating widgets that dock to other widgets.

[[Introduction to Get Hot New Stuff]]: An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.

====File Access with KIO====

[http://web.archive.org/web/20080921201511/http://www.heise.de/ct/english/01/05/242/ KIO Tutorial] [http://www.heise.de/ct/artikel/Allesfresser-284884.html (German version)]: Tutorial by KDE developers Carsten Pfeiffer and Stephan Kulow for the c't Magazine, giving an introduction into the KDE IO Architecture and an example KIO Slave.

[http://developer.kde.org/documentation/design/kde/ioslaves/index.html Using IOSlaves]: IOSlaves are the subprocesses KDE uses to fetch remote files without blocking the user interface. This document discusses how they work and how to use them. (Somewhat dated, but might still be useful).

====Scripting and Application Automation====

[http://web.archive.org/web/20100126055754/http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface]: This tutorial shows you how to create a DCOP interface to a KDE application.

[http://www-106.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP]: IBM DeveloperWorks tutorial, shows how to use kdcop and dcop with several examples such as instantly messaging a contact in kopete when he comes online, and also how to create a simple DCOP-aware application.

====Misc.====

[http://www.usermode.org/docs/kwintheme.html KWin decoration styles]: Tutorial on creating decoration plugins for the KWin window manager (KDE 3.2 and later).

[[Creating Konqueror Service Menus]]: This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").

[[KMDI Tutorial]]: Creating a Multi-Document Interface program using the KMDI library and KDevelop.

[[TDE DBus Tutorial]]: Automatically generate and use dbus interfaces, publish services.

KDE3 Tutorials

2020-11-22T17:23:45Z

Cethyel:

[[Category:Developers]]
[[Category:KDE3]]
[[Category:Tutorials]]

Note: Some of these tutorials are only available from the Wayback Machine. Attempts have been made to link to the last viable version, but if the document spanned multiple pages, they may not all have been crawled on that date. We apologize for the inconvenience.

====Getting Started====
[KDE3 programming tutorial using KDevelop]: [http://www.dazzle.plus.com/linux/KDE3/index.htm] A programming tutorial by Richard Crook.

[[Qt Designer and KDevelop 3.0 for Beginners]] [http://women.kde.org/articles/tutorials/kdevelop3/index.html (Original Link--now dead)]: Qt is the toolkit used by the KDE project for developing graphical applications. Currently, translations are available through the original link. This paper, written by Anne-Marie Mahfouf, shows a beginner how to create a simple application using Qt Designer 3 and KDevelop 3. This tutorial is based on an application written by Jono Bacon and has been reviewed by Daniel Molkentin (for the KDevelop 2 version) and Thomas Nagy. Translations to German, Russian, French, Italian, and Romanian available at the original site. Brought to you by KDE-Women.

[http://devel-home.kde.org/~larrosa/tutorial/index.html KDE 3.0 Tutorial]: An excellent tutorial by KDE developer Antonio Larrosa Jiménez leading you from nothing to a fairly full featured web browser. Highly recommended for KDE 3.0 developers.

[[Programming Tutorial for KDE 3]]

[[Makefile.am HOWTO]]: Make the KDE 3 build system work for you. This HOWTO shows you how to do most anything you would need to do to get your application to compile and install

====Components and Plugins====

[http://web.archive.org/web/20110131141802/http://developer.kde.org/documentation/tutorials/xmlui/preface.html KDE User Interface Tutorial (XML GUI)]: Tutorial by KDE developer Kurt Granroth showing how to convert an existing KDE application to use the new XML based user interface builder.

[http://web.archive.org/web/20041123015635/http://www-106.ibm.com/developerworks/linux/edu/l-dw-linuxkp1-i.html Creating KParts Components]: Tutorial on IBM DeveloperWorks, by David Faure shows developers how to create KParts components, under KDE 2 and KDE 3.

[http://web.archive.org/web/20100305214125/http://developer.kde.org/documentation/tutorials/developing-a-plugin-structure/index.html Developing a Plugin Structure for a KDE Application]: This tutorial will take you through all the steps needed to write a plugin structure, plus plugins for your KDE application.

[http://web.archive.org/web/20081222231818/http://developer.kde.org/documentation/tutorials/kfile-plugin/t1.html Providing file meta-data support with KFile plugins]: Tutorial by Brad Hards that describes how to write a meta-data plugin for your favourite file format. It is presented as an example based tutorial.

[http://web.archive.org/web/20100806144422/http://developer.kde.org/documentation/tutorials/components/index.html Embedded Components Tutorial]: Tutorial by KDE developer Kurt Granroth showing how to convert an existing KDE application into a component suitable for embedding in Konqueror.

[[How to write Kontact plugins]]

[http://web.archive.org/web/20110407033422/http://developer.kde.org/documentation/other/kcm_howto.html KConfig Module HOWTO]: A small tutorial about writing a module for the KDE Control Center.

[[Using the KDE dock widget]]: Tutorial for creating widgets that dock to other widgets.

[[Introduction to Get Hot New Stuff]]: An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.

====File Access with KIO====

[http://web.archive.org/web/20080921201511/http://www.heise.de/ct/english/01/05/242/ KIO Tutorial] [http://www.heise.de/ct/artikel/Allesfresser-284884.html (German version)]: Tutorial by KDE developers Carsten Pfeiffer and Stephan Kulow for the c't Magazine, giving an introduction into the KDE IO Architecture and an example KIO Slave.

[http://developer.kde.org/documentation/design/kde/ioslaves/index.html Using IOSlaves]: IOSlaves are the subprocesses KDE uses to fetch remote files without blocking the user interface. This document discusses how they work and how to use them. (Somewhat dated, but might still be useful).

====Scripting and Application Automation====

[http://web.archive.org/web/20100126055754/http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface]: This tutorial shows you how to create a DCOP interface to a KDE application.

[http://www-106.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP]: IBM DeveloperWorks tutorial, shows how to use kdcop and dcop with several examples such as instantly messaging a contact in kopete when he comes online, and also how to create a simple DCOP-aware application.

====Misc.====

[http://www.usermode.org/docs/kwintheme.html KWin decoration styles]: Tutorial on creating decoration plugins for the KWin window manager (KDE 3.2 and later).

[[Creating Konqueror Service Menus]]: This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").

[[KMDI Tutorial]]: Creating a Multi-Document Interface program using the KMDI library and KDevelop.

[[TDE DBus Tutorial]]: Automatically generate and use dbus interfaces, publish services.

Fedora Trinity Repository Installation Instructions

2020-09-28T11:54:15Z

Cethyel: /* 5. (Optional) Sets TDM as the default display manager */

==Fedora Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install RPMFUSION repository: [http://rpmfusion.org/Configuration http://rpmfusion.org/Configuration]

===2. Download the repo configuration file corresponding to your distribution (as root user)===

====For Fedora 30 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f30/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.fc30.noarch.rpm</nowiki>

====For Fedora 31 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f31/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.fc31.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Choose one of the following scenarios.

Install the minimalistic Trinity Desktop Environment:

dnf install trinity-tdebase

Install the entire Trinity Desktop Environment, without applications:

dnf install trinity-desktop

Install the entire Trinity Desktop Environment, with all applications:

dnf install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

dnf install trinity-tde-i18n-French

Koffice translations:

dnf install trinity-koffice-i18n-French

K3B translations:

dnf install trinity-k3b-i18n-French

Gwenview translations (all languages):

dnf install trinity-gwenview-i18n

Note: you can obtain a list of available TDE packages with the following command:

dnf search trinity-

===5. (Optional) Sets TDM as the default display manager===

You must disable your current DM (e.g. KDM, GDM, XDM ...) service and then enable the TDM service.

systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service
systemctl disable lightdm.service
systemctl disable lxdm.service
systemctl enable tdm.service

Then reboot your computer.

Fedora Trinity Repository Installation Instructions

2020-09-28T11:51:59Z

Cethyel: /* 5. (Optional) Sets TDM as the default display manager */

==Fedora Trinity Repository Installation Instructions==
[[Category:Documentation]]
[[Category:Installation]]

===1. Configure the supplementary 3rdparty repositories===

Install RPMFUSION repository: [http://rpmfusion.org/Configuration http://rpmfusion.org/Configuration]

===2. Download the repo configuration file corresponding to your distribution (as root user)===

====For Fedora 30 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f30/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.fc30.noarch.rpm</nowiki>

====For Fedora 31 (R14.0.7)====

<nowiki>rpm -Uvh http://mirror.ppa.trinitydesktop.org/trinity/rpm/f31/trinity-r14/RPMS/noarch/trinity-repo-14.0.7-1.fc31.noarch.rpm</nowiki>

===3. Install the Trinity desktop environment===

Choose one of the following scenarios.

Install the minimalistic Trinity Desktop Environment:

dnf install trinity-tdebase

Install the entire Trinity Desktop Environment, without applications:

dnf install trinity-desktop

Install the entire Trinity Desktop Environment, with all applications:

dnf install trinity-desktop-all

===4. (Optional) Install your locale translation package, e.g for French translation===

dnf install trinity-tde-i18n-French

Koffice translations:

dnf install trinity-koffice-i18n-French

K3B translations:

dnf install trinity-k3b-i18n-French

Gwenview translations (all languages):

dnf install trinity-gwenview-i18n

Note: you can obtain a list of available TDE packages with the following command:

dnf search trinity-

===5. (Optional) Sets TDM as the default display manager===

You must disable your current DM (e.g. KDM, GDM, XDM ...) service and then enable the TDM service.

systemctl disable gdm.service
systemctl disable kdm.service
systemctl disable xdm.service
systemctl disable lightdm.service
systemctl enable tdm.service

Then reboot your computer.