[Kde-bindings] making smoke/korundum generate bindings for other things?
illissius at gmail.com
Wed Jun 22 18:07:19 UTC 2005
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 =).
Work is punishment for failing to procrastinate effectively.
More information about the Kde-bindings