Dear Ian,Is this proparly compiled or not??? i hope its not but still m asking
you..please reply me. Linking fluid.../usr/bin/ld: skipping incompatible
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libXext.so when
searching for -lXext/usr/bin/ld: skipping incompatible
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libX11.so when
searching for -lX11=== making test ===Compiling unittests.cxx...Linking
unittests.../usr/bin/ld: skipping incompatible
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libXext.so when
searching for -lXext/usr/bin/ld: skipping incompatible
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi/lib/X11//libX11.so when
searching for
-lX11---===
installing FL ===Installing include files in
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi//include...=== installing src
===Installing libraries in
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi//lib...
=== installing fluid ===Installing FLUID in
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi//bin...=== installing test
===Installing example programs to
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi//share/doc/fltk/examples...===
installing documentation ===Installing documentation files in
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi//share/doc/fltk...Installing
man pages in
/home/vinayak/arm-2007q1/arm-none-linux-gnueabi//share/man...Quoting
quot;MacArthur, Ian (SELEX GALILEO, UK)quot; lt;[EMAIL PROTECTED]gt;:gt;
before that i need to say one thing. gt; earlier while compiling got a an
error which some thing like this:- Fl_x.cxx:239: error: impossible
constraint in 'asm' Fl_x.cxx:240: error: impossible constraint in 'asm'
Fl_x.cxx:241: error: impossible constraint in 'asm'If those line numbers are
correct, then those errors suggest that youhave the wrong header files for the
unix quot;selectquot; functions or similar -not specifically related to
the X-windowing system, but still a showstopper.You need to ensure that *only*
the target toolchain header files areincluded in the build, and that no
local-system header files getincluded, as they *will* be different and often
incompatible.gt; what i have done is copied X11 from /usr/lib/X11/ togt; my
toolchain /lib.gt; is that correct method No.All the libs that you link
the target applications against *must* belibs built for the target
architecture.So you must not use *any* of your host libs on your target, you
mustobtain (or build for yourself) the correct libs for the target.If you think
about it, the libs contain code that will be linked intoyour app then run on
your target - so the host libs contain x86 code andthe target libs need to
contain ARM code... Not the same thing at all!gt; if not tell me from scracth
will try to rebuild fltk. You need to tell us what display system your target
board has - is itX-windows or is it a framebuffer device?Assuming it is X
-windows, you need to obtain the correct X11 librariesand header files to
allow you to build X-windows applications for yourtarget board. I assume that
these will be available from the toolchainor board supplier.If you are building
the boards yourself, then you may need to build theX11 libraries yourself - in
which case you need to get the sources fromXorg, then cross-compile them for
your target hardware. The Xorgconfigure system is complex, but does support
cross-compilation fairlywell, and there are many articles on the web about
doing this. It isoutside the scope of a fltk list to discuss it though.
(Suffice to sayit is a straightforward but long and arduous process!)Anyway -
once you have the necessary X libs and headers for your target,fltk should
build against them without these troubles.SELEX Sensors and Airborne Systems
LimitedRegistered Office: Sigma House, Christopher Martin Road, Basildon, Essex
SS14 3ELA company registered in England amp; Wales. Company no. 02
426132This
email and any attachments are confidential to the intendedrecipient and may
also be privileged. If you are not the intendedrecipient please delete it from
your system and notify the sender.You should not copy it or use it for any
purpose nor disclose ordistribute its contents to any other
person.
___
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
