nanogui: FLTK 2.0 followup
Subject:
RE: [nanogui] FLTK 2.0 followup
From:
"Martin Kajdas" ####@####.####
Date:
23 Jul 2007 22:06:28 +0100
Message-Id: <CF2BB830A62F914F848E5AD5FFF57AC2291609@mkmail.MKPROD.COM>
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
