[Kde-bindings] Building QtRuby on MeeGo - any advice?

[Robert Riemann]

Hi Dec,

I would recommend you to not use cmake, but the interactive
ccmake. There you could disable the most options for the initial start
and see how it works.

Robert


On Thursday 05 August 2010 15:53:49 Declan McGrath wrote:
> Cheers Arno,
> 
> I'll try to build QtRuby on MeeGo without QML first tonight and then look
> at rebuilding with QML later - starting with your easiest suggestion
> first. Thanks for the info!
> 
> All the best,
> Dec
> 
> On Thursday 05 August 2010 13:23:20 Arno Rehn wrote:
> > On Thursday 05 August 2010 10:43:26 Declan McGrath wrote:
> > > I take it that I don't need to do anything special to have QML support
> > > enabled out of the box?
> > 
> > Well, the additional QML headers have to be parsed and the classes have
> > to be processed by smokegen. That means that you either have to create a
> > seperate Smoke module for QML (which would be best :)) and load that in
> > QtRuby, or add the QML classes to another Smoke module (like QtGui).
> > The latter is probably easiest for testing, but it won't go into trunk
> > that way.
> > If you still want to try it, just add the QML headers to <kdebindings-
> > root>/smoke/qtgui/qtgui_includes.h and the the QML classes to the
> > 'smokeconfig.xml'  file in the same directory. Re-generate the QtGui
> > smoke lib and it should work .
> 
> _______________________________________________
> Kde-bindings mailing list
> Kde-bindings at kde.org
> https://mail.kde.org/mailman/listinfo/kde-bindings
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-bindings/attachments/20100805/27192587/attachment.sig>