nanogui: Thread: FLTK 2.0 followup

Hi all,

I checked my sources and managed to re-discover the problem I had run into before. Compiling fltk 2.0 goes ok, but when compiling apps against the libraries I produce these errors:

../lib/libfltk2.a(run.o): In function `open_stylus_device(_XDeviceInfo*, int, int)':
run.cxx:(.text+0xfe8): undefined reference to `XSelectExtensionEvent'
run.cxx:(.text+0x1008): undefined reference to `XOpenDevice'
../lib/libfltk2.a(run.o): In function `fltk::enable_tablet_events()':
run.cxx:(.text+0x125c): undefined reference to `XGetExtensionVersion'
run.cxx:(.text+0x1280): undefined reference to `XListInputDevices'
run.cxx:(.text+0x1330): undefined reference to `XFreeDeviceList'
collect2: ld returned 1 exit status
make: *** [test1] Error 1

as far as I can tell these functions are from either libXext or libXi. I tried to code around these places in x11/run.cxx and eventually got test apps linking against the libraries, but as these apps always seg fault on me it probably has to do with these code sections I have messed with. 

good luck,
Mike McCune
Navigation Solutions
248 282 5407

The problem is that libnx does not contain all of the X11 functions and
if FLTK 2.0 uses any of those functions you will get undefined
references.
You need to add missing functions to libnx and make them do something
that makes sense.
I had similar problem with FLTK 1.7 but the number of problem functions
was very small.
FLTK 2.0 uses more advanced X11 functions that are not provided (yet!)
in libnx.
Martin


-----Original Message-----
From: McCune, Michael ####@####.#### 
Sent: Monday, July 23, 2007 12:50 PM
To: ####@####.####
Subject: [nanogui] FLTK 2.0 followup


Hi all,

I checked my sources and managed to re-discover the problem I had run
into before. Compiling fltk 2.0 goes ok, but when compiling apps against
the libraries I produce these errors:

../lib/libfltk2.a(run.o): In function `open_stylus_device(_XDeviceInfo*,
int, int)':
run.cxx:(.text+0xfe8): undefined reference to `XSelectExtensionEvent'
run.cxx:(.text+0x1008): undefined reference to `XOpenDevice'
../lib/libfltk2.a(run.o): In function `fltk::enable_tablet_events()':
run.cxx:(.text+0x125c): undefined reference to `XGetExtensionVersion'
run.cxx:(.text+0x1280): undefined reference to `XListInputDevices'
run.cxx:(.text+0x1330): undefined reference to `XFreeDeviceList'
collect2: ld returned 1 exit status
make: *** [test1] Error 1

as far as I can tell these functions are from either libXext or libXi. I
tried to code around these places in x11/run.cxx and eventually got test
apps linking against the libraries, but as these apps always seg fault
on me it probably has to do with these code sections I have messed with.


good luck,
Mike McCune
Navigation Solutions
248 282 5407

Michael:

Thank you for your replies.  Yes....that is where I  am at  right now.  I have added the missing functions to the stub.c file to get eCos/nxlib/fltk2 and my application code to compile.

Within eCos, both the client and the server reside in the same space with the application.  I also needed to add some SVC_[fuinctionname] definitions to serv.h to make nano-x happy.

I just need to resolve two more undefined references and it will be time for a smoke test.

Graham...


"McCune, Michael" ####@####.#### wrote: 
Hi all,

I checked my sources and managed to re-discover the problem I had run into before. Compiling fltk 2.0 goes ok, but when compiling apps against the libraries I produce these errors:

../lib/libfltk2.a(run.o): In function `open_stylus_device(_XDeviceInfo*, int, int)':
run.cxx:(.text+0xfe8): undefined reference to `XSelectExtensionEvent'
run.cxx:(.text+0x1008): undefined reference to `XOpenDevice'
../lib/libfltk2.a(run.o): In function `fltk::enable_tablet_events()':
run.cxx:(.text+0x125c): undefined reference to `XGetExtensionVersion'
run.cxx:(.text+0x1280): undefined reference to `XListInputDevices'
run.cxx:(.text+0x1330): undefined reference to `XFreeDeviceList'
collect2: ld returned 1 exit status
make: *** [test1] Error 1

as far as I can tell these functions are from either libXext or libXi. I tried to code around these places in x11/run.cxx and eventually got test apps linking against the libraries, but as these apps always seg fault on me it probably has to do with these code sections I have messed with. 

good luck,
Mike McCune
Navigation Solutions
248 282 5407


       
---------------------------------
Yahoo! oneSearch: Finally,  mobile search that gives answers, not web links. 

Hi Martin,

Yeah, that's more or less what I did( adding the missing functionality ). 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.

Mike McCune
Navigation Solutions
248 282 5407


-----Original Message-----
From: Martin Kajdas ####@####.####
Sent: Mon 7/23/2007 3:19 PM
To: McCune, Michael; ####@####.####
Subject: RE: [nanogui] FLTK 2.0 followup
 
The problem is that libnx does not contain all of the X11 functions and
if FLTK 2.0 uses any of those functions you will get undefined
references.
You need to add missing functions to libnx and make them do something
that makes sense.
I had similar problem with FLTK 1.7 but the number of problem functions
was very small.
FLTK 2.0 uses more advanced X11 functions that are not provided (yet!)
in libnx.
Martin

Graham,

Sounds like you are very close to testing it out, please keep us posted I would love to hear how things go.

Mike McCune
Navigation Solutions
248 282 5407


-----Original Message-----
From: Graham Henderson ####@####.####
Sent: Mon 7/23/2007 3:44 PM
To: McCune, Michael; ####@####.####
Subject: Re: [nanogui] FLTK 2.0 followup
 
Michael:

Thank you for your replies.  Yes....that is where I  am at  right now.  I have added the missing functions to the stub.c file to get eCos/nxlib/fltk2 and my application code to compile.

Within eCos, both the client and the server reside in the same space with the application.  I also needed to add some SVC_[fuinctionname] definitions to serv.h to make nano-x happy.

I just need to resolve two more undefined references and it will be time for a smoke test.

Graham...

I usually add printf() into every libnx function that I modified and
this way I can see  which ones get called and which one causes the
problem.
Your problem could be that your libnx functions do not set X11
variables/structures properly that following X11 functions depend on.
I fixed many libnx problems but you must understand what X11 functions
do that libnx replaces.
Martin
 

________________________________

From: McCune, Michael ####@####.#### 
Sent: Monday, July 23, 2007 1:56 PM
To: Martin Kajdas; ####@####.####
Subject: RE: [nanogui] FLTK 2.0 followup



Hi Martin,

Yeah, that's more or less what I did( adding the missing functionality
). 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.

Mike McCune
Navigation Solutions
248 282 5407


-----Original Message-----
From: Martin Kajdas ####@####.####
Sent: Mon 7/23/2007 3:19 PM
To: McCune, Michael; ####@####.####
Subject: RE: [nanogui] FLTK 2.0 followup

The problem is that libnx does not contain all of the X11 functions and
if FLTK 2.0 uses any of those functions you will get undefined
references.
You need to add missing functions to libnx and make them do something
that makes sense.
I had similar problem with FLTK 1.7 but the number of problem functions
was very small.
FLTK 2.0 uses more advanced X11 functions that are not provided (yet!)
in libnx.
Martin

Michael:

I have gotted eCos to run the non-fltk part of my application in client/server mode.  As you may recall, my application linked directly to the server before.

I have added the button test application to my code and it will execute to a point.  I am currently throwing a Data Abort exception in SVR_GrPeekEvent.  In addition, the following unsupported (nxlib 0.45) routines are being called:

XSetErrorHandler
XSetLocaleModifier
XOpenIM

More as it develops.

Graham
 

"McCune, Michael" ####@####.#### wrote: Graham,

Sounds like you are very close to testing it out, please keep us posted I would love to hear how things go.

Mike McCune
Navigation Solutions
248 282 5407


-----Original Message-----
From: Graham Henderson ####@####.####
Sent: Mon 7/23/2007 3:44 PM
To: McCune, Michael; ####@####.####
Subject: Re: [nanogui] FLTK 2.0 followup
 
Michael:

Thank you for your replies.  Yes....that is where I  am at  right now.  I have added the missing functions to the stub.c file to get eCos/nxlib/fltk2 and my application code to compile.

Within eCos, both the client and the server reside in the same space with the application.  I also needed to add some SVC_[fuinctionname] definitions to serv.h to make nano-x happy.

I just need to resolve two more undefined references and it will be time for a smoke test.

Graham...



       
---------------------------------
Yahoo! oneSearch: Finally,  mobile search that gives answers, not web links. 

> 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

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. 

: 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.

When you're done, if you could send me a "diff -urN" patch of nxlib
and any nano-X changes that'd be great.

Are there specific features of FLTK 2.0 you prefer over the 1.x release?

Regards,

Greg