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