[Kde-bindings] making smoke/korundum generate bindings for other things?
Richard_Dale at tipitina.demon.co.uk
Wed Jun 22 18:59:33 UTC 2005
On Wednesday 22 June 2005 20:07, Gábor Lehel wrote:
> how hardwired is smoke/korundum to the existing kdelibs? eg, if I
> wanted to make it generate bindings for kdenonbeta/kcanvas, how hard
> would it be? (and how would I go about it?)
> I tried doing it the 'dumb way' (eg, without trying to figure out how
> any of it actually works) by making a symlink for kdenonbeta/kcanvas
> at kdelibs/kcanvas, and adding all the headers to
> smoke/kde/kde_headers_list, lines for all the classes to
> kalyptus/kalyptusDataDict.pm, and finally adding -lkcanvas to
> smoke/kde/Makefile.am, and it even compiled, but it doesn't seem to
> have actually had any effect (eg, no classes called KDE::Canvas*).
> the reason i want to do this is that kcanvas looks cool and I want to
> play around with it, and playing around is much funner in ruby =).
You don't need to add the classes to kalyptus/kalyptusDataDict.pm, but other
than that what you did should have worked. Is KCanvas in a namespace, is that
It's certainly important to be able to wrap all the kde apis, but the Smoke
library needs to be made more modular to be able to do that. So it might not
be possible until we have a new version of Smoke for KDE 4.
More information about the Kde-bindings