> Thank you very much!!! I'm using an Ubuntu 6.06 VMWare Image > under Windows XP. Urgh. Just to be sure I understand; you are cross-compiling for the avr32, from a vmware linux image hosted on winXP. Sounds like the long way round to me! Still, I guess it ought to work... > The board is running with the normal ATMEL > (www.atmel.com/avr32) tools, e.g. busybox "linux" etc. If you > need any further information, please let me know and I'll > give my best. > > FTLK should run with the fb0 device. I've crosscompiled the > nano-x, but I am fed up with it. So I would like to use FLTK. OK, since your last post, I've had a very brief look at the spec for these boards (NGW100)... They are certainly cheap, but they might be a bit "low end"... What are you hoping to do with it? In particular: - I worry it doesn't have enough memory, even for a fltk GUI system. - It's not clear to me what display capability it even has. Are you intending to run an X-client on it and have it render to an X-server elsewhere over the net? Or does the device have a display capability of its own (and if so, what?) - fltk, "out of the box" doesn't work with the framebuffer device. There are patches around that do, however. > I've changed in the config.h just this lines: Comments interleaved: > #define WORDS_BIGENDIAN 1 I assume this is correct. > #define HAVE_STRINGS_H 1 > #define HAVE_STRCASECMP 1 > #define HAVE_STRLCAT 0 > #define HAVE_STRLCPY 0 You are sure this matches what's available in the avr32 toolchain? > STRIP = strip This really should point to the avr32 strip utility. > CFLAGS = $(OPTIM) -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include The include paths MUST point to the avr32 headers, NOT to your host system headers. > CXXFLAGS = $(OPTIM) -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include Ditto... > # program to make the archive: > LIBNAME = ../lib/libfltk.a I'd be inclined to make this libfltk_avr32.a and so on, just to ensure it doesn't collide with the host system libs. > LIBCOMMAND = /usr/bin/ar cr If there's an avr32 "ar" you should really reference that, although it shouldn't matter. > # libraries to link with: > AUDIOLIBS = -lasound Unlikley to work - and only needed for the example programs anyway. > LDLIBS = -L/usr/lib -lm -lXext -lX11 You MUST reference the avr32 libs here, NOT the host system libs. > GLDLIBS = -L/usr/lib -lm -lXext -lX11 Ditto... > LINKFLTK = ../lib/libfltk.a See suggestion above about lib naming (libfltk_avr32.a etc...) which should be applied to all the following fltk lib paths really, I suggest. > LINKFLTKGL = > LINKFLTKFORMS = ../lib/libfltk_forms.a ../lib/libfltk.a > LINKFLTKIMG = ../lib/libfltk_images.a ../lib/libfltk.a $(IMAGELIBS) > LINKSHARED = ../lib/libfltk_images.a > ../lib/libfltk_forms.a ../lib/libfltk.a $(IMAGELIBS) > IMAGELIBS = -L../lib -lpng -lz -ljpeg If you want image support, you'll need to build avr32 versions of png, zlib and jpeg, and reference them here. > # image libraries to build... > IMAGEDIRS = > > # The extension to use for executables... > EXEEXT = > > # Do we build the OpenGL demos? > GLDEMOS = > > # Do we build the threads demo? > THREADS = Might be worth setting this to "THREADS = threads" as threading should work. > # Name of FLUID executable we install > FLUID = fluid$(EXEEXT) This'll likely not build right, as it'll try and build a host runnable fluid with the cross-tools... > # Additional GUI install/uninstall targets... > INSTALL_DESKTOP = install-linux > UNINSTALL_DESKTOP = uninstall-linux You aren't going to need these. > # Be quiet when building... > .SILENT: Probably best to remove this line until things are working, that way you'll see more of what's going wrong! 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
Re: [fltk.general] Cross Compiling AVR32
MacArthur, Ian (SELEX GALILEO, UK) Fri, 04 Apr 2008 04:43:21 -0700
- [fltk.general] Cross Compiling AVR32 pete
- Re: [fltk.general] Cross Compiling... MacArthur, Ian (SELEX GALILEO, UK)
- Re: [fltk.general] Cross Compiling... pete
- Re: [fltk.general] Cross Compi... MacArthur, Ian (SELEX GALILEO, UK)
- Re: [fltk.general] Cross Compiling... pete
- Re: [fltk.general] Cross Compi... MacArthur, Ian (SELEX GALILEO, UK)

