SUBMISSION: New Library for kdesupport: indexlib
k1pfeifle at gmx.net
Sun Jun 12 00:41:27 BST 2005
On Saturday 11 June 2005 12:58, Michael Nottebrock wrote:
> We quickly discovered that tinderboxing kdebindings would create about the
> same work for us as the complete rest of KDE, not to mention it would require
> us to build an incredible amount of dependencies to just get there, so we
> didn't bother (most of the KDE language bindings aren't very popular anyway,
> at least in FreeBSD).
This matches my own experience fully.
I never managed to compile kdebindings on my own. Not once! Most of the time
I got different error messages from update to update. And I tried for a long
time, very frequently. My motivation was that it could help me to access an
"easier than C++" way of learning to program for KDE. But man, if the thingie
doesnt build, I'm lost.
First I thought that it is just bad luck, and that the last commits fixed my
last problem but maybe introduced a different one. I tried to dko without
distcc and ccache, I made clean repeatedly. But no luck.
When I asked in #kde-devel/IRC that gave no big motivation: most said they
hadnt compiled kdebindings since very long time "because it never builds"...
I'd stil love to see a well working kdebinding module.
I think the time is maturing quickly were it could be big bonus to have (not
only because of Aarons kicker/plasma effort -- there are people massively going
for non-C++ languages on many fronts to see, and we should be able to utilize
that fresh new blood for KDE).
More information about the kde-core-devel