QUOTE(d.maddock1 @ Dec 22 2005, 05:43 PM)
In particular, what <arc-dir>, <work-dir>, and <src-dir> were used to set up Zaurus-X-gcc?
what are the issues you find?
Here is the path for Zaurus-X-gcc:
<work-dir> = /Developer/Zaurus-X-gcc
with that it calls ./cross.sh --srcdir "$srcdir" --workdir "$workdir"
That one in turn does a
./configure --target=arm-linux --prefix=$absworkdir/opt/Embedix/tools
./configure --target=arm-linux --prefix=$absworkdir/opt/Embedix/tools --with-headers=$absworkdir/opt/Embedix/tools/arm-linux/include --with-libs=$absworkdir/opt/Embedix/tools/arm-linux/lib --enable-threads=posix
<arc-dir> is not used in generating the compiler. And <src-dir> is something local while generating the compiler.
I have never compiled any Qt program, so I did not look at the libraries...
One very important thing to remember: gcc does not like if there are space characters in the file path (e.g. $workdir).
Usually I put something like the following in my Makefiles (optimized for Objective-C)
TOOLCHAIN := /Developer/Zaurus-X-gcc/opt/Embedix/tools/arm-linux
SDK := /Developer/Zaurus-X-gcc/SDKs/mySTEP.sdk
MYSTEP := $(SDK)/usr/mySTEP
CC := $(TOOLCHAIN)/bin/gcc
LS := $(TOOLCHAIN)/bin/ld
AS := $(TOOLCHAIN)/bin/as
NM := $(TOOLCHAIN)/bin/nm
STRIP := $(TOOLCHAIN)/bin/strip
# header search paths
INCLUDES := \
# standard libraries (incl. search path)
LIBS := $(LIBS) \
-L$(SDK)/usr/mySTEP/lib -lFoundation -lGdo \
-L$(SDK)/usr/ffcall/lib -lavcall \
-lm -ldl -lpthread \
Hope this helps.