> My goal is to get a User Interface for my embedded Blackfin 
> Device running
> on uClinux with nano-X 0.91 and nxlib.

I'm very wary of nano-X and don't use it, so what follows may not be
useful to you.


> The next step I did was to configure fltk2 that I can compile it with
> blackfin-toolchain. With this makeinclude file generated
> 
> by the configure script I compiled fltk2 without any problems.

Hmm, OK, though I'm not convinced the fltk configure handles
cross-compilation robustly, so I'd want to check the auto-generated
"config.h" and "makeinclude" files by hand, just to be sure...


> STRIP     = strip

Need to make sure the default strip understands the bfin files. Probably
OK though (elf I assume?)



> CC        = bfin-linux-uclibc-gcc
> 
> CXX       = bfin-linux-uclibc-gcc

Hmm, I'd favour  bfin-linux-uclibc-g++ at this point (and maybe drop the
libstdc++ from the link lines...)


> LIBCOMMAND = /usr/bin/ar cr

Again, I'd want to be convinced the system ar understands the bfin
files...


> # libraries to link with:
> 
> LDLIBS =  -L/home/mheiser/uClinux/MyStaging/usr/lib
> -L/home/mheiser/uClinux/MyStaging/usr/lib -lX11 -lpthread -lm 
>  -lnano-X
> -lsupc++


Is that list of libs OK? Is X11 needed for the nano-x builds?

FWIW, I'd hand edit that to make sure the paths were explicit - Just In
Case!
The build chain might have different ideas than you might expect, for
searching for "-lname" entries, so giving an explicit path to the actual
lib you want is often worth trying.

If you pass -v to gcc at build time, it will tell you where it is
searching for include and lib files, so might be worth trying that and
confirming that it is looking in the places you expect...



> After proper compilation of fltk2 I copied the library-files and the
> fltk/include folder to a place where 
> my libs for my app are. I develop the App using Eclipse 3.5. 

OK - do the examples from the fltk test folder cross-compile on your
host, and do the generated executables run on your target?




> /opt/uClinux-2008R1.5/bfin-linux-uclibc/bin/bfin-linux-uclibc-g++
> -L/home/mheiser/uClinux/MyStaging/usr/lib -mcpu=bf537-any 
> -o"CCUI"  ./CCUI.o
> ./CCUI_BA_PicHandle.o ./CCUI_BesucherAlbumDlg.o ./CCUI_CommFuncs.o
> ./CCUI_Dlg.o ./CCUI_FileHandle.o ./CCUI_KennzifferneingabeDlg.o
> ./CCUI_Thread.o ./main.o  ./Wrapper/MsgQueueFuncs.o 
> ./Wrapper/SocketFuncs.o
> ./Wrapper/ThreadingFuncs.o   -lfltk2 -lfltk2_images -ljpeg 
> -lpng -lz -lX11
> -lnano-X -lfreetype -lpthread


Faced with this, I'd be inclined to try running that command from the
shell, but hand editing it to give explicit paths to the cross-compiled
libs, e.g. replacing

        "-lfltk2"

With

        "/path/to/my/cross-compiled/libfltk2.a"

And so on...

Any good?




SELEX Galileo Ltd
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

Reply via email to