Tim, All,
I'm working forward in the build order after building tdebase, but I'm not sure what should be building and what shouldn't?? The build order I'm trying to follow is:
"dependencies/$useqt" OK 'dependencies/tqtinterface' OK 'dependencies/arts' OK 'dependencies/dbus-tqt' OK 'dependencies/dbus-1-tqt' OK 'dependencies/tqca-tls' OK 'dependencies/libart-lgpl' OK 'dependencies/avahi-tqt' FAILED 'dependencies/libcaldav' OK 'dependencies/libcarddav' OK 'tdelibs' OK 'tdebase' OK 'applications/abakus, ..??' 'tdebindings' 'tdeaccessibility' 'tdeutils' 'tdemultimedia' 'tdenetwork' 'tdeadmin' 'tdeartwork' 'tdegames' 'tdetoys' 'tdeedu' 'tdegraphics' 'tdevelop' 'tdeaddons' 'tdepim' 'tdewebdev' 'tdesdk'
What after tdebase should be ready to build? Also why is everything turned OFF ("Build all" OFF) in the tdegraphics, tdenetwork, etc.. CMakeLists.txt files?
On 03/06/2012 04:35 PM, David C. Rankin wrote: <snip>
What after tdebase should be ready to build? Also why is everything turned OFF ("Build all" OFF) in the tdegraphics, tdenetwork, etc.. CMakeLists.txt files?
I get this part .. packaging: -DBUILD_ALL=ON, but some of the earlier packages didn't like taking -DWITH_... or other options...
I get this part .. packaging: -DBUILD_ALL=ON, but some of the earlier packages didn't like taking -DWITH_... or other options...
I enable BUILD_ALL in all of my build scripts. I want feature rich packages and enabling that option is the only way to expose bugs.
I'll evaluate all build options someday when ever I get around to writing an article to build "Trinity Light."
Darrell
I'm working forward in the build order after building tdebase, but I'm not sure what should be building and what shouldn't?? The build order I'm trying to follow is:
What after tdebase should be ready to build? Also why is everything turned OFF ("Build all" OFF) in the tdegraphics, tdenetwork, etc.. CMakeLists.txt files?
The wiki has a recommended build order. Here is my build order, which follows the wiki pretty close:
Core:
tqt3 or qt3 tqtinterface arts dbus-tqt dbus-1-tqt tqca-tls qca qca-tls libart_lgpl avahi-tqt tdelibs tdebase
Main Suite:
Support for tdebindings: sip tqscintilla python-tqt python-trinity pytdeextensions libtqt-perl tdebindings tdeaccessibility tdeutils tdemultimedia tdeadmin tdenetwork tdeartwork tdegames tdetoys tdeedu tdegraphics tdevelop tdeaddons tdewebdev Webdav support for tdepim: libcaldav libcarddav tdepim tdesdk
Applications:
amarok k3b k9copy gtk-qt-engine ksystemlog kaffeine libkdcraw libkexiv2 libkipi kipi-plugins digikam gwenview knemo ktorrent konversation koffice
Darrell
On 03/06/2012 05:29 PM, Darrell Anderson wrote:
Main Suite:
Support for tdebindings: sip tqscintilla python-tqt python-trinity pytdeextensions libtqt-perl
You are using autotools, etc.. for the remainder that don't have CMake files -- and it's working???
tdebindings tdeaccessibility tdeutils tdemultimedia tdeadmin tdenetwork tdeartwork tdegames tdetoys tdeedu tdegraphics tdevelop tdeaddons tdewebdev Webdav support for tdepim: libcaldav libcarddav tdepim tdesdk
Applications:
amarok k3b k9copy gtk-qt-engine ksystemlog kaffeine libkdcraw libkexiv2 libkipi kipi-plugins digikam gwenview knemo ktorrent konversation koffice
You are using autotools, etc.. for the remainder that don't have CMake files -- and it's working???
Yes, as of last week. :) I haven't performed a full run in the past many days because I am testing several patches affecting XDG support (part of resolving bug report 892). Otherwise, for a long while I have been building everything on my list except the tdebindings support packages and avahi--tqt.
With the automake packages, sometimes I'll use the not-well-known DO_NOT_COMPILE environment variable that is native to KDE/TDE compiling. I will pass that variable at the command line or temporarily in the affected build script to bypass that particular component of the package. For example, in my current tdeadmin build script, I have the following because I can't build tdeadmin against TQt3 (bug report 871):
if [ -r ${PREFIX}/lib/pkgconfig/tqt-mt.pc ] || [ -r /usr/lib/pkgconfig/tqt-mt.pc ]; then export DO_NOT_COMPILE="knetworkconf" fi
With cmake, study each CMakeLists.txt to discover the various component build options. For example, right now, I can't build tdesdk unless I use -DBUILD_KUIVIEWER=OFF (bug report 872).
I hope to run a full build pass soon and will be able to report more about tdegraphics then.
Darrell
On 03/06/2012 06:21 PM, Darrell Anderson wrote:
Yes, as of last week. :) I haven't performed a full run in the past many days because I am testing several patches affecting XDG support (part of resolving bug report 892). Otherwise, for a long while I have been building everything on my list except the tdebindings support packages and avahi--tqt.
With the automake packages, sometimes I'll use the not-well-known DO_NOT_COMPILE environment variable that is native to KDE/TDE compiling. I will pass that variable at the command line or temporarily in the affected build script to bypass that particular component of the package. For example, in my current tdeadmin build script, I have the following because I can't build tdeadmin against TQt3 (bug report 871):
if [ -r ${PREFIX}/lib/pkgconfig/tqt-mt.pc ] || [ -r /usr/lib/pkgconfig/tqt-mt.pc ]; then export DO_NOT_COMPILE="knetworkconf" fi
With cmake, study each CMakeLists.txt to discover the various component build options. For example, right now, I can't build tdesdk unless I use -DBUILD_KUIVIEWER=OFF (bug report 872).
I hope to run a full build pass soon and will be able to report more about tdegraphics then.
Darrell
That is Awesome! I can adapt the Archlinux build scripts based on what you have working and hopefully bring that distro up to par. (Make sure you commit updates to the slackware build scripts to tde-packaging :)
That is Awesome! I can adapt the Archlinux build scripts based on what you have working and hopefully bring that distro up to par. (Make sure you commit updates to the slackware build scripts to tde-packaging :)
Thanks. :)
Just remember when resorting to this type of chicanery and the package builds to file that danged bug report. I hate filing them but when there is no response in this list then there is no other recourse. :)
Other than the two bug reports I mentioned previously, I can build a clean set of full packages against TQt3. I need to start building all of the applications. I can build about a dozen right now without issue. And then there are the tdebindings packages. One of these days....
Darrell
-
Darrell Anderson -
David C. Rankin