Creating own native qte apps

[rpconnect]

Hmm.. I don't believe in the QVFb-stuff .

leprechaun: I agree that since we are not using qvfb there is no reason to specify the display as such. (I also get a "Socket not open" error when I try a Qtopia example, when I include the -qws it gets further, but still the "Illegal Instruction")

Can you post the configuration setting you used to compile the libs in qt-2.3.XXX? (e.g. ./configure -qconfig qpe -thread -depths 16,32 -xplatform linux-ipaq-g++ ...), thanks!

[leprechaun]

u don't thinks "Illegal instruction" is because of the compiler then?

[maxx_730]

Leprechaun, your server up already? You said youd post a link to your site this evening.

[leprechaun]

No.. sry not yet.. got a little caught up in this qws stuff, and one of my scripts seem to fail,
maybe I have forgotten some step. I'm trying to simplify the process a little cause the first time
I created the cross-compiler u would have to edit a lot of files..
As soon as I solve it, it will be published! Please be patient

[rpconnect]

u don't thinks "Illegal instruction" is because of the compiler then?

I'm not sure: I am using arm-linux-g++ to compile qt-2.3.7 and qtopia-free-1.7.0 and they seem to compile fine (no complaining), I then use arm-linux-g++ to compile and link the example application, and that goes fine too. When I try to run it on the phone it seems to load the (re)compiled lib files just fine, then says "Create pluginlibman in libqpe" followed by "Illegal instruction" and then it quits.

I am pretty sure the .so files are loading correctily because if I take them away it asks for libqpe, then libte, and when I put them back it moves along without asking for libraries, but then comes to the "Illegal instruction" error.

I guess I am simply assuming that the arm-linux-g++ compiler is okay because the phone seems to start the executable and load the libraries wi/o complaining.

[leprechaun]

well, how about the floating point operations then?

[rpconnect]

well, how about the floating point operations then?

I'm pretty new to this, how can I check the FP status of the arm-linux-g++ compiler?

should I try the test code buhzi posted previously to check?

[leprechaun]

do the objdump thing that buhzi mentioned earlier in this thread
it should say [APCS-32] [VFP float format] [software FP] [has entry point] in the end if ok..
at least mine does now, and they work

[rpconnect]

do the objdump thing that buhzi mentioned earlier in this thread
it should say [APCS-32] [VFP float format] [software FP] [has entry point] in the end if ok..
at least mine does now, and they work

what options should I use for the objdump command? (I am new to this too, sorry)

If it helps, I tried compiling the example from buhzi for both x86 and the arm-linux and there is a difference (when I run it on the phone I get d_foo = 1233433.000000 0.000000, looks like somethings wrong.... at least it runs on the phone so the arm-linux-g++ can't be that far off.... any suggestions?)

[leprechaun]

Ok here's the "not so complete but at least something" GUIDE that I've been talking about..
Now I've got to sleep..