Re: http://mini2440vietnam.blogspot.com/2011/04/upgrade-qt462-in-mini2440.html Well I have to "hand it to you", or in other words - congratulations! Well done . . . excellent job on producing a qmake.conf for Qt/embedded (4.7.3 in my case) that looks like it WORKS. The resultant binaries are for v4t and the /demo/browser example works. Great start! I tried to subscribe to post a comment on your site but nothing happened, so I'll post my comments here. Previous suggestions that the Qt/desktop version should be installed and even Qt/embedded configured for the frame buffer BEFORE installing Qt/embedded for the target, I think may make the whole process go more smoothly. It would be helpful to make it clear which of the two source files, which have the same name and are the same size, you should be trying to cross-compile. I renamed them to keep them straight in my mind. There is one typo, which is easily recognised, but people may overlook it in qmake.conf: QMAKE_CFLAGS_RELEASE += -march=armv4t -mtune=arm920t is missing the "t" in armv4t I added: QMAKE_RANLIB = /usr/local/arm/4.3.2/bin/arm-none-linux-gnueabi-ranlib just because most other tutorials do. Now, just for my own understanding . . . did you arrive at this qmake.conf file by trial and error OR did you find an example somewhere that explains why one needs to be so verbose in the actual commands. I tried exporting paths to just about everything that I had seen in other tutorials, but always had a compile problem somewhere. Two days ago I managed to get ARM binaries, but not for the v4t. It appears including -march=armv4t on every line in qmake.conf is the key to success. Thanks again for publishing the results of your hard work! Regards, Dave
Qt at mini2440vietnam.blogspot.com
Hi Dave. It's very glad when I know that my blog was helpful for someone :). That result come after many days searching code on Internet (so, sometimes I actually don't understand much the code for upgrading). I was tired of instructions of someone which are not clearly and specific, so I decided to post my result if i finished. And the blog did (at least for you ^^ ). Thanks for your comments. Anyway, I've check the comment sections in my blog, it still run well ... ~~ And, in qmake.conf : QMAKE_CFLAGS_RELEASE += -march=armv4 -mtune=arm920t This line doesn't miss 't' in 'armv4'. However, it RUN even with either 't' or not 't' there. Thanks for visiting my blog. Good luck with coding.