[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] nxlib
From: Anthony Fu ####@####.#### Date: 8 Sep 2004 04:10:55 +0100 Message-Id: <11E0FCE17997AF499A67EEB55B0F6048488BDB@arg001.argus-tech.com.tw> Hi My FLTK can run on cygwin/X. how can I set up to run against NXLIB? Thanks, Anthony | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] nxlib
From: Hinko Kocevar ####@####.#### Date: 8 Sep 2004 10:49:55 +0100 Message-Id: <413ED5BE.3040407@iskramedical.si> Anthony Fu 傅錫泓 wrote: > Hi > > My FLTK can run on cygwin/X. how can I set up to run against NXLIB? > compile nanox for your platform, compile nxlib, copy nanox binaries and libs to your platform, copy nxlib binaries to your platform, start nanox server, start fltk app. It will use libX11 provided ny nxlib instead of X native libX11. Of course you need to recompile your fltk app for target platform with appropriate fltk libs... regards, h -- hinko <dot> kocevar <at> iskramedical <dot> si Hinko Kocevar, developer Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU "Aì rén" | [Analects XII:22] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
nxlib
From: Yan Seiner ####@####.#### Date: 9 Apr 2007 23:38:09 +0100 Message-Id: <461AC009.6080104@seiner.com> Any hints for cross-compiling nxlib? Which version of X11 headers should I use? How do I modify the Makefile to use my (crosscompile) X11 headers? Thanks, --Yan | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] nxlib
From: "Greg Haerr" ####@####.#### Date: 10 Apr 2007 04:29:22 +0100 Message-Id: <03cd01c77b20$28d8b850$6401a8c0@winXP> : Which version of X11 headers should I use? Most any should work. I used X11R6 : How do I modify the Makefile to use my (crosscompile) X11 headers? I think there's an X11INCLUDE or something like that in the Makefile, where you can point to your target headers. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] nxlib
From: Yan Seiner ####@####.#### Date: 10 Apr 2007 21:09:10 +0100 Message-Id: <461BEEA3.6070202@seiner.com> Greg Haerr wrote: >: Which version of X11 headers should I use? > >Most any should work. I used X11R6 > >: How do I modify the Makefile to use my (crosscompile) X11 headers? > >I think there's an X11INCLUDE or something like that in >the Makefile, where you can point to your target headers. > > H Gregg: I got Tcl/Tk built and running - sort of. I have a black window with the wm decorations. I would appreciate any comments on the output from nano-X below (especially the 'no handler' stuff): root:~> nano-X & nanowm & DISPLAY=:0 echo "load /lib/libTkhtml3.0.so ; source /bin/hv/hv3_main.tcl" | wish 150 151 nx11: display bpp = 16, bits_per_rgb 6 XSetLocaleModifiers called nxTranslateEventMask no handler for event mask (00c1807f): 16 22 23 XInternAtom Comm 0 XInternAtom InterpRegistry 0 XInternAtom TK_APPLICATION 0 XGrabServer called XChangeProperty InterpRegistry XUngrabServer called XChangeProperty TK_APPLICATION WARNING: can't find package Img WARNING: can't find package sqlite3 XInternAtom MULTIPLE 0 XInternAtom INCR 0 XInternAtom TARGETS 0 XInternAtom TIMESTAMP 0 XInternAtom TEXT 0 XInternAtom COMPOUND_TEXT 0 XInternAtom TK_WINDOW 0 XInternAtom CLIPBOARD 0 XInternAtom UTF8_STRING 0 XLoadFont('cursor') = '(null)' [0] nxTranslateEventMask no handler for event mask (00c1807f): 16 22 23 nxTranslateEventMask no handler for event mask (00c1807f): 16 22 23 nxTranslateEventMask no handler for event mask (00c1807f): 16 22 23 nxTranslateEventMask no handler for event mask (00c1807f): 16 22 23 Error in constructor: couldn't load cursor font nxTranslateEventMask no handler for event mask (00e3807f): 16 22 23 XSetClassHint called XInternAtom _NET_WM_NAME 0 XChangeProperty _NET_WM_NAME XInternAtom WM_DELETE_WINDOW 0 XInternAtom WM_PROTOCOLS 0 XChangeProperty WM_PROTOCOLS --Yan | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
nxlib
From: "Greg Haerr" ####@####.#### Date: 16 Nov 2007 05:48:07 +0000 Message-Id: <083401c82814$41e5b810$6401a8c0@winXP> Martin - By chance, are you running the patched version of NXLIB that is required to properly handle variable-sized truetype fonts? I want to get a couple of other patches in to NXLIB, but would prefer to take the code from a working version from somebody. I haven't setup FLTK to run with freetype, so I'm not actually running anything that will test that patch directly. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: nxlib
From: "Martin Kajdas" ####@####.#### Date: 16 Nov 2007 16:59:15 +0000 Message-Id: <CF2BB830A62F914F848E5AD5FFF57AC24F9941@mkmail.MKPROD.COM> I downloaded all new files from CVS and compared with mine. Most of the differences are either fixes, not important or minor and I will update mine to match. Only LoadFont.c is somewhat different and I would have to go thru the differences to see what is important and what is not. I know that I fixed my file before I reported the problem and my fixes are crude but work in my system. Yours are probably cleaner and more generic but I would have to test them in my system. Let me know how you want to work with me to test these patches. Martin -----Original Message----- From: Greg Haerr ####@####.#### Sent: Thursday, November 15, 2007 9:48 PM To: Martin Kajdas Cc: ####@####.#### Subject: nxlib Martin - By chance, are you running the patched version of NXLIB that is required to properly handle variable-sized truetype fonts? I want to get a couple of other patches in to NXLIB, but would prefer to take the code from a working version from somebody. I haven't setup FLTK to run with freetype, so I'm not actually running anything that will test that patch directly. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] RE: nxlib
From: "Greg Haerr" ####@####.#### Date: 16 Nov 2007 19:45:52 +0000 Message-Id: <0a5801c82889$3cad7390$0300a8c0@RDP> > Only LoadFont.c is somewhat different and I would have to go thru the differences to see what is important and what is not. Send me your LoadFont.c and I'll inspect it from here and produce any further changes. > I know that I fixed my file before I reported the problem and my fixes are crude but work in my system. Are you running freetype fonts using a fonts.dir file from Microwindows? > Let me know how you want to work with me to test these patches. Just send LoadFont.c. Next we'll debug arc drawing. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] RE: nxlib
From: "Greg Haerr" ####@####.#### Date: 16 Nov 2007 19:48:34 +0000 Message-Id: <0a8c01c82889$a5a0d270$0300a8c0@RDP> > Yours are probably cleaner and more generic but I would have to test them in my system. > Let me know how you want to work with me to test these patches. Martin If the CVS NXLIB works on your system, then that should be good enough, since I've reviewed all the patches before committing them. There appear to be two LoadFont patches/implementations, so I'll compare them. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: [nanogui] RE: nxlib
From: "Martin Kajdas" ####@####.#### Date: 16 Nov 2007 23:05:16 +0000 Message-Id: <CF2BB830A62F914F848E5AD5FFF57AC24F9948@mkmail.MKPROD.COM> > If the CVS NXLIB works on your system, then that should be good enough, since I've reviewed all the patches before committing them. > There appear to be two LoadFont patches/implementations, so I'll compare them. The latest CVS version of LoadFont.c has problems and should not be used until we figure it out. On my system it crashes from memory problems. All other files are OK. Martin | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |