>> I can build tdebindings against ruby >> 1.8.7 and 1.9.1 without failure against TQt3. >> >> I thought I'd give qtsharp a whirl. I had to install mono >> and pnet. I received build errors for a lack of libqtc.la. >> >> Looks like that file is part of some kind of Qt C# bindings >> that needs to exist before building tdebindings. The best I >> can tell those bindings no longer exist. >> >> I found old discussion threads that seem to indicate qtsharp >> has been broken and unsupported in (k)tdebindings for many >> years. The configure.in.in (very last line) indicates >> likewise. >> >> The short term solution is to use the DO_NOT_COMPILE option, >> which already exists in configure.in.in. >> >> Building against ruby 1.9.1 requires a set of patches, all >> of which are ruby 1.9.x related. >> >> Building against 1.8.7 required some nominal patching too. >> >> With both there are strange messages that look like >> failures, apparently not fatal, but need attention. I notice >> differences between the older kdebindings binary package and >> the one I build. That tells me some files are not building. >> >> I do not have any of the tdebindings support packages >> installed, which likely makes a difference. > > Here is what I notice is different between TDE and 3.5.10: > > KDE 3.5.10 TDE GIT (4395) > ============================================= > ---------- dcopidl2java > embedjs embedjs > javalib ---------- > jsaccess ---------- > kdepyuic ---------- > kjscmd kjscmd > koala ---------- > krubyinit krubyinit > pylupdate ---------- > pyuic ---------- > qtrubyinit qtrubyinit > rbkconfig_compiler rbkconfig_compiler > rbqtapi rbqtapi > rbqtsh rbqtsh > rbuic rbuic > sip ---------- > ---------- shell_xparthost > ---------- xp_notepad > > pylupdate and pyuic were compiled in 3.5.10 because the 3.5.10 sources > contained copies of the upstream PyQt3. I presume because PyQt3 will not > build against TQt3 that those two apps are now lost to history? > > kdepyuic was compiled in 3.5.10 because the 3.5.10 sources contained > copies of the upstream PyKDE3. Is that app available by building > python-trinity? > > sip was compiled in 3.5.10 because the 3.5.10 sources contained copies of > the upstream sip. Most distros now provide sip separately. > > Remaining mysteries are why javalib, jsaccess, and koala did not build. > Any ideas? > > Darrell PyQt3 and SIP were removed from tdebindings and placed in their own directories to modularize the builds somewhat. IIRC at this point they are in sip4 and python-tqt in GIT. Tim