[Kde-bindings] compiling kdebindings trunk
Richard Dale
Richard_Dale at tipitina.demon.co.uk
Wed May 24 19:17:13 UTC 2006
On Wednesday 24 May 2006 19:51, Paolo Capriotti wrote:
> On 5/24/06, Richard Dale <Richard_Dale at tipitina.demon.co.uk> wrote:
> > There's no point in doing much with KDE bindings until the KDE 4 api has
> > stabilised - it only makes sense to work on the Qt4 part at the moment.
> > As far as I know the only parts of trunk kdebindings that are being
> > actively developed at the moment are qtruby, kalyptus, and smoke/qt.
>
> I would like to try qyoto, so that I can think of helping the project
> in the near future. Could you tell me which version of smoke is
> required?
The one from trunk kdebindings. Any help with Qyoto would be great, it just
needs a little bit more work to be quite useful.
> Anyway, what's the building procedure for kdebindings? I don't know
> much about the autotool stuff, and the scripts keep complaining with
> strange error messages. I had to set environment variables such
> AUTOCONF=/usr/bin/autoconf
> but the configure script is not created correctly (not all macros get
> expanded). Could someone shed some light on this?
I not sure about the macros. It should be a matter of doing a 'make -f
Makefile.cvs', and configure with a prefix pointing the kde4 kdelibs.
To build trunk kdebindings, you need to check out unsermake from
kde/trunk/kdenonbeta/unsermake and add it to your $PATH environment variable.
The easiest way to build the Smoke library might be to download QtRuby 1.4.5
from here:
http://rubyforge.org/projects/korundum/
That version doesn't need unsermake, only automake/autoconf, and you don't
have to build and install kde4 libs. On the other hand, the configure will
look for ruby, so you'll need to have that installed.
-- Richard
More information about the Kde-bindings
mailing list