1,423
edits
Changes
From Studiosg
Jump to navigationJump to searchPage updated to new template
{{header_en|title=Building a Graphics package for TDE| keyword={{Template:keyword_en_tde}}| description=Building, installing and configuring a working Graphics package for TDE and Slackware Linux | link_page=TDE_tdegraphics}}
== TDEGRAPHICS ==
== TDEGRAPHICS ==
[[En/trinity_desktop_environment#Base_Packages]]
[[En/trinity_desktop_environment#Base_Packages | TDE - Base Packages]]
The '''tdegraphics''' package is a collection of graphics related programs and libraries developed for the '''Trinity Desktop Environment'''. Some among the graphical applications are worth mentioning:
The '''tdegraphics''' package is a collection of graphics related programs and libraries developed for the '''Trinity Desktop Environment'''. Some among the graphical applications are worth mentioning:
* '''KSnapshot''': A tool to get snapshots of the entire desktop, of single windows or of some window detail.
* '''KSnapshot''': A tool to get snapshots of the entire desktop, of single windows or of some window detail.
The package is fully optional and '''no TDE functionality will go missing by not installing it'''.
The package is fully optional and '''no TDE functionality will go missing by not installing it'''.
== Tdegraphics and Slackware ==
== Tdegraphics and Slackware ==
The tdegraphics package replaces kdegraphics for KDE 3.5. The build system relies on '''autotools''' and has not been ported to [http://www.cmake.org cmake] yet. The kdegraphics build script can be used for tdegraphics, but some updates and tweaks are due. The following rules were applied when compiling the package to ensure a clean build:
The tdegraphics package replaces kdegraphics for KDE 3.5. The build system relies on '''autotools''' and has not been ported to [http://www.cmake.org cmake] yet. The kdegraphics build script can be used for tdegraphics, but some updates and tweaks are due. The following rules were applied when compiling the package to ensure a clean build:
* Directory '''/opt/trinity''' was set as package root directory.
* Directory ''/opt/trinity'' was set as package root directory.
* Some missing makefiles were created running the '''make''' command from inside the main directory of the code extracted from the source archive.
* Some missing makefiles were created running the '''make''' command from inside the main directory of the code extracted from the source archive.
* The source code '''was patched''' in order to '''solve a version mismatch issue with libtool''': the source code was configured for release 2.2.6, but 2.4.2 is installed along Slackware 14.0.
* The source code '''was patched''' in order to '''solve a version mismatch issue with libtool''': the source code was configured for release 2.2.6, but 2.4.2 is installed along Slackware 14.0.
Some configuration scripts required by the build procedure are missing from the source tarball. We create the makefiles using the make command:
Some configuration scripts required by the build procedure are missing from the source tarball. We create the makefiles using the make command:
<syntaxhighlight lang="bash">
# Prepare the package for building (Create the configure script).
# Prepare the package for building (Create the configure script).
echo "(II) admin makefile run here" >> ${OUTPUT}/${PRGNAM}_configure.log
echo "(II) admin makefile run here" >> ${OUTPUT}/${PRGNAM}_configure.log
make -f admin/Makefile.common \
make -f admin/Makefile.common \
2>&1 | tee -a ${OUTPUT}/${PRGNAM}_configure.log
2>&1 | tee -a ${OUTPUT}/${PRGNAM}_configure.log
</syntaxhighlight>
A patch is needed to solve a '''libtool''' package version mismatch conflict:
A patch is needed to solve a '''libtool''' package version mismatch conflict:
<syntaxhighlight lang="bash">
# Patch the admin/ltmain.sh script in order to solve a version mismatch.
# Patch the admin/ltmain.sh script in order to solve a version mismatch.
patch -p0 -i ${SRCDIR}/ltmain_version_update.patch
patch -p0 -i ${SRCDIR}/ltmain_version_update.patch
</syntaxhighlight>
'''The script specifically sets Qt libraries paths''' in order for other scripts to find them at build time:
'''The script specifically sets Qt libraries paths''' in order for other scripts to find them at build time:
<syntaxhighlight lang="bash">
# Add temporary paths to handle new libraries during build
# Add temporary paths to handle new libraries during build
export QTDIR=/opt/trinity
export QTDIR=/opt/trinity
export LD_LIBRARY_PATH=/usr/lib${LIBDIRSUFFIX}:/opt/trinity/lib${LIBDIRSUFFIX}
export LD_LIBRARY_PATH=/usr/lib${LIBDIRSUFFIX}:/opt/trinity/lib${LIBDIRSUFFIX}
export PKG_CONFIG_PATH=:/usr/lib${LIBDIRSUFFIX}/pkgconfig:/opt/trinity/lib${LIBDIRSUFFIX}/pkgconfig:$PKG_CONFIG_PATH
export PKG_CONFIG_PATH=:/usr/lib${LIBDIRSUFFIX}/pkgconfig:/opt/trinity/lib${LIBDIRSUFFIX}/pkgconfig:$PKG_CONFIG_PATH
</syntaxhighlight>
Finally the script runs the '''./configure''' command to configure source code in accordance to the destination environment:
Finally the script runs the '''./configure''' command to configure source code in accordance to the destination environment:
<syntaxhighlight lang="bash">
# Configure the package
# Configure the package
LDFLAGS="${SLKLDFLAGS}" \
LDFLAGS="${SLKLDFLAGS}" \
--enable-closure \
--enable-closure \
2>&1 | tee -a ${OUTPUT}/${PRGNAM}_configure.log
2>&1 | tee -a ${OUTPUT}/${PRGNAM}_configure.log
</syntaxhighlight>
Once the configuration successfully concludes, the script runs the make command then goes on with packaging the software.
Once the configuration successfully concludes, the script runs the make command then goes on with packaging the software.
External Links
External Links
----
----
* [http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild TDE build guide]
* [http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild TDE build guide]
* [http://www.kde.org/applications/graphics/ Official KDE Graphics page]
* [http://www.kde.org/applications/graphics/ Official KDE Graphics page]
----
----
{{footer_en | link_page=TDE_tdegraphics}}
