<div dir="ltr">On Fri, Sep 26, 2008 at 6:22 PM, Kelvie Wong <span dir="ltr"><<a href="mailto:kelvie@ieee.org">kelvie@ieee.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
</div>In the meantime, I've managed to get PyQt4 working (hooked up against Qt-x11);<br>
this eliminates the need for a toolchain (or even building apps in general).<br>
There's another thread about that on this list.<br>
<br>
--<br>
<font color="#888888">Kelvie Wong<br>
</font><div></div></blockquote><div><br>That's very nice, Kelvie.<br>I'm still trying to get a working and safe oetree with qt library inside :).<br>The first time i tried with the org.openembedded.dev branch and my typical angstrom configured local.conf file, but it got a compilation error on uicmoc4-native. After that i tried with the fso openmoko conf file, it failed again but i noted that the preferred version of qt4 there was 4.3.3 instead of <a href="http://4.4.1.">4.4.1.</a> I remembered that in org.openembedded.stable there was 4.3.3 version, so i tried again with the stable branch. It compiled fine but did not create all the requested ipk (empty). I managed a bit on the qt_packaging.inc recipie and finally i got a working qt-oe-tree, i was able to compile a my application too. I bitbaked the last fso unstable image and flashed the phone with it, setupped a fake feed server on my oe tree, added it to feeds on the phone and did opkg update, opkg install qt4-x11-free, opkg install my-application, and after that i was able to start it adding a simple DISPLAY=:0.<br>
But i'm not very happy of this as it's not simple and i do not like to mix different branches.<br>Please share your experience on this...<br><br>Regards<br><br> Nicola<br></div></div></div>