Yesterday I downloaded a mirror image of the GIT repository. 3.9 GB. :)
I have been updating and revising my build scripts with many obvious things but I suspect the renaming project will throw a few speed bumps into the build process.
The ehterpad has helped some. Yet is there anything specific or generic we need to know? A list of "gotchas"? Environment variables that have not been renamed? Etc.
Darrell
The tdenetwork package has a cmake option -DWITH_SPEEX.
How do I add the specific location of the speex include files? With automake I would add this:
--with-extra-includes=/usr/include/speex
What is the equivalent directive in cmake?
Darrell
A few days ago we discussed rebuilding libarts from the Trinity sources.
Yet I would like clarification about all of the packages in the dependencies and libraries branch. Which are required, which are recommended, and what is an appropriate build order?
Dependencies:
Build order presumed to be as listed (please correct!):
tqt3 or qt3 (is there a reason to build the latter rather than the former?)
tqtinterface (required)
arts (required)
dbus-1-tqt (required?)
dbus-tqt (required?)
tqca-tls (required?)
libart-lgpl (required?/recommended?)
avahi-tqt (recommended?)
python-tqt (recommended?)
sip4-tqt (recommended?)
tqscintilla (recommended?)
Libraries:
Build order: as needed for various packages.
kipi-plugins (recommended? which packages?)
libkdcraw (recommended? which packages?)
libkexiv2 (recommended? which packages?)
libkipi (recommended? which packages?)
libksquirrel (recommended? which packages?)
libtqt-perl (recommended? which packages?)
mlt (recommended? which packages?)
mlt++ (recommended? which packages?)
pytdeextensions (required?/recommended? which packages?)
python-trinity (required?/recommended? which packages?)
Second, are python-tqt, pytdeextensions, and python-trinity direct replacements for PyQt3 and PyKDE3? That is, do we stop building PyQt3 and PyKDE3?
Third, SIP is available on many/most distros. What is sip4-tqt just an add-on layer? When is that package required?
Fourth, seems libart is an oddball package. All of the others are installed but for most distros, libart from Trinity is an update/upgrade package process rather than an install.
Lastly, what is the deal with third-party/libreoffice?
I'll update the wiki as necessary once I'm no longer confused. :)
Thanks!
Darrell
Tim,
I don't know your strategy for this. You know far more than me about these matters. Still, I would like to see all build related patches get merged first before merging usability bug patches.
My reason is now that I have Git synced locally, I have updated all of my build scripts for this new environment. Theoretically, after all the build related patches are merged, I should be able to build all packages without a single patch. That won't immediately fix usability bugs, but will allow everybody to build without issues.
That will be my R14 goal: to build all packages without any patches at all.
If that sounds reasonable, I humbly ask to start in the preferred build order. That is, first merge all qt3 related patches, then tqt patches, then arts, kdelibs, kdebase, etc.
I'm looking forward to the merging!
Thanks Tim!
Darrell
I'm getting my local GIT mirror and build scripts ready for when GIT goes public.
My build scripts extract the version number from tdelibs/tdecore/tdeversion.h. I notice in GIT the TDE_VERSION_STRING define does not match the number of levels. That is, the variable is assigned a value of R14.0 rather than R14.0.0. The variable should be the latter to remain consistent. :)
Darrell
While building packages for arch I noticed that docs instead of going
into /opt/trinity/share/doc/HTML/$LANG go into
/opt/trinity/share/dok/kde/HTML/$LANG. I vaguely remember this was
already discussed on the ML, but I can't seem to find it in the
archive (maybe it wasn't after all, and I dreamed about it). Doing mv
at the end of the package installation process don't seem to me like
solution to the problem, but rather like hack around it.
Slowly, ever so slowly, I'm trying to learn C++. I have this Big Fat Book on my desk and almost every day I read, tinker, and study code.
While trying to compile koffice I ran into these fatal errors:
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::~Parser()'
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::statement() const'
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::parse(QString const&)'
../../.libs/libkexidb.so: undefined reference to `tname(int)'
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::Parser(KexiDB::Connection*)'
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::query()'
If the g++ error lists a line in a *.cpp file, then usually the "undefined reference to" error means a missing header file that declares the namespace or function.
In this particular error, g++ listed a static library. From what I've read, this means something is awry in the linking process and not in the code itself. Am I on the right track?
If not then please set me straight. :)
If yes, then how do I fix the error? I presume something in the Makefiles? Does the error provide me clues as to where I need to fix the problem?
Trying to learn! Thanks!
Darrell
I notice some apps use a stripped or minimal KDialog rather than the full blown KDialog that supports bookmarks and configuration.
Examples include Ark and KFileReplace.
Is there a user way to configure those apps to use the full KDialog? Or does the source code need modification?
Is there a way to search the source code to find which apps use this minimal KDialog?
Darrell
