Hi All,
As per the wiki (http://trinitydesktop.org/wiki/bin/view/Developers/HowToBuild), it seems that python-kde3 source has been removed from Trinity. I've therefore built SIP and PyQt from upstream but PyKDE (3.16.7) fails, complaining it can't find kdeversion.h, which doesn't exist on my system (building from git).
Am I doing something stupid? Apologies if this is a stupid question.
Cheers, Mike.
As per the wiki (http://trinitydesktop.org/wiki/bin/view/Developers/HowToBuild), it seems that python-kde3 source has been removed from Trinity. I've therefore built SIP and PyQt from upstream but PyKDE (3.16.7) fails, complaining it can't find kdeversion.h, which doesn't exist on my system (building from git).
Am I doing something stupid? Apologies if this is a stupid question.
The short answer is that kdeversion.h has been renamed to tdeversion.h. :) The longer answer is to browse the mailing list discussions of the past couple of days. I have been asking for clarification on the build process in order to update the wiki.
Hopefully Tim confirms this specific reply, but in a previous statement he said Trinity packages now replace PyQt3 and PyKDE3. Here are my most recent proposed changes for the wiki, which I have not yet posted:
================================================== Recommended build order for Trinity dependencies:
Required: tqt3 (replaces Qt3; Qt3 without the tqtinterface layer is available) tqtinterface arts
Recommended: dbus-tqt (Required for some applications, such ksmserver in kdebase) dbus-1-tqt (Required for some applications, such ksmserver in kdebase) tqca-tls (Required for some applications, such as the Kopete OTR add-on) libart-lgpl (Required by many applications, such as kdelibs, ksvg, kdeartwork-kscreensaver) avahi-tqt (Recommended but required when supporting DNS discovery services) python-tqt (Required for python bindings support) sip4-tqt (Required for building python related bindings for tdebindings) tqscintilla
Libraries:
None are required but all provide additional functionality for a variety of packages. These libraries must be built and installed before any packages using these libraries can take advantage of the additional functionality.
libkipi: required by kipi-plugins kipi-plugins: several high-end image viewers such as gwenview and digikam libkdcraw: several image viewers and graphics apps, such as chalk and digikam libkexiv2: several image viewers libksquirrel: required by ksquirrel libtqt-perl: adept add-on mlt: not required or supported at this time mlt++: not required or supported at this time pytdeextensions: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance python-trinity: replacement for PyQt3 and PyKDE3, and used by apps such as tdebindings and tde-guidance
Notes:
Python-tqt, pytdeextensions, and python-trinity are direct replacements for PyQt3 and PyKDE3. There no longer is any need to build PyQt3 or PyKDE3.
Sip is available on many/most distros. However, Sip requires Qt3 but won't build on TQt3, which adds the tqinterface layer to Qt3. More than likely down the road, Sip will be dumped or moved to Qt4 by distro maintainers. All of the python-*-tqt-* packages need sip to build. Build this TQt3 compatible version of Sip and replace the stock Sip installed with the distro.
libart-lgpl no longer is maintained upstream (https://bugzilla.gnome.org/show_bug.cgi?id=155472#c4) and needs several patches (http://git.trinitydesktop.org/cgit/libart-lgpl/diff/?id=150562b89b645c402f1b...) to avoid crashing some apps. The version of libarts provided by the Trinity Project includes those patches and is intended to be a replacement for any version of libarts currently installed by any distro. Build this patched version of libart and replace the stock libart installed with the distro.
Regarding Third-party/LibreOffice: This folder contains patches that add TDE support to the upstream LibreOffice sources. The patches allow LibreOffice to use Trinity dialog boxes. The patches have not been merged into the upstream LibreOffice GIT tree, but they work just fine as-is when applied to the stock LO sources. Obtaining the advantages of these patches requires rebuilding LibreOffice from sources. ==================================================
Darrell
As per the wiki (http://trinitydesktop.org/wiki/bin/view/Developers/HowToBuild), it seems that python-kde3 source has been removed from Trinity. I've therefore built SIP and PyQt from upstream but PyKDE (3.16.7) fails, complaining it can't find kdeversion.h, which doesn't exist on my system (building from git).
Am I doing something stupid? Apologies if this is a stupid question.
The short answer is that kdeversion.h has been renamed to tdeversion.h. :) The longer answer is to browse the mailing list discussions of the past couple of days. I have been asking for clarification on the build process in order to update the wiki.
Hopefully Tim confirms this specific reply, but in a previous statement he said Trinity packages now replace PyQt3 and PyKDE3. Here are my most recent proposed changes for the wiki, which I have not yet posted:
I did not know you needed confirmation, sorry! ;-)
Yes, from what I can tell all of what you have written is correct. Thanks for handling the Wiki update!
Tim
I did not know you needed confirmation, sorry! ;-)
Didn't NEED confirmation --- just politely hoping you'd pipe in to confirm my explanation. :)
No trouble at all. Work is picking up here so I don't have much free time to work on TDE/monitor the lists, but I try during breaks to chime in. :-)
Tim
On 06/01/2012 17:20, Darrell Anderson wrote:
As per the wiki (http://trinitydesktop.org/wiki/bin/view/Developers/HowToBuild), it seems that python-kde3 source has been removed from Trinity. I've therefore built SIP and PyQt from upstream but PyKDE (3.16.7) fails, complaining it can't find kdeversion.h, which doesn't exist on my system (building from git).
Am I doing something stupid? Apologies if this is a stupid question.
The short answer is that kdeversion.h has been renamed to tdeversion.h. :) The longer answer is to browse the mailing list discussions of the past couple of days. I have been asking for clarification on the build process in order to update the wiki.
Hopefully Tim confirms this specific reply, but in a previous statement he said Trinity packages now replace PyQt3 and PyKDE3. Here are my most recent proposed changes for the wiki, which I have not yet posted:
Thank you for your very detailed response and the information it contained. I decided, after your post to start from scratch (I'm using this as a learning exercise) but even with your info I'm still having problems marrying the QT/TQT thing.
I've installed TQt (qt3-3.5.13.tar.gz source) into /opt/qt, tqtinterface into /usr, dbus-tqt & dbus-1-tqt (both with --prefix /usr), sip4-tqt and tqscintilla.
python-tqt however seems to be confused about what is installed and where. More than likely my configuration that's causing the problem!
Anyway;
'python configure.py' results in 'Error: No TQt libraries could be found in /opt/qt/lib' 'python configure.py -q /usr' results in 'Error: Unable to open /usr/mkspecs/linux-g++/qmake.conf'
etc, etc.
Obviously I don't need to build python-tqt but I would like to get a better understanding of what's going wrong.
Regards, Mike
Thank you for your very detailed response and the information it contained. I decided, after your post to start from scratch (I'm using this as a learning exercise) but even with your info I'm still having problems marrying the QT/TQT thing.
I've installed TQt (qt3-3.5.13.tar.gz source) into /opt/qt, tqtinterface into /usr, dbus-tqt & dbus-1-tqt (both with --prefix /usr), sip4-tqt and tqscintilla.
python-tqt however seems to be confused about what is installed and where. More than likely my configuration that's causing the problem!
Anyway;
'python configure.py' results in 'Error: No TQt libraries could be found in /opt/qt/lib' 'python configure.py -q /usr' results in 'Error: Unable to open /usr/mkspecs/linux-g++/qmake.conf'
etc, etc.
Obviously I don't need to build python-tqt but I would like to get a better understanding of what's going wrong.
First, I am not an expert with building packages. Caveat emptor. :)
In my environment I build everything to install to $PREFIX=/opt/trinity, expect tqtinterface, which I install to $PREFIX=/usr. That means I build qt3 to install to /opt/trinity as well.
In my build scripts I still install all traditional doc files to /usr/doc.
With that said, I notice in my build PyKDE3 script I have the following:
=============================================== # python ./configure.py -h # exit 1
# -h displays the help message # -c concatenates each module's C/C++ source files [default] # -d dir where the PyKDE modules will be installed [default %s] % opt_pykdemoddir # -g always release the GIL (SIP v3.x behaviour) # -i no concatenation of each module's C/C++ source files # -j # splits the concatenated C++ source files into # pieces [default 1] # -k dir the KDE base directory ($PREFIX) # -L dir the library directory name [default lib] ($LIBDIR) # -n dir the directory containing the KDE lib files ($LIBDIR/kde3) # -o dir the directory containing the KDE header files ($PREFIX/include/kde3) # -r generates code with tracing enabled [default disabled] # -u build with debugging symbols # -v dir where the PyKDE .sip files will be installed [default %s] % opt_pykdesipdir # -w turn on KDE deprecated object warnings when compiling [default off] # -z file the name of a file containing command line flags
echo "Running ./configure.py -k $PREFIX -L $LIBDIR -n $LIBDIR -o $PREFIX/include -i" echo "Please be patient." python ./configure.py -k $PREFIX -L $LIBDIR -n $LIBDIR -o $PREFIX/include -i ===============================================
I have not yet started trying to build directly from GIT, but I suspect something similar is needed. I hope this helps. :)
NOTE: To everybody reading the recent discussion about cmake options and quality assurance testing. Only a few people try to build t/kdebindings. This package is a good example of why as a team we need to test and building all packages and not just those we use. I know that t/kdebindings is a bugger, but that is a poor excuse for us as the upstream providers not to fully test. Okay, I'm off my soap box. :)
Darrell
On 08/01/2012 20:11, Darrell Anderson wrote:
Thank you for your very detailed response and the information it contained. I decided, after your post to start from scratch (I'm using this as a learning exercise) but even with your info I'm still having problems marrying the QT/TQT thing.
I've installed TQt (qt3-3.5.13.tar.gz source) into /opt/qt, tqtinterface into /usr, dbus-tqt& dbus-1-tqt (both with --prefix /usr), sip4-tqt and tqscintilla.
python-tqt however seems to be confused about what is installed and where. More than likely my configuration that's causing the problem!
Anyway;
'python configure.py' results in 'Error: No TQt libraries could be found in /opt/qt/lib' 'python configure.py -q /usr' results in 'Error: Unable to open /usr/mkspecs/linux-g++/qmake.conf'
etc, etc.
Obviously I don't need to build python-tqt but I would like to get a better understanding of what's going wrong.
First, I am not an expert with building packages. Caveat emptor. :)
In my environment I build everything to install to $PREFIX=/opt/trinity, expect tqtinterface, which I install to $PREFIX=/usr. That means I build qt3 to install to /opt/trinity as well.
In my build scripts I still install all traditional doc files to /usr/doc.
With that said, I notice in my build PyKDE3 script I have the following:
=============================================== # python ./configure.py -h # exit 1
# -h displays the help message # -c concatenates each module's C/C++ source files [default] # -d dir where the PyKDE modules will be installed [default %s] % opt_pykdemoddir # -g always release the GIL (SIP v3.x behaviour) # -i no concatenation of each module's C/C++ source files # -j # splits the concatenated C++ source files into # pieces [default 1] # -k dir the KDE base directory ($PREFIX) # -L dir the library directory name [default lib] ($LIBDIR) # -n dir the directory containing the KDE lib files ($LIBDIR/kde3) # -o dir the directory containing the KDE header files ($PREFIX/include/kde3) # -r generates code with tracing enabled [default disabled] # -u build with debugging symbols # -v dir where the PyKDE .sip files will be installed [default %s] % opt_pykdesipdir # -w turn on KDE deprecated object warnings when compiling [default off] # -z file the name of a file containing command line flags
echo "Running ./configure.py -k $PREFIX -L $LIBDIR -n $LIBDIR -o $PREFIX/include -i" echo "Please be patient." python ./configure.py -k $PREFIX -L $LIBDIR -n $LIBDIR -o $PREFIX/include -i ===============================================
I have not yet started trying to build directly from GIT, but I suspect something similar is needed. I hope this helps. :)
Hi Darrell,
It didn't help, but thanks anyway. PyKDE3 is obviously significantly different to python-tqt. With python-tqt there is no '-L' configure option and LIBPATH etc seem to be ignored. The '-k' option tells python-tqt to build static libs, the '-n' option relates to TQScintilla headers and the '-o' option to TQScintilla libs.
I shall plod on.
Cheers, Mike.
--
It didn't help, but thanks anyway. PyKDE3 is obviously significantly different to python-tqt. With python-tqt there is no '-L' configure option and LIBPATH etc seem to be ignored. The '-k' option tells python-tqt to build static libs, the '-n' option relates to TQScintilla headers and the '-o' option to TQScintilla libs.
I shall plod on.
Tim,
I know you're busy, but as the various Trinity python related packages are new, we need snippets from your build scripts that can be adapted to all distros. We need that information for all new Trinity packages. :)
Side note: as previously discussed here, as a team we need to improve the wiki with such information for each package. Just a statement/observation --- no finger pointing as we're all busy. :)
We should add a base snippet for building with automake too. I will add that to the main page.
Do we need individual pages for each package or can exceptions and deviations from the base snippets be provided on the same wiki page? For example, I think the -DQT_VERSION=3 cmake option is needed only for tqtinterface.
Darrell
It didn't help, but thanks anyway. PyKDE3 is obviously significantly different to python-tqt. With python-tqt there is no '-L' configure option and LIBPATH etc seem to be ignored. The '-k' option tells python-tqt to build static libs, the '-n' option relates to TQScintilla headers and the '-o' option to TQScintilla libs.
I shall plod on.
Tim,
I know you're busy, but as the various Trinity python related packages are new, we need snippets from your build scripts that can be adapted to all distros. We need that information for all new Trinity packages. :)
Here are all my semi-official build files. Navigate to the module you want information for and open the debian/rules file. http://git.trinitydesktop.org/cgit/tde-packaging/tree/ubuntu/maverick
<snip>
Do we need individual pages for each package or can exceptions and deviations from the base snippets be provided on the same wiki page? For example, I think the -DQT_VERSION=3 cmake option is needed only for tqtinterface.
The organization is up to you; whatever will be clearest to the average user. You are correct about the QT_VERSION cmake option.
Tim
-
Darrell Anderson -
Mike Howard -
Timothy Pearson