I'm able to build tdebindings against
TQt3. Exceptions are qtsharp and xparts but I plan to test
the former today. Yeah, a slight miracle anybody can build
that package. :) (Several patches are needed.)
I plan to further test building against both ruby 1.8.7 and
1.9.1.
As reported in another mail, I can build tdebindings against both ruby 1.8.7 and 1.9.1. I
can build xparts too, but not qtsharp. Although the package builds without failures I
believe the package is nonetheless incomplete. So there remains some work with this
package.
I notice there are directories in tdebindings named
test. I
presume these are test programs and scripts to ensure the
bindings built correctly? Anybody know for sure?
I want to see a tdebindings testing guideline written at the wiki for packagers and
developers to ensure they are building tdebindings correctly. For example, how does a
person know the dcopc bindings built correctly? A C program with dcop calls, probably to
pop up kdialog messages or to change the volume of a media player. Do those test
directories that are part of the package sources do this? When I look at the final
tdebindings binary package I don't see anything obvious to indicate a bin file that
might be a testing tool.
Does anybody have experience with this?
I am willing to write the guideline but need technical help.
Darrell