Some time ago we discussed a desire to post at our wiki package-specific information needed for building.
Recently Tim and I ran into an interesting quirk with building on 64-bit. (Thanks Tim!) I decided this information should be in the wiki. If you're curious, the quirk is that for 64-bit, building (T)Qt3 with the following configure option might be needed:
-platform ${PLATFORM}
Where, for 64-bit, ${PLATFORM} == linux-g++-64 rather than linux-g++.
Recent posts by Nix regarding build issues also remind me of this wiki need.
Perhaps the time has arrived that we start accumulating this information for the wiki.
For now, perhaps we share information here in the mail list, which will serve somewhat as a way for providing peer reviews before posting to the wiki.
I'm thinking eventually we have a page for each package, even thos that are quite generic with build configurations. Each wiki page will list no less than minimum build information. For many packages they all will look the same except for the package name. Just cookie-cut information because there is nothing complicated about those packages.
We then move many of our preliminary wiki notes to those package-specific pages.
Currently section 5 of the wiki page is our potential portal to individual package information. We can create links in that section as we create each new wiki page for each package.
All I'm asking for at this point is we start pooling knowledge.
We have a project goal of releasing R14 when ready but are focusing on summer's end. That provides us ample time to assemble this information.
Please help!
Darrell
Tim,
Slackware 13.1
Clean build, previous packages all uninstalled.
I built tqt3, tqtinterface but dbus-tqt fails to build for both 32-bit and 64-bit:
-- checking for one of the modules 'tqt'
CMake Error at cmake/modules/TDEMacros.cmake:23 (message):
#################################################
tmoc is not found!
tqt is correctly installed?
#################################################
From my last full build run a couple of days ago, my dbus-tqt build log shows this:
-- checking for one of the modules 'tqt'
-- tmoc path: /usr/bin/tmoc
-- moc path: /opt/trinity/bin/moc
-- uic path: /opt/trinity/bin/uic
-- tqt-replace path: /usr/bin/tqt-replace
-- Performing Test HAVE_USABLE_TQT
-- Performing Test HAVE_USABLE_TQT - Success
-- Configuring done
I verified that tmoc is installed at /usr/bin/tmoc.
Not sure what changed where, but has to be a recent patch.
Darrell
So my attempted build of kdeaccessibility is failing. The failure is
because of Q_SLOTS: nothing is replacing it with <slots> before
processing by uic, so uic is never putting the slot into the .h file and
compilation is failing.
While tqt-replace fixes this up for projects using CMake, the
corresponding call in am_edit was commented out in July 2010, in this
commit:
commit 4f9a36e2fcee4ecd7adbc3e53c8e6837712c2a35
Author: tpearson <tpearson@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>
Date: Mon Jul 26 02:04:25 2010 +0000
First attempt at getting TQT integrated...
But even with that commented-out tqt-replace call uncommented, it still
doesn't work. If we look at
kaccessibility/kmouth/wordcompletion/Makefile, we see:
all: docs-am all-am
all-am: Makefile $(LIBRARIES)
LIBRARIES = $(noinst_LIBRARIES)
noinst_LIBRARIES = libwordcompletion.a
libwordcompletion.a: $(libwordcompletion_a_OBJECTS) $(libwordcompletion_a_DEPENDENCIES) $(EXTRA_libwordcompletion_a_DEPENDENCIES)
libwordcompletion_a_OBJECTS = $(libwordcompletion_a_nofinal_OBJECTS)
libwordcompletion_a_OBJECTS = $(libwordcompletion_a_nofinal_OBJECTS)
#libwordcompletion_a_OBJECTS = $(libwordcompletion_a_final_OBJECTS)
libwordcompletion_a_final_OBJECTS = libwordcompletion_a.all_cpp.o
and it is the libwordcompletion_a.all_cpp.o rule that has the
tqt-replace call in it.
Thus, this is only going to work if that line is uncommented *and*
--enable-final is passed in. But the Wiki doesn't mention
--enable-final, only --enable-closure!
Unfortunately that *also* doesn't work, and it becomes obvious why Tim
commented that line out -- it's applying to the .cpp files only, but to
be effective tqt-replace must run over the .ui files, before uic gets to
them.
I don't see how this could possibly ever work. Have people actually
managed to compile the non-cmake parts of Trinity in the last little
while?
If so, what configure flags did you use, and could you send me a copy of
kaccessibility/kmouth/wordcompletion/Makefile.in and
kaccessibility/kmouth/wordcompletion/wordcompletionui.{everything but .o
and .lo} after a build? 'cos I am sore confused.
Ditching this whole nightmare and going to cmake is ever such a good
idea! :)
--
NULL && (void)
While finding and testing the various files in the icon themes that needed branding updates, I noticed a sym link named default.kde pointing to crystalsvg. Seems as long as we are trying to catch various branding issues and avoid potential conflicts with KDE, that the sym link should be renamed to default.tde.
Looks like the following apps need nominal patching:
kile
tde-style-qtcurve
kmymoney
tdepim
tdelibs
tdebindings
tdebase (docbook reference)
tde-i18n (docbook references)
Any objections to patching?
Darrell
Has anybody tested exiting Trinity with different icon sets? The exit status dialog image looks great with the crystalsvg icon set.
When used with other icons set the image is KDE rather than TDE. Oops! :-)
Affected icon sets:
kdeclassic
kids
monochrome
slick
Does anybody know which images the exit status dialog grabs so we can update the images?
E. Liddell --- looks like your wonderful art talents will be needed again!
Darrell
So I just tried to migrate to trinity (from trunk as of two days ago,
before the latest round of renaming patches). To keep things neat I'm
sticking the whole thing excepting tqtinterface into a tree rooted at
/usr/trinity/ (henceforward '$trinity_root').
I've built up to tdebase, I've noticed the following build problems
(patches follow fixing those for which fixes seem practical). Non-build
problems are mostly not mentioned here because I haven't restarted into
TDE yet (I want to get more built before then).
- If you install tqtinterface as suggested on the wiki, avahi-tqt
fails to build:
make[2]: Entering directory `/usr/src/kde/trinity/main/dependencies/x86_64-spindle/avahi-tqt'
/usr/trinity/bin/moc moc qt-watch.cpp qt-watch.moc3
TQt meta object compiler
moc: Too many input files specified
This is in part because moc-tqt cannot be found. If we follow the
wiki's instructions and install tqtinterface in /usr, it ends up in a
different place from TQt and the configure-time search for tmoc
fails. Moving tqtinterface into the $trinity_root fixes that, but
then the hardwired -I/usr/include/tqt is wrong and the build fails
again. The only fix I've found is to install tqtinterface into the
$trinity_root, and then symlink /usr/include/tqt to that location.
This is, not to put too fine a point on it, insane.
I note that even if you *do* install tqtinterface into the
$trinity_root, the pkg-config file ends up in ${prefix}/pkgconfig.
This appears to be intentional, but is quite mystifying given that
all you need to do to avoid it is to set PKG_CONFIG_PATH, which must
be set anyway or the build of tqtinterface will fail (because
qt-mt.pc is not in /usr/lib/pkgconfig but rather in
$trinity_root/lib/pkgconfig.)
Is the expectation nowadays that tqt3 is installed in /usr as well,
or is this a bug?
(I don't have a patch for this because I can't think of a non-insane
fix.)
- in konsole, meta is not recognized (only alt is). I have a pre-existing
patch for this ancient KDE problem.
- covariant return type checking is broken, because it's using the C
compiler rather than the C++ compiler :) but even if that is fixed,
the check still fails, because...
- in the cmake FindTQt module, most of the CXXFLAGS are being missed out,
leading to spurious failures in CheckCXXSourceRuns.
Patches for the latter three problems follow (not as a single git patch
series, though, because I can't figure out how to make one of those
crossing multiple submodules: anyone?)
--
NULL && (void)
