Difference between revisions of "En/TDE tdenetwork"

From Studiosg
Jump to navigationJump to search
(Added page about Tdenetwork, TDE and Slackware 14.0)
 
(Page updated to new template)
Line 1: Line 1:
Welcome to Simone Giustetti's wiki pages.
+
{{header_en|title=Building a Network package for TDE| keyword={{Template:keyword_en_tde}}| description=Building, installing and configuring a working Network package for TDE and Slackware Linux | link_page=TDE_tdenetwork}}
 
 
 
 
Languages: '''English''' - [http://www.giustetti.net/wiki/index.php?title=TDE_tdenetwork Italiano]
 
 
 
----
 
  
 
== TDENETWORK ==
 
== TDENETWORK ==
[[En/trinity_desktop_environment#Base_Packages]]
+
[[En/trinity_desktop_environment#Base_Packages | TDE - Base Packages]]
  
 
The TDE Network package includes some networking tools and services used by the '''Trinity Desktop Environment'''. Among them are:
 
The TDE Network package includes some networking tools and services used by the '''Trinity Desktop Environment'''. Among them are:
Line 20: Line 15:
 
* '''kwifimanager''': Graphical tool to configure and monitor '''WiFi''' networks.
 
* '''kwifimanager''': Graphical tool to configure and monitor '''WiFi''' networks.
 
Some system daemons are included along the user tools: '''LISa''', a LAN network monitor, some inter PC communication tools as the '''talk''' protocol and more.
 
Some system daemons are included along the user tools: '''LISa''', a LAN network monitor, some inter PC communication tools as the '''talk''' protocol and more.
 +
  
 
== Tdenetwork and Slackware ==
 
== Tdenetwork and Slackware ==
  
 
The tdenetwork package replaces kdenetwork for KDE 3.5. The build system relies on '''autotools''' and has not been ported to [http://www.cmake.org cmake] yet. The kdenetwork build script can be used for tdenetwork, but some updates and tweaks are due. To guarantee a smooth build the following guidelines were followed:
 
The tdenetwork package replaces kdenetwork for KDE 3.5. The build system relies on '''autotools''' and has not been ported to [http://www.cmake.org cmake] yet. The kdenetwork build script can be used for tdenetwork, but some updates and tweaks are due. To guarantee a smooth build the following guidelines were followed:
* 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.
Line 30: Line 26:
  
 
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
A patch is needed to solve a '''libtool''' package version mismatch conflict:  
+
</syntaxhighlight>
 +
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
Line 44: Line 45:
 
   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}" \
Line 60: Line 63:
 
       --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.
  
Line 69: Line 73:
  
 
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://en.wikipedia.org/wiki/Kdenetwork Kde Network Wikipedia page]
 
* [http://en.wikipedia.org/wiki/Kdenetwork Kde Network Wikipedia page]
Line 75: Line 81:
 
----
 
----
  
Languages: '''English''' - [http://www.giustetti.net/wiki/index.php?title=TDE_tdenetwork Italiano]
+
{{footer_en | link_page=TDE_tdenetwork}}

Revision as of 15:13, 21 December 2016

Welcome to Simone Giustetti's wiki pages.


Languages: English - Italiano


TDENETWORK

TDE - Base Packages

The TDE Network package includes some networking tools and services used by the Trinity Desktop Environment. Among them are:

  • kdict: A graphical interface for the DICT protocol able to search in on-line dictionaries.
  • kget: A download manager.
  • knewstickerstub: An applet for the TDE dock able to access on-line news sites.
  • kopete: An instant messaging client supporting many protocols both natively and through plug-ins.
  • kppp: A graphical tool to configure analog modems.
  • krdc: A remote desktop client supporting the RDP and VNC protocols.
  • krfb: A remote desktop client supporting the Remote Frame Buffer protocol.
  • ksirc: The integrated IRC client in TDE.
  • kwifimanager: Graphical tool to configure and monitor WiFi networks.

Some system daemons are included along the user tools: LISa, a LAN network monitor, some inter PC communication tools as the talk protocol and more.


Tdenetwork and Slackware

The tdenetwork package replaces kdenetwork for KDE 3.5. The build system relies on autotools and has not been ported to cmake yet. The kdenetwork build script can be used for tdenetwork, but some updates and tweaks are due. To guarantee a smooth build the following guidelines were followed:

  • 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.
  • 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.

No specific options were used for the configure command as the package seems not to need any. Some script lines of code and related comments follow.

Some configuration scripts required by the build procedure are missing from the source tarball. We create the makefiles using the make command:

   # Prepare the package for building (Create the configure script).
   echo "(II) admin makefile run here" >> ${OUTPUT}/${PRGNAM}_configure.log
   make -f admin/Makefile.common \
      2>&1 | tee -a ${OUTPUT}/${PRGNAM}_configure.log

A patch is needed to solve a libtool package version mismatch conflict:

   # Patch the admin/ltmain.sh script in order to solve a version mismatch.
   patch -p0 -i ${SRCDIR}/ltmain_version_update.patch

The script specifically sets Qt libraries paths in order for other scripts to find them at build time:

   # Add temporary paths to handle new libraries during build
   export QTDIR=/opt/trinity
   export PATH=/opt/trinity/bin:/usr/bin:$PATH
   export LIBDIR=/usr/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

Finally the script runs the ./configure command to configure source code in accordance to the destination environment:

   # Configure the package
   LDFLAGS="${SLKLDFLAGS}" \
   CFLAGS="${SLKCFLAGS}" \
   CXXFLAGS="${SLKCFLAGS}" \
   ../${PRGNAM}-${VERSION}/configure \
      --prefix=${PREFIX} \
      --sysconfdir="/etc/trinity" \
      --libdir=${LIBDIR} \
      --mandir=${PREFIX}/man \
      --with-qt-dir=${QTDIR} \
      --with-qt-includes=${PREFIX}/include \
      --with-qt-libraries=${PREFIX}/lib${LIBDIRSUFFIX} \
      --disable-rpath \
      --enable-closure \
      2>&1 | tee -a ${OUTPUT}/${PRGNAM}_configure.log

Once the configuration successfully concludes, the script runs the make command then goes on with packaging the software.

A full script can be downloaded from the following link. The output package can be installed using command installpkg as usual in Slackware Linux.


For any feedback, questions, errors and such, please e-mail me at studiosg [at] giustetti [dot] net


External Links





Languages: English - Italiano