Linked by Thom Holwerda on Tue 1st Dec 2009 19:03 UTC, submitted by poundsmack
Thread beginning with comment 397480
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Does this mean we are going to have to rebuild Qt4-QtRuby again from scratch?
Yes, you may not need to recompile QtRuby when changing to Qt 4.6, but it wouldn't do any harm. It would certainly be a good idea to regenerate and rebuild the smoke bindings libraries that QtRuby uses.
How is this going to affect KDE 4.4?
Well as KDE 4.4 depends on Qt 4.6, and so it means that in can actually be released :-)
As far as QtRuby is concerned, the big change for the KDE 4.4 release will be that the Smoke libraries will be generated with Arno Rehn's C++ based generator, instead of the perl one that previous releases used.
Also the Smoke libs for Qt 4.6 and the corresponding Ruby extensions will be split up so that there is one per Qt module - ie one qtcore, qtgui, qtnetwork etc instead of everything being in a single 'qtruby4' extension. That will mean if you only want to write a ruby app using QtCore stuff it won't pull in all the Gui classes.




Member since:
2007-04-11
This leaves me with 2 questions open to discussion:
Does this mean we are going to have to rebuild Qt4-QtRuby again from scratch?
How is this going to affect KDE 4.4?