Hmmm.. That's what I was doing... Here is the build order I use:
Perform the following on my build script collection:
grep build_package TDE.SlackBuild
You find my build order and whether I use automake or cmake. If you browse TDE.SlackBuild you'll find comments about building certain packages before other packages.
Also perform the following in my unarchived build environment:
find . -maxdepth 3 -name "*.SlackBuild" -exec grep -l "AUTOTOOLS=" {} ;
This will reveal which packages can use either automake or cmake. When the line AUTOTOOLS=true is commented out then the script uses cmake. When not commented out then I still use automake.
There are some partical conversions to cmake. Those respective build scripts I have configured to test either cmake or automake as new cmake patches come forth. I use the AUTOTOOLS=true line to determine which to use. When new patches come forth I uncomment the line and test cmake.
BTW, as Slavek mentioned, in my TDE.SlackBuild you'll notice I have the following comment:
# Build tdegames after tdemultimedia.
Darrell
On 01/21/2014 01:01 PM, Darrell Anderson wrote:
Perform the following on my build script collection:
grep build_package TDE.SlackBuild
You find my build order and whether I use automake or cmake. If you browse TDE.SlackBuild you'll find comments about building certain packages before other packages.
Also perform the following in my unarchived build environment:
find . -maxdepth 3 -name "*.SlackBuild" -exec grep -l "AUTOTOOLS=" {} ;
This will reveal which packages can use either automake or cmake. When the line AUTOTOOLS=true is commented out then the script uses cmake. When not commented out then I still use automake.
There are some partical conversions to cmake. Those respective build scripts I have configured to test either cmake or automake as new cmake patches come forth. I use the AUTOTOOLS=true line to determine which to use. When new patches come forth I uncomment the line and test cmake.
I've been through your treasure trove :), but this type of 'query for' help really helps. I do go though each package.SlackBuild and look/compare how you are building and then go though the CMakeLists.txt (or ./configure --help) info from the package and mix/match the setup I need on Arch, and to get the features I need.
I hardcode my build order using the tde-wiki suggested order, then step through the remain packages. In my build script, I do:
## array of TDE modules to build (source from local GIT tree tarballs) declare -a tbo tbo=("dependencies/$useqt" 'dependencies/tqtinterface' 'dependencies/arts' 'dependencies/dbus-tqt' 'dependencies/dbus-1-tqt' 'dependencies/tqca-tls' 'dependencies/libart-lgpl' 'dependencies/avahi-tqt' 'dependencies/libcaldav' 'dependencies/libcarddav' 'dependencies/sip4-tqt' #10 'dependencies/python-tqt' 'tdelibs' 'tdebase' 'libraries/libksquirrel' 'libraries/libkdcraw' 'libraries/libkexiv2' 'libraries/libkipi' 'libraries/kipi-plugins' 'libraries/mlt' 'libraries/mlt++' #20 'tdebindings' 'tdeaccessibility' 'tdeutils' 'tdemultimedia' 'tdenetwork' 'tdeadmin' 'tdeartwork' 'tdegames' 'tdetoys' 'tdeedu' #30 'tdegraphics' 'tdevelop' 'tdeaddons' 'tdepim' 'tdewebdev' 'applications/abakus' 'applications/amarok' 'applications/dolphin' <snip> ## Quick hack to set build start/stop (note the comments in the array, #20) isint $1 && tbstart=$1 || tbstart=0 isint $2 && test $2 -gt $tbstart && tbstop=$2 || tbstop=83 <snip> ## Main TDE build loop [[ $tbstart -lt $tbstop ]] && echo -e "\nBuilding TDE" [[ $DEP_BUILDALL == OFF ]] && [[ $TDE_BUILDALL == ON ]] && { bu_crpkgs "tde" bu_tdepkgs "tde" } for((tb=${tbstart};tb<${tbstop};tb++)); do tm_mod_start=$(date +%s) cpkg="${tbo[${tb}]}" echo " -> $cpkg" <snip>
So no matter what I'm building, it has to be built in order... (helps keep me straight...)
-
Darrell Anderson -
David C. Rankin