Changes

From Studiosg
Jump to navigationJump to search

En/TDE krename (view source)

Revision as of 17:42, 21 December 2016

148 bytes added ,  17:42, 21 December 2016
Page updated to new template
Line 1: Line 1: −
Welcome to Simone Giustetti's wiki pages.
+
{{header_en|title=Building Krename for TDE| keyword={{Template:keyword_en_tde}}| description=Building, installing and configuring a working Krename package for TDE and Slackware Linux | link_page=TDE_krename}}
−
 
  −
 
  −
Languages: '''English''' - [http://www.giustetti.net/wiki/index.php?title=TDE_krename Italiano]
  −
 
  −
----
      
== KRENAME ==
 
== KRENAME ==
−
[[En/trinity_desktop_environment#Applications]]
+
[[En/trinity_desktop_environment#Applications | TDE - Applications]]
    
'''Krename''' is a tool handy to rename file and directory names in one single step. New names can be generated either from scratch or combining parts from the original ones. Moreover it is possible to recur to regular expressions and wildcards when renaming. Krename may prove helpful when it comes to '''rename hundreds of files and directories at once''' for example to reorder photo, book or music file collections and more. '''Krename was ported to KDE 4''', but the release I'll introduce in the article is the '''Trinity Desktop Environment''' compatible one. Were You in need of some Krename 4 functionality, please refer to the official [http://www.krename.net/ project home page].
 
'''Krename''' is a tool handy to rename file and directory names in one single step. New names can be generated either from scratch or combining parts from the original ones. Moreover it is possible to recur to regular expressions and wildcards when renaming. Krename may prove helpful when it comes to '''rename hundreds of files and directories at once''' for example to reorder photo, book or music file collections and more. '''Krename was ported to KDE 4''', but the release I'll introduce in the article is the '''Trinity Desktop Environment''' compatible one. Were You in need of some Krename 4 functionality, please refer to the official [http://www.krename.net/ project home page].
 +
    
== Krename and Slackware ==
 
== Krename and Slackware ==
    
'''No Krename official package was ever distributed along the Slackware releases''' in the years. To obviate the problem the [http://slackbuilds.org Slackbuilds.org] project provides a '''build script''' to consent users in need to obtain a package from the source archive. To build the TDE 3.5.13.2 included Krename release a script was written from scratch following the project rules and conventions:
 
'''No Krename official package was ever distributed along the Slackware releases''' in the years. To obviate the problem the [http://slackbuilds.org Slackbuilds.org] project provides a '''build script''' to consent users in need to obtain a package from the source archive. To build the TDE 3.5.13.2 included Krename release a script was written from scratch following the project rules and conventions:
−
* 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 22: Line 18:     
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
Line 36: Line 37:  
   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 51: Line 54:  
   --disable-rpath \
 
   --disable-rpath \
 
       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 60: Line 64:     
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.krename.net/ Krename home page]
 
* [http://www.krename.net/ Krename home page]
Line 68: Line 74:  
----
 
----
   −
Languages: '''English''' - [http://www.giustetti.net/wiki/index.php?title=TDE_krename Italiano]
+
{{footer_en | link_page=TDE_krename}}
Retrieved from "http://www.giustetti.net/wiki/index.php?title=Special:MobileDiff/859"

Navigation menu