Cross compiling (Qtopia/Zaurus) bug in Kdevelop
blachner at gmx.de
Tue Sep 3 21:23:04 UTC 2002
I have found a bug in KDevelop. I have a project which compiles fine in
KDevelop as a normal Qt2 program and as a Qtopia program for x86.
When I switch the compilers (and Qt, library and include pathes) to ARM the
following error occured when KDevelop calls configure:
checking for Qt.. configure: error: Qt (>= Qt 2.2.2) (library qte) not found.
Please check your installation!
For more details about this problem, loo at the end of config.log.
O.K. I looked at config.log and found this:
configure:6769: rm -rf SunWS_cache; g++ -o conftest -O2 -O0 -fno-exceptions
-fno-check-new -fno-rtti -DQWS -I/opt/Qtopia/sharp//include -DQTOPIA
-D_REENTRANT -DQWS -L/opt/Qtopia/sharp//lib conftest.C -lqte -lpng -lz
-lm -ljpeg 1>&5
/opt/Qtopia/sharp//lib/libqte.so: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
Hmm. libqte in /opt/Qtopia/sharp//lib is the correct ARM lib, this is 100%
In the config.log I found also this:
configure:2974: checking for ld used by GCC
configure:3042: checking if the linker (/usr/i486-suse-linux/bin/ld) is GNU ld
Its a stupid idea from KDevelop or the configure script to use a 486 linker to
link a ARM library, this must fail.
After this I searched in Kdevelop, if I can set the linker (LD) for ARM. But
only CC, CXX and CPP can set in KDevelop, so far I see. Why can't I set the
linker for cross compiling? What can I do that KDevelop can runs the
Btw. If I call the configure script in the console with the same options as
KDevelop and the LD variable is set to the arm linker the configure script
More information about the KDevelop-devel