There's been a few of these recently - is there a sudden rush of people doing ARM embedded designs or something? (Or is it just the technical colleges starting back?)
Anyway - a trawl through the archives should find a lot of useful tips. > I am new to fltk Welcome! Before you start building anything for your target system, play about with fltk on your host PC for a while first. It's much easier to debug problems with your initial programs on the host system than on the target! > as well as ARM cross compilation, can > anybody suggest which version of gnu arm toochain is suits > for FLTK cross compilation (Assuming a linux/unix target - if your target is WinCE you will have other problems...) You need a reasonably standards compliant C++ compiler, and an implementation of the X11 windowing system. Other than that there are few issues, so pick a toolchain that is known to work for your target hardware. Then build a few simple (e.g. command line) "hello world" type of programs to make sure the tools work and you know how to use 'em! If you have a choice between a "real" X-server (e.g. Xorg or xf86) and a "lite" X-server (e.g. nano-X, etc.) then I would opt for the "real" X-server every time. This will be easier and more compatible than the "lite" versions, which tend to be "problematic". It is not clear that the niche for "lite" X-servers really exists anymore - most ARM target hardware has way more CPU and RAM than we had for running X-servers in the old days... However, if you are *very* constrained for resources, e.g. RAM, you might need to consider a "lite" X-server. In which case, good luck... > and i also wanted to know cross > compilation of FLTK for arm target board. Note that at this point, lots of folk try and configure fltk for a cross-compilation build by passing --host... And --target... Flags to the fltk configure script. Forget this, it will not work for you. Instead, configure a minimalist[1] fltk build on your Linux host, then copy the generated "config.h" and "makeinclude" files to your clean cross-compilation tree. There, edit them to reflect your target environment. In "makeinclude" this mainly involves fixing the library, include and tool paths to point to the correct cross-compilation equivalents. In "config.h" this involves checking the endianess is OK for your target (most, but not all, ARM ports force the ARM into little-endian mode the same as an x86 PC, but you need to watch this.) Also check that the configure hasn't set 64-bit mode, if your host is 64-bit capable... Then hit make and hope for the best... It'll most likely choke trying to build the test programs (the Makefile tries to use the newly built cross-target-fluid to generate some of the tests - edit the Makefile to use the "local" host fluid instead.) That's it. [1] The "minimalist" configure might go something like this: ./configure --disable-shared --enable-threads --disable-xdbe --disable-xft --enable-local-zlib --enable-local-png --enable-local-jpeg SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
