Added a section to BUILD-TDE.sh for cpu optimization.
It only functions for x86 - the build for any other cpu type works as before.
I would think that most people building these packages would be doing so for their own use on the machine where the build takes place, so it makes sense to provide an option to optimize the build for that machine.
Added the cpu option to get-source.sh, tqt3.SlackBuild, and tqca-tls.SlackBuild. Moved setting ARCH from get-source.sh and koffice.SlackBuild into BUILD-TDE.sh where it's used for this new option.
Added a summary of the selected options to the final dialog screen.
Other changes to BUILD-TDE.sh are an internal clean-up, mainly making use of dialog options.
This is the set up script for TDE SlackBuilds on Slackware 14.2 for setting user preferences and options.
\n\n
Source archives must be placed in the 'src' directory or will be downloaded during the build from a geoIP located mirror site.
\n\n
A package build list is created and successfully built and installed packages are removed from that list as the build progresses.
\n\n
US English is the default language and support for additional languages can be added.
\n\n
There is an option to abort the build on the final setup screen - so just run through the options and familiarize yourself with them before an actual build. "\
<\Z2\Zb1\Zn> is the default where the target machine's cpu-type is not known
* for i586 the -mtune= option has been set at i686${I586_MSG:-}
* for x86_64 it is the gcc configured option.
<\Z2\Zb2\Zn> will be the best option for any builds to be installed on this machine or one with an identical cpu-type.
<\Z2\Zb3\Zn> has been included to build packages on this machine for installation on another machine with a known cpu-type, allowing that target machine's cpu instruction set to be fully utilized.
The relationship between -march and -mtune options and their use is detailed in the gcc man page in the section 'Intel 386 and AMD x86-64 Options'.
This is the complete list for tde-i18n - and will also apply for other packages.
\n
Other package sources may not have support for all these additional languages, but they will be included in the build for that package when the translations are included in the source.
\n
If any other translation is included in the package source, it can be added here but won't be supported by TDE.
\n\n
Multiple selections may be made - space separated.
\n\n
Build language packages/support for any of:
\n
\Zb\Z6af ar az be bg bn br bs ca cs csb cy da de el en_GB eo es et eu fa fi fr fy ga gl he hi hr hu is it ja kk km ko lt lv mk mn ms nb nds nl nn pa pl pt pt_BR ro ru rw se sk sl sr sr@Latn ss sv ta te tg th tr uk uz uz@cyrillic vi wa zh_CN zh_TW\Zn
If you can see the two 'y' like characters, then you've probably got
\na suitable terminal font installed and can choose \Zr\Z4\ZbContinue\Zn,
\notherwise choose \Z1A\Zb\Z0scii\Zn.
\n\n
a suitable terminal font installed and can choose \Zr\Z4\ZbUtf-8\Zb\Zn,
otherwise choose \Z1A\Zb\Z0scii\Zn.
<<\Z3\Zb ҷ ɣ\Zn>>
\n\n
$(echo -e "\Zb\Z0A suitable font in a utf8 enabled terminal is needed to display all the extended characters in this list. Liberation Mono in an 'xterm' is known to work. Setting up a 'tty' is not worth the effort.\Zn")
\n\n"\
\Zb\Z0A suitable font in a utf8 enabled terminal is needed to display all the extended characters in this list. Liberation Mono in an 'xterm' is known to work. Setting up a 'tty' is not worth the effort.\Zn
Do you want the build to \Zr\Z4\ZbStop\Zn at a failure or <\Z1C\Zb\Z0ontinue\Zn> to the next SlackBuild?
Build logs are $TMP/'program'-build-log, and configure/cmake error logs will be in $TMP/build/tmp-'program'.
\n\n
A practical build method could be:
\n\n
1] build the \Zb\Zr\Z4R\Znequired packages with the \Zr\Z4\ZbStop\Zn option - if any SlackBuild fails, the temporary files for that build will be kept and the problem can be identified and the build restarted.
\n
Any problems with the build environment will also become apparent here.
\n\n
2]then build other packages with the \Z1C\Zb\Z0ontinue\Zn option which deletes the temporary build files while the successful package builds are completing.
\n
2]then build other packages with the <\Z1C\Zb\Z0ontinue\Zn> option which deletes the temporary build files while the successful package builds are completing.
Any failures here are likely to be related to dependencies not found.
\n\n
3] re-run the build for the failed programs from [2] by re-using the build list and with the \Zr\Z4\ZbStop\Zn option ...
The default with the tqt3 build is to append the TDE lib paths to /etc/ld.so.conf.
\n\n
This means that TDE libs will be at the end of the search path. If the package configuration sets up the search path without using the shell variables set up in this script, those TDE libs will not be used if a library of the same name exists - a conflict which could arise if another DE is installed.
\n\n
If you experience any problems of this nature, then try the \Z1P\Zb\Z0repend\Zn option, which will set up doinst.sh for tqt3 to add the TDE libs paths to the beginning of the search path.
\n\n
Then \Zb\Z2rebuild tqt3\Zn. This build option only applies to that package.
dialog --nocancel --no-shadow --colors --title " Building chalk in koffice " --item-help --checklist \
"\n
dialog --cr-wrap --nocancel --no-shadow --colors --title " Building chalk in koffice " --item-help --checklist \
"
There are three options that can be set up for building the imaging app in koffice.
\n\n
[1] It is called \Zb\Z3chalk\Zn in TDE but is known as \Zb\Z3krita\Zn most other places.
\n\n
[2] .pngs loaded into chalk/krita will crash if it is built with libpng-1.6, but will load if libpng-1.4 is used for the build.
\n
If libpng is chosen here, it will be added to the build list and the package placed in $TMP - not installed. It will then be installed by koffice.SB if the libpng unversioned headers and libs are not linked to libpng14.
\n
The koffice.SB will restore those links to libpng16 when the build has finished or failed.
\n\n
[3] GraphicsMagick will enable an extended range of image formats to be loaded and saved. ImageMagick should be an alternative, but building fails with that, so without GM, the range of supported image formats will be limited.
\n
If GM is chosen here, it will be added to the build list if not already selected or installed."\
30753\
" krita""Set the app name to krita" on "\Zb\Z6 otherwise will be \Zb\Z3chalk\Zn"\
@ -425,12 +443,12 @@ There are three options that can be set up for building the imaging app in koffi
You have chosen to re-use the TDE build list, which now contains only those programs that failed to build.
\n\n
But this script is set to Continue in the event of a failure, which will delete all but the last build record. It will be easier to investigate each failure if the build is stopped when it fails.
\n\n
Do you still want the build to \Zr\Z4\ZbContinue\Zn at a failure
Ray-V
7 years ago