Well I managed to get a bit farther with this installation.  To answer a few of your questions, we were attempting to build 4.6.x, but have switched to 4.5.3 for now.  I could probably rebuild on 4.6.x with my new configure options...

I really don't know what toolchain I'm using.  I do have OpenEmbedded installed, and have some arm-linux-g++ installed, but I don't remember where that came from.  I then installed Qt Embedded from a Commercial tarball using the following configure parameters (note I copied qws/linux-arm-g++ to qws/linux-gumstix-g++ in case I wanted to make any changes to it):

./configure -static -prefix /opt/QtEmbedded -embedded arm -platform /qws/linux-x86-g++ -xplatform /qws/linux-gumstix-g++ -no-largefile -no-accessibility -no-openssl -fast -little-endian -no-cups -host-big-endian -qt-freetype -nomake examples -silent

Then ran gmake and sudo gmake install.  Everything appeared to install successfully.  However, in Qt Creator, when I try to add a new Qt version in the tools -> options menu, the debugger helper will not rebuild and any project I try to compile against the Qt Embedded libraries fail with an error:

Starting: /opt/QtEmbedded/bin/qmake /home/user/Projects/Qt Creator/testembedded/testembedded.pro -spec /qws/linux-gumstix-g++ -r CONFIG+=debug
Failure to read QMAKESPEC conf file /qws/linux-gumstix-g++/qmake.conf

There is no qws folder directly under /opt/QtEmbedded.  It's under /opt/QtEmbedded/mkspec/qws.  I'm not sure why it's trying to use /qws/linux-gumstix-g++ or how to change that.


On Tue, Feb 2, 2010 at 6:43 PM, David Boddie <david@boddie.org.uk> wrote:
On Tuesday 02 February 2010 14:33, coderdrone@gmail.com wrote:

> Not sure how to quote in Gmail sadly...  Never heard of IPlinux.
> Currently we're using, or at least trying to use Qt Embedded in Qt Creator
> and OpenEmbedded.

OK.

> I'll have to look at the gumstix.net Qtopia core guide at home.  For some
> reason gumstix.net always times out with some tcp_error at the office. :/
>
> As for the platform and errors, we're running Overo Earth as the target
> device and RHEL 5 on the development side.  The first error was the
> following related to freetype (there may have been more error text, but I
> can't recall it.
>
>> >>{standard input}:Assembler messages:
>
>> >>{standard input}:778: Error: register or shift expression expected ?
>
>> >>'orr r3, r2, lsl#16'

Hmm. I haven't seen that. Which version of Qt are you using? I'm guessing
from your other comments that it's 4.6.x.

> Nokia provided a fix due to a compiler error in GCC 3.4:
>
> To fix this issue patch
> /src/3rdparty/freetype/include/freetype/config/ftconfig.h Line 330.
>
> "orr %0, %2, lsl #16\n\t" /* %0 |= %2 << 16 */
>
> + "orr %0, %0, %2, lsl #16\n\t" /* %0 |= %2 << 16 */
>
> Another error we were seeing related to JavaScriptCore/wtf/Platform.h, I
> believe around line 680 or so.  I didn't save the compiler output and
> would
> have to attempt to recreate it.  It appears to have gone away since I ran
> ./configure again with -no-webkit and -no-javascript-jit.

If you're building with GCC 3.4, you won't be able to build WebKit, and
you're correct in removing the support for the JIT as well. I would try
to build with a later version of GCC if possible.

 http://qt.nokia.com/doc/4.6/supported-platforms.html

Are you using one of the toolchains that OpenEmbedded builds for you?

If all else fails, and you have already built your kernel and root
filesystem. I would perhaps try a CodeSourcery toolchain to build Qt, as
linked to from that page.

> It just seems the more errors we get fixed, the more come up.  I wouldn't
> expect Nokia's Qt Embedded code to have errors like this, which leads me
> to believe we may simply be configuring it incorrectly with the configure
> script on the development workstation.
>
> ./configure -embedded arm -no-webkit -no-javascript-jit
> gmake
> <...compilerer errors...>

It's possible that the configuration is causing you problems. You can make
the configuration process more verbose by passing the -verbose option.

As I said, I've been using the IPlinux chroot to cross-build Qt, using the
toolchain it provides. I pass the following options to the configure script:

 -opensource -release -xplatform qws/linux-arm-ip-gnueabi-g++
 -embedded arm -no-qvfb -depths 16,32 -qt-libjpeg
 -qt-libmng -qt-libpng -qt-zlib -qt-mouse-tslib -no-accessibility
 -no-qt3support -no-dbus -no-scripttools -no-webkit -no-phonon
 -release
 -D QT_NO_ACCESSIBILITY -D QT_NO_CURSOR -D QT_NO_QWS_CURSOR
 -D QT_NO_SESSIONMANAGER -D QT_QWS_SCREEN_COORDINATES

I also pass various others, but these are the ones which you might want to
see. Some of these are probably the default settings, but I like to be
explicit about what it's building.

You probably want to pass "-embedded arm" and "-xplatform qws/linux-arm-g++"
at least.

If you want to send me compiler output off-list, feel free to do so, though
I can't guarantee I'll have any profound suggestions for you. :-/

David


------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users