nanogui: FLTK 2.0 followup
Subject:
Re: [nanogui] FLTK 2.0 followup
From:
Graham Henderson ####@####.####
Date:
2 Aug 2007 15:19:04 +0100
Message-Id: <944006.3687.qm@web32012.mail.mud.yahoo.com>
Greg:
I have managed to get fltk 2.0/NxLib 0.45/ Nano-X/eCos to compile and run on my iMXL-Lite arm-9 dev system. It is currently running the fltk "Buttons" example. I am moving the fltk 1.17 application to 2.0 using VS.Net and will then move it to the arm board. As I am working in an embedded environment, everything is statically linked.
Graham....
Greg Haerr ####@####.#### wrote: > Unfortunately I still get seg faults when running even the simplest of
apps, I am having serious difficulty debugging this as I don't have gdb on
my target and the problems seem to occur once fltk::run has been called.
I don't recommend porting a new version of a widget set, like FLTK
2.0 to NXLIB using your embedded target. These things are much
easier debugged on the linux desktop (running framebuffer) first.
This is because with dynamic linking, ONLY NXLIB, and not
any of the applications nor FLTK need recompiling. This works
because NXLIB uses only standard X11 headers, and just redirects
X11 requests to nano-X. The applications and FLTK don't have
to be recompiled.
Having said this, the dynamic link mechanism won't always
tell you which X11 library entry points don't exist, so sometimes
a quick static link pass in the beginning will save a lot of time
creating the initial stubs in nxlib/stubs.c that may eventually
require a real implementation.
Hope this helps,
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####
Graham W. Henderson
241 Sauk Drive
Batavia, IL 60510-8660
630 406 1724 (home)
630 862 6474 (cell)
801 406 6008 (fax )
---------------------------------
Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV.
