[Aragorn_DSP]

Has anyone been successful with native ezx or qte/qtopia application development in e680i? I have tried something (with e680i (?) headers from the forum) without success (segfault). I tried to compiled t1 tutorial in qte (a simplest demo in qte) - it ran but nothing showed up.

[rpconnect]

What version of qte/qtopia were you using? Were you compiling against the qt-libs in the phone or those built during the qt-embedded build?

The tricky part is getting non-native qt apps to run w/ the native qt-libs, but since the qt-libs in the phone aren't stock this is not a trivial application; at present it seems like cyph's opieproxy app is the best way to run non-native qt apps w/ the native phone apps. I'm sure it could be modified to work w/ stand-alone qtopia apps, but it would require applying a similar patch to the qt-embedded source and if you are using a version different than for the opie stuff (qt-2.3.6) you might have to patch this by hand.

Also, the ezx headers are available for the qt-libs in the e680, but not yet for the e680i, so it is possible to develop agaist the libs in the e680, but not all functionality will be ported to the e680i.

It seems as though any qt dev. for the phone will require some non-standard mods, either to the qt-embedded source (e.g. cyph's method) to get it to work along side the native qt-apps, or modify the calls to the qt embedded functions such that they are compatible w/ the phone's qt-libs (but again, limited to e680 use at this time).

For this type of experimentation i've found the opie option to be the best bet. Starting w/ cyph's package covers the problem of the qt-libs compatibility, and it is fairly easy to build and play around w/ the opie example apps (fairly similar to the example apps that come w/ qtopia) and then include them in your own (modified) opie.cramfs.

i'd still like to see us be able to develop single stand-alone qt apps that run w/out problems on the phone, but having to fight against the non-open qt environment on the phone is more work than i care to go through.

[Aragorn_DSP]

Thank you for the information. I compiled with qt-2.3.6 headers (from the SDK) and and libs from the phone (C5A4P).
For t1 tutorial:

#include <qapplication.h>
#include <qpushbutton.h>

int main( int argc, char **argv )
{
    QApplication a( argc, argv );

    QPushButton hello( "Hello world!", 0 );
    hello.resize( 100, 30 );

    a.setMainWidget( &hello );
    hello.show();
    return a.exec();
}

- using native qt lib at runtime (i.e. via #. /home/native/.profile) and run #./t1 I got a black rectangle w/o any "Hello world!" and w/o any posible interaction using touch screen and /or buttons
- using qt lib from the sdk and run #./t1 : i got in the same thing
For neopop (neogeo pocket emu):
- using native qt lib at runtime (i.e. /home/native/.profile) i got segfault
- using qt lib from the sdk and run #./neopop : UI shown on the screen but the process is not in EZX task manager
I will look for opieproxy for a workaround. Btw, in miniroot.cramfs (from cyph) we have loop.o, so maybe we could mount opie.cramfs as a loop device (so it would not necessary to create a new partition in sd). I have trouble with partitioning my sd

[maxx_730]

Yes that is possible, the partition way was just done because at the time leprechaun put that guide together there were no kernel sources yet so no loopback module.

[Aragorn_DSP]

Thanks. And one important thing is that neither t1 nor neopop shows a caption or label in the buttons etc.