RE: drawables
-Original Message- From: Harold Hunt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 3:11 PM I hope that clarifies things. This may actually be documented in the Porting Layer Definition, but I don't remember for sure. Yes it is sortof - some frameworks have defined mechanisms for RTTI, and I hate to guess wrong... Sounds like you are making good progress. Keep it up and I hope to see what you have soon, So do I :}. As soon as I get the mouse going again I think I'll send the patch in. Rob
Re: Xfree and OpenGL
Dear Harold, thank you for the reply. xdpyinfo shows that both named extensions are present. Is there some possibility to trace where is the problem (some debug mode for Xfree or so ?) David David, Cygwin/XFree86 doesn't have OpenGL, it has Mesa. You can run 'xdpyinfo' in Cygwin/XFree86 and look for the GLX and SGI-GLX extensions. Both of those should be present in a default installation. I'm not sure if Mesa is completely compatible with OpenGL apps on SGI... you'll have to find that out for yourself or hope that someone on the list with an SGI machine answers. Harold David Komanek [EMAIL PROTECTED] said: Hi, sorry to vaste your time, but please, can me somebody explain how to use the OpenGL support in Xfree ? I have installed the complete cygwin distribution (includes opengl libraries), downloaded and installed complete Xfree. It works fine with classical X-servers. However, connecting to SGI workstation, many of its graphical apps don't work. Have I edit /etc/X11/XftConfig some way to get the OpenGL libraries loaded ? Is there some OpenGL application ported for CygWin to test the functionality localy ? Latest versions of CygWin and Xfree (downloaded just today), Windows 2000 Pro SP2. Thanks in advance for any help, David Komanek
Re: Xfree and OpenGL
On Tue, Apr 09, 2002 at 02:43:13PM +0200, David Komanek wrote: Dear Harold, thank you for the reply. xdpyinfo shows that both named extensions are present. Is there some possibility to trace where is the problem (some debug mode for Xfree or so ?) David, There is a sample program called 'glxgears' which will draw three depth buffered rotating gears. If this works, you've got it all running. What's your application reporting ? Alan.
Re: Xfree and OpenGL
Dear Alan, thanks for your comments/advices. I tried glxgears and it works. The gears are not rotating fluent enough on my 800MHz pentium, but I don't expect this is related to my problem. I am able to start xterm, swmgr, toolchest connecting to SGI 6.5.14 box which probably use classical X11 and Motif library only. Trying to start i.e. jot, it claims: dgl error (protocol): remote machine not DGL capable - meda:10.0 dgl error (default init): default dglopen(meda:10.0,4) returned -13 Connecting to another box, running IRIX 6.2, it is even worse - swmgr shows only the first Wait please window and then you can wait for hours and the main window does not appear. In the xterm you can see following message: WARNING: Not all colors for application icons could be allocated. Some interface elements may have different colors. Warning: creating new shape image Jot coredumps, many others too. Toolchest starts fine, but no apps called invoked from its menus. When I run this apps on the local graphics console of an SGI box, it works fine. Well, this problem is not connection type related (both ssh and telnet+xhost produce same results). Probably should I install something on the SGI boxes to translate DGL requests into the X11 protocol (rendered on the server side, but at least working) ? Any ideas are appreciated. David On Tue, Apr 09, 2002 at 02:43:13PM +0200, David Komanek wrote: Dear Harold, thank you for the reply. xdpyinfo shows that both named extensions are present. Is there some possibility to trace where is the problem (some debug mode for Xfree or so ?) David, There is a sample program called 'glxgears' which will draw three depth buffered rotating gears. If this works, you've got it all running. What's your application reporting ? Alan.
Re: Xfree and OpenGL
dgl error (protocol): remote machine not DGL capable - meda:10.0 dgl error (default init): default dglopen(meda:10.0,4) returned -13 Cygwin/XFree86 doesn't have the DGL extension. If you do an 'xdpyinfo' on your SGI box, you'll probably see it. Eh, I thought, DGL is SGI name for OpenGL. Sorry. I suspect you won't be able to get this app working on anything but SGI boxes. O.k., I'll trz VNC if it can handle it on the copy of local display. Not Xfree related anymore. WARNING: Not all colors for application icons could be allocated. Some interface elements may have different colors. Warning: creating new shape image Jot coredumps, many others too. Toolchest starts fine, but no apps called invoked from its menus. When I run this apps on the local graphics console of an SGI box, it works fine. Well, this problem is not connection type related (both ssh and telnet+xhost produce same results). Probably should I install something on the SGI boxes to translate DGL requests into the X11 protocol (rendered on the server side, but at least working) ? How many colours is your Windows screen set up in ? Try changing the depth to 24bit (i.e. 16million colours) Using TrueColor(32bit) on the desktop and starting Xfree with start XWin -screen 0 1024 768 so I don't expect problems here. Probably something in color translation. Most important I see the creating new shape image warning which I get not on the native SGI display. David
Re: Just a note - nativegdi engine
On Wed, Apr 10, 2002 at 01:47:58AM +1000, Robert Collins wrote: 2) I'm working on, I suspect it's a coordinate translation thing. I get lovely background stipple but not (AFAICT solid fills). Rob, Take a look at wingc.c and set miTranslate to 0 (FALSE). Alan.
Re: Just a note - nativegdi engine
On Wed, Apr 10, 2002 at 01:47:58AM +1000, Robert Collins wrote: Creating a single combined clipping region using CombineRgn will allow you to move the for (iX= ..)loop from within the while (nbox--) loop, thus saving multiple selectClipRgn+deleteObject + bitblt calls, which may make the native engine quite a bit faster. I *will* do this optimisation here and elsewhere, but only after I get the fills working for 'native' windows first. Forgot about this Robert, this loop is not a single blt. It's a span of small blits of a part of the stipple/tile. You won't be able to just do a single blit for this. Alan.
Just a note - nativegdi engine
I've made serious progress, but I'm having trouble with two things.
1) The mouse - I'm not getting any WM_MOUSEMOVE messages to the app
windows. Anyone seen this before?
2) I've broken fillspans for DRAWABLE_WINDOWs. I can fix it by drawing
into the root window hdc always,
but that's defeating the purpose - all we gain is the pretty task bar
entries :[.
2) I'm working on, I suspect it's a coordinate translation thing. I get
lovely background stipple but not (AFAICT solid fills).
Anyway, the reason for the email:
Harold:
I thought you might like to see the little todo: I've added.
Creating a single combined clipping region using CombineRgn will allow
you to move the for (iX= ..)loop from within the while (nbox--) loop,
thus saving multiple selectClipRgn+deleteObject + bitblt calls, which
may make the native engine quite a bit faster. I *will* do this
optimisation here and elsewhere, but only after I get the fills working
for 'native' windows first.
Rob
/* TODO: create a single commbined clipping region */
nbox = REGION_NUM_RECTS (pClip);
pbox = REGION_RECTS (pClip);
while (nbox--)
{
hrgn = CreateRectRgn (pbox-x1, pbox-y1, pbox-x2,
pbox-y2);
SelectClipRgn (pGCPriv-hdcMem, hrgn);
DeleteObject (hrgn);
hrgn = NULL;
for (iX = fullX1; iX fullX2; iX +=
pStipple-drawable.width)
{
int width;
if ((iX + pStipple-drawable.width) fullX2)
width = fullX2 - iX;
else
width = pStipple-drawable.width;
BitBlt (pGCPriv-hdcMem,
iX, fullY1,
width, 1,
hdcStipple,
0,
fullY1 % pStipple-drawable.height,
g_copyROP[pGC-alu]);
}
pbox++;
}
Re: Just a note - nativegdi engine
On Wed, Apr 10, 2002 at 01:47:58AM +1000, Robert Collins wrote: Creating a single combined clipping region using CombineRgn will allow you to move the for (iX= ..)loop from within the while (nbox--) loop, thus saving multiple selectClipRgn+deleteObject + bitblt calls, which may make the native engine quite a bit faster. I *will* do this optimisation here and elsewhere, but only after I get the fills working for 'native' windows first. Shucks... Re-read it. I understand what your saying now. Ignore that last one. Alan.
RE: Xfree and OpenGL
David, Just as a sanity check, you have run non OpenGL applications from your SGI machine using Cygwin/XFree86, right? I mean, it wouldn't make much sense to jump right into debugging complex applications if an xterm doesn't work correctly. Just let us know that you have in fact done this. Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Komanek Sent: Tuesday, April 09, 2002 11:07 AM To: [EMAIL PROTECTED] Subject: Re: Xfree and OpenGL Dear Alan, thanks for your comments/advices. I tried glxgears and it works. The gears are not rotating fluent enough on my 800MHz pentium, but I don't expect this is related to my problem. I am able to start xterm, swmgr, toolchest connecting to SGI 6.5.14 box which probably use classical X11 and Motif library only. Trying to start i.e. jot, it claims: dgl error (protocol): remote machine not DGL capable - meda:10.0 dgl error (default init): default dglopen(meda:10.0,4) returned -13 Connecting to another box, running IRIX 6.2, it is even worse - swmgr shows only the first Wait please window and then you can wait for hours and the main window does not appear. In the xterm you can see following message: WARNING: Not all colors for application icons could be allocated. Some interface elements may have different colors. Warning: creating new shape image Jot coredumps, many others too. Toolchest starts fine, but no apps called invoked from its menus. When I run this apps on the local graphics console of an SGI box, it works fine. Well, this problem is not connection type related (both ssh and telnet+xhost produce same results). Probably should I install something on the SGI boxes to translate DGL requests into the X11 protocol (rendered on the server side, but at least working) ? Any ideas are appreciated. David On Tue, Apr 09, 2002 at 02:43:13PM +0200, David Komanek wrote: Dear Harold, thank you for the reply. xdpyinfo shows that both named extensions are present. Is there some possibility to trace where is the problem (some debug mode for Xfree or so ?) David, There is a sample program called 'glxgears' which will draw three depth buffered rotating gears. If this works, you've got it all running. What's your application reporting ? Alan.
New Weight Loss Product
HTMLPREBODY BGCOLOR=#00FONT COLOR=#00 SIZE=3 Dear [EMAIL PROTECTED], IT'S COMING!!! GET READY TO LOOSE WEIGHT ANABOLIC WEIGHT LOSS IN LESS THAN 10 DAYS OASIS WILL LAUNCH A NEW ROCKET ! THE WORLD'S FIRST ANABOLIC WEIGHT LOSS SYSTEM! · A double blind, placebo controlled, clinically tested Weight Management System developed to Throw The Fat-Burning Switch! · A safe, consistent, long lasting way to lose weight, maintain muscle and become healthier. · Nutritional fuel formulated to activate the body's natural Power Centers that fight FAT! · No Ephedra! No Ma Huang! No harmful stimulants! OASIS BEATS THE HEAVYWEIGHTS OF THE INDUSTRY! · Preliminary results are better than those published by the weight loss leaders! · Clinical trials show significant and consistent weight loss, plus bonus health benefits! · Participants reporting successful weight loss where other programs failed! FOR THE FIRST TIME EVER -- WEIGHT MANAGEMENT COMBINED WITH ANTI-AGING! COMING APRIL 20th !!! ONLY FROM OASIS WELLNESS FOR MORE INFO SEND NAME, E-MAIL ADDRESS AND/OR PHONE [EMAIL PROTECTED] ( 90 day money back guaranty on all Oasis Wellness products) Your choices regarding email are respected. If you would no longer like to receive correspondence from us, please click the following link: http://www.unsubscribesystem.com/1B156B47446753445171 /FONTFONT COLOR=#00 SIZE=3
New Weight Loss Product
HTMLPREBODY BGCOLOR=#00FONT COLOR=#00 SIZE=3 Dear [EMAIL PROTECTED], IT'S COMING!!! GET READY TO LOOSE WEIGHT ANABOLIC WEIGHT LOSS IN LESS THAN 10 DAYS OASIS WILL LAUNCH A NEW ROCKET ! THE WORLD'S FIRST ANABOLIC WEIGHT LOSS SYSTEM! · A double blind, placebo controlled, clinically tested Weight Management System developed to Throw The Fat-Burning Switch! · A safe, consistent, long lasting way to lose weight, maintain muscle and become healthier. · Nutritional fuel formulated to activate the body's natural Power Centers that fight FAT! · No Ephedra! No Ma Huang! No harmful stimulants! OASIS BEATS THE HEAVYWEIGHTS OF THE INDUSTRY! · Preliminary results are better than those published by the weight loss leaders! · Clinical trials show significant and consistent weight loss, plus bonus health benefits! · Participants reporting successful weight loss where other programs failed! FOR THE FIRST TIME EVER -- WEIGHT MANAGEMENT COMBINED WITH ANTI-AGING! COMING APRIL 20th !!! ONLY FROM OASIS WELLNESS FOR MORE INFO SEND NAME, E-MAIL ADDRESS AND/OR PHONE [EMAIL PROTECTED] ( 90 day money back guaranty on all Oasis Wellness products) Your choices regarding email are respected. If you would no longer like to receive correspondence from us, please click the following link: http://www.unsubscribesystem.com/1B156B47446753445171 /FONTFONT COLOR=#00 SIZE=3
How do I change fonts in xfree86?
Hi all I am using my CDE form a Solaris box on my local PC by ruining xfree86 this is what I type #xwin -noreset -screen 0 1152 864 -query server ip -from my pc ip And the fonts that I get are bold. How do I change the font size, bold, not bold, different font etc. Please help Thanks in advance Eli
New Weight Loss Product
HTMLPREBODY BGCOLOR=#00FONT COLOR=#00 SIZE=3 Dear [EMAIL PROTECTED], IT'S COMING!!! GET READY TO LOOSE WEIGHT ANABOLIC WEIGHT LOSS IN LESS THAN 10 DAYS OASIS WILL LAUNCH A NEW ROCKET ! THE WORLD'S FIRST ANABOLIC WEIGHT LOSS SYSTEM! · A double blind, placebo controlled, clinically tested Weight Management System developed to Throw The Fat-Burning Switch! · A safe, consistent, long lasting way to lose weight, maintain muscle and become healthier. · Nutritional fuel formulated to activate the body's natural Power Centers that fight FAT! · No Ephedra! No Ma Huang! No harmful stimulants! OASIS BEATS THE HEAVYWEIGHTS OF THE INDUSTRY! · Preliminary results are better than those published by the weight loss leaders! · Clinical trials show significant and consistent weight loss, plus bonus health benefits! · Participants reporting successful weight loss where other programs failed! FOR THE FIRST TIME EVER -- WEIGHT MANAGEMENT COMBINED WITH ANTI-AGING! COMING APRIL 20th !!! ONLY FROM OASIS WELLNESS FOR MORE INFO SEND NAME, E-MAIL ADDRESS AND/OR PHONE [EMAIL PROTECTED] ( 90 day money back guaranty on all Oasis Wellness products) Your choices regarding email are respected. If you would no longer like to receive correspondence from us, please click the following link: http://www.unsubscribesystem.com/1B156B47446753445171 /FONTFONT COLOR=#00 SIZE=3
New Weight Loss Product
HTMLPREBODY BGCOLOR=#00FONT COLOR=#00 SIZE=3 Dear [EMAIL PROTECTED], IT'S COMING!!! GET READY TO LOOSE WEIGHT ANABOLIC WEIGHT LOSS IN LESS THAN 10 DAYS OASIS WILL LAUNCH A NEW ROCKET ! THE WORLD'S FIRST ANABOLIC WEIGHT LOSS SYSTEM! · A double blind, placebo controlled, clinically tested Weight Management System developed to Throw The Fat-Burning Switch! · A safe, consistent, long lasting way to lose weight, maintain muscle and become healthier. · Nutritional fuel formulated to activate the body's natural Power Centers that fight FAT! · No Ephedra! No Ma Huang! No harmful stimulants! OASIS BEATS THE HEAVYWEIGHTS OF THE INDUSTRY! · Preliminary results are better than those published by the weight loss leaders! · Clinical trials show significant and consistent weight loss, plus bonus health benefits! · Participants reporting successful weight loss where other programs failed! FOR THE FIRST TIME EVER -- WEIGHT MANAGEMENT COMBINED WITH ANTI-AGING! COMING APRIL 20th !!! ONLY FROM OASIS WELLNESS FOR MORE INFO SEND NAME, E-MAIL ADDRESS AND/OR PHONE [EMAIL PROTECTED] ( 90 day money back guaranty on all Oasis Wellness products) Your choices regarding email are respected. If you would no longer like to receive correspondence from us, please click the following link: http://www.unsubscribesystem.com/1B156B47446753445171 /FONTFONT COLOR=#00 SIZE=3
some help with xWin
All - I have succesfully installed cygwin/xfree and when attempting to use XWin with XDM for solaris even using the -fp tcp/box:7100, I get a creen that is grey with a X as the cursor. Can anyone help on what I am doing wrong? I have attached 2 snapshots David S. Lee Manager, Technical Operations Managed Objects, Inc. 7925 Westpark Drive McLean, VA 22102 Office: 703-208-3330 Cell:415-250-6115 snap.gif snap.gif David S. Lee Manager, Technical Operations Managed Objects, Inc. 7925 Westpark Drive McLean, VA 22102 Office: 703-208-3330 Cell:415-250-6115 snap.gif Description: GIF image snap.gif Description: GIF image
Re: info: single install xfree86 + minimal cygwin?
Christopher Faylor wrote: Yep, as Robert indicated, this has been possible for a while. For Cygwin/XFree86, what I'd like to do is have you all come up with a few .tar.bz2 files which install into a /usr/X11R6, /etc/X11, etc. I repackaged the current .tgz files as .tar.bz2 files. I created a rudimentary setup.ini file and was able to install them with setup.exe from a local directory. I haven't yet created a proper hierarchy setup.hint files. The hierarchy would be something like: xfree base setup.hint XFree-4.2.0-1.tar.bz2 XFree-4.2.0-1-src.tar.bz2 doc setup.hint XFree-doc-4.2.0-1.tar.bz2 devel setup.hint XFree86-devel-4.2.0-1.tar.bz2 XFree86-devel-4.2.0-1-src.tar.bz2 The packages I made were: xfree-base-4.2.0.tar.bz2 (11MB; Xbin, Xman, Xlib, Xxserv, Xetc) xfree-devel-4.2.0.tar.bz2 (595kB; Xprog) xfree-doc-txt-4.2.0.tar.bz2 (1.3MB; Xdoc) xfree-doc-html-4.2.0.tar.bz2 (905kB; Xhtml) xfree-doc-ps-4.2.0.tar.bz2 (4.4MB; Xps) xfree-fonts-100dpi-4.2.0.tar.bz2 (12MB; Xf100) xfree-fonts-4.2.0.tar.bz2 (18MB; Xfnts, Xfscl, Xfenc; required) xfree-fonts-cyrillic-4.2.0.tar.bz2 (364kB, Xfcyr) xfree-xfs-4.2.0.tar.bz2 (202kB; Xfsrv) xfree-xnest-4.2.0.tar.bz2 (1.1MB; Xnest) xfree-xprt-4.2.0.tar.bz2 (791kB; Xprt) xfree-xvfb-4.2.0.tar.bz2 (1.2MB; Xvfb) Is it possible to have multiple packages in a subdirectory and setup.hint file? Or does each package needs its own directory? For a hierarchy, I was thinking: base, devel, doc, fonts, and progs (for the optional servers). There are a couple of refinements that can be made to the repackaging. First, the 75dpi fonts make up the bulk (10MB) of the fonts package and aren't strictly required. They could be made their own package. The miscellaneous fonts could be folded into the base package so there is only one required package. Second, move the man3 man pages into the devel package. Also, move the .a files in /usr/X11R6/lib into devel. That reduces the base package by a couple MB. - Ian -- [EMAIL PROTECTED] http://www.znark.com/
RE: info: single install xfree86 + minimal cygwin?
-Original Message- From: Ian Burrell [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 9:49 AM Is it possible to have multiple packages in a subdirectory and setup.hint file? Or does each package needs its own directory? Each package needs it's own directory. For a hierarchy, I was thinking: base, devel, doc, fonts, and progs (for the optional servers). I'm not clear not the hierarchy there - that reads like a list to me. You've got two clauses you can independently use to make a hierarchy and package dependencies - category:(i.e. the devel tarball belongs in XFree86 and in Devel) and requires: (i.e. the server package requires the fonts and the programs and ...) There are a couple of refinements that can be made to the repackaging. First, the 75dpi fonts make up the bulk (10MB) of the fonts package and aren't strictly required. They could be made their own package. The miscellaneous fonts could be folded into the base package so there is only one required package. Second, move the man3 man pages into the devel package. Also, move the .a files in /usr/X11R6/lib into devel. That reduces the base package by a couple MB. Those refinements can be made at any point - there's no need to have it perfect on first release. Setup.exe is quite capable of handling files moving from one package to another now. Rob
Re: info: single install xfree86 + minimal cygwin?
Robert Collins wrote: I'm not clear not the hierarchy there - that reads like a list to me. You've got two clauses you can independently use to make a hierarchy and package dependencies - category:(i.e. the devel tarball belongs in XFree86 and in Devel) and requires: (i.e. the server package requires the fonts and the programs and ...) That is a list of subdirectories. But it won't work since the each package needs its own subdirectory. A better hiearchy would use the components from the package names. Hopefully, multiple levels of subdirectories will work. xfree: base: xfree-base-4.2.0.tar.bz2 devel: xfree-devel-4.2.0.tar.bz2 doc: html: xfree-doc-html-4.2.0.tar.bz2 ps: xfree-doc-ps-4.2.0.tar.bz2 txt: xfree-doc-txt-4.2.0.tar.bz2 fonts: 100dpi: xfree-fonts-100dpi-4.2.0.tar.bz2 75dpi: xfree-fonts-75dpi-4.2.0.tar.bz2 misc: xfree-fonts-misc-4.2.0.tar.bz2 xfs: xfree-xfs-4.2.0.tar.bz2 xnest: xfree-xnest-4.2.0.tar.bz2 xprt: xfree-xprt-4.2.0.tar.bz2 xvfb: xfree-xvfb-4.2.0.tar.bz2 Those refinements can be made at any point - there's no need to have it perfect on first release. Setup.exe is quite capable of handling files moving from one package to another now. They were simple changes to the script I wrote to repackage the distributed archives. I'll try to write proper setup.hint files for all the packages. - Ian -- [EMAIL PROTECTED] http://www.znark.com/
RE: info: single install xfree86 + minimal cygwin?
-Original Message- From: Ian Burrell [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 10:57 AM That is a list of subdirectories. But it won't work since the each package needs its own subdirectory. A better hiearchy would use the components from the package names. Hopefully, multiple levels of subdirectories will work. xfree: base: ... xvfb: xfree-xvfb-4.2.0.tar.bz2 As a directory layout, that should be fine. Those refinements can be made at any point - there's no need to have it perfect on first release. Setup.exe is quite capable of handling files moving from one package to another now. They were simple changes to the script I wrote to repackage the distributed archives. I'll try to write proper setup.hint files for all the packages. Cool. Rob
Re: info: single install xfree86 + minimal cygwin?
On Tue, Apr 09, 2002 at 05:56:36PM -0700, Ian Burrell wrote: Robert Collins wrote: I'm not clear not the hierarchy there - that reads like a list to me. You've got two clauses you can independently use to make a hierarchy and package dependencies - category:(i.e. the devel tarball belongs in XFree86 and in Devel) and requires: (i.e. the server package requires the fonts and the programs and ...) That is a list of subdirectories. But it won't work since the each package needs its own subdirectory. A better hiearchy would use the components from the package names. Hopefully, multiple levels of subdirectories will work. xfree: base: xfree-base-4.2.0.tar.bz2 devel: xfree-devel-4.2.0.tar.bz2 doc: html: xfree-doc-html-4.2.0.tar.bz2 ps: xfree-doc-ps-4.2.0.tar.bz2 txt: xfree-doc-txt-4.2.0.tar.bz2 fonts: 100dpi: xfree-fonts-100dpi-4.2.0.tar.bz2 75dpi: xfree-fonts-75dpi-4.2.0.tar.bz2 misc: xfree-fonts-misc-4.2.0.tar.bz2 xfs: xfree-xfs-4.2.0.tar.bz2 xnest: xfree-xnest-4.2.0.tar.bz2 xprt: xfree-xprt-4.2.0.tar.bz2 xvfb: xfree-xvfb-4.2.0.tar.bz2 Those refinements can be made at any point - there's no need to have it perfect on first release. Setup.exe is quite capable of handling files moving from one package to another now. They were simple changes to the script I wrote to repackage the distributed archives. I'll try to write proper setup.hint files for all the packages. There's no need to go into too much information in the ldesc, fwiw. And, the sdesc field can be pretty brief, too, IMO. If you have Red Hat linux installed somewhere, you might be able to get some info from the 'rpm -q -i' command, applying it to various installed XFree86 packages. Btw, should the directory be called xfree or xfree86 or XFree86? I assume the category for this should be XFree86, right? cgf
Re: info: single install xfree86 + minimal cygwin?
Robert Collins wrote: They were simple changes to the script I wrote to repackage the distributed archives. I'll try to write proper setup.hint files for all the packages. Cool. I'm unclear about how the -src packages (are/should be) handled, since there are a great many binary packages in XFree, but only a few original source packages. In the past, when multiple binary packages are generated from a single source package, we've done the following: ncurses-5.2-?-src.tar.bz2 contains the actual src dist for ncurses/libncurses, with cygwin patches, build scripts, etc However, building this -src generates two binary packages: ncurses-5.2-?.tar.bz2 libncurses6-5.2-?.tar.bz2 So, we create an empty libncurses6-5.2-?-src.tar.bz2 that contains only a single README that says go look over there, in ncurses-5.2-?-src.tar.bz2. Now, this works, and upset/setup are happy (every binary package has a src package) but it is hackish, ugly, and a pain to maintain. Is there a better solution? (Or can we discard the psuedo-src packages without repurcussion? Won't upset be upset by the bin without src problem?) --Chuck
Re: info: single install xfree86 + minimal cygwin?
On Tue, Apr 09, 2002 at 09:43:54PM -0400, Charles Wilson wrote: If it is upset I'll be upset. It should be acceptable to have bin without source. If it causes a problem, I'll fix it. That's great. (I'm not planning on needlessly changing my packages, but perhaps the next time they must be updated for other reasons, I'll drop the psuedo-src packages). However, is there any way we can add to the setup/upset grammar an optional keyword like: (within libncurses6's setup.hint) external-src: ncurses This would require conflict avoidance within setup.exe, too -- the src chkboxes for ncurses and libncurses6 should be tied together in this case... Or is this just not worth worrying about? I like the idea as far as upset is concerned. It would be easy to add. However, maybe the setup.exe part would be hairy. cgf
Re: info: single install xfree86 + minimal cygwin?
On Tue, Apr 09, 2002 at 06:34:29PM -0700, Ian Burrell wrote: Is the script for building setup.ini files from a directory hierarchy available anywhere? I want to setup a test install directory with the full hierarchy and setup.hint files. Also, I ran into a problem with the xfree-fonts-100dpi and xfree-fonts-75dpi packages. With a hand-generated setup.ini, they weren't being displayed. This might be because the last component starts with a number and something is confused about where the version starts. Yes, a -75dpi part of a tar file will look like a version number. Can you use an underscore instead? Just to be clear, you shouldn't be including the '@ xfree-fonts-100dpi' or the version: in the setup.hint. Those are only needed if you are overriding defaults. cgf The lines in my setup.ini are: @ xfree-fonts-100dpi sdesc: Cygwin/XFree86 100dpi fonts category: XFree86 requires: xfree-base version: 4.2.0-1 @ xfree-fonts-75dpi sdesc: Cygwin/XFree86 75pi fonts category: XFree86 requires: xfree-base version: 4.2.0-1 - Ian -- [EMAIL PROTECTED] http://www.znark.com/
RE: info: single install xfree86 + minimal cygwin?
-Original Message- From: Charles Wilson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 11:23 AM Now, this works, and upset/setup are happy (every binary package has a src package) but it is hackish, ugly, and a pain to maintain. Is there a better solution? (Or can we discard the psuedo-src packages without repurcussion? Won't upset be upset by the bin without src problem?) Setup won't be. It won't allow the src box to be ticked unless it knows of a src package details. Rob
Re: info: single install xfree86 + minimal cygwin?
Christopher Faylor wrote: Yes, a -75dpi part of a tar file will look like a version number. Can you use an underscore instead? I could use an underscore. I got it to work by changing it to dpi75. Shouldn't the name in the setup.ini file override that version number parsing? - Ian -- [EMAIL PROTECTED] http://www.znark.com/
RE: info: single install xfree86 + minimal cygwin?
-Original Message- From: Charles Wilson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 12:19 PM I don't think it's that big a deal to require cygwin packages to follow a parseable naming scheme; ours is pretty lenient...when it fails, it's not a terrible imposition to either change a '-' to a '_', or swap some digits and alphabetics within a -- word. And package file names are not directly used by humans 99% of the time. That's what setup + cygcheck + upset are for. Rob
makeNativeRgn
Alan,
this may be of use to you: It's the region optimisation I mentioned
before. It seems a little faster to me, which indicates that some
(most?) of the calls have mulitple clip regions.
There's a little extra stuff for the rootless mode in win.h, but it
won't hurt to have that committed - if you're willing.
There is also some rootless stuff (the #if 1-else-end and #if
0-else-end's) in winsetsp and winfillsp, and that stuff should NOT go
into CVS, but I didn't want to corrupt the patch by hand removing. You
should be able to do it easily in your sandbox... (it's only 2-3 lines
to delete).
Index: win.h
===
RCS file: /cvsroot/xoncygwin/xc/programs/Xserver/hw/xwin/win.h,v
retrieving revision 1.1.1.1.2.2
diff -u -p -r1.1.1.1.2.2 win.h
--- win.h 5 Feb 2002 18:47:39 - 1.1.1.1.2.2
+++ win.h 10 Apr 2002 02:39:46 -
@@ -268,7 +268,8 @@ typedef Bool (*winHotKeyAltTabPtr)(Scree
typedef struct
{
- DWORDdwDummy;
+ HWND hwnd;
+ HDC hdc;
} winPrivWinRec, *winPrivWinPtr;
typedef struct
@@ -414,6 +415,7 @@ extern miPointerScreenFuncRec g_winPoint
extern DWORD g_dwEvents;
extern int g_fdMessageQueue;
extern int g_iScreenPrivateIndex;
+extern int g_iWindowPrivateIndex;
extern int g_iCmapPrivateIndex;
extern int g_iGCPrivateIndex;
extern int g_iPixmapPrivateIndex;
@@ -553,6 +555,8 @@ winBlockHandler (int nScreen,
RegionPtr
winPixmapToRegionNativeGDI (PixmapPtr pPix);
+HRGN
+makeNativeRgn (RegionPtr const pRegion);
/*
Index: winclip.c
===
RCS file: /cvsroot/xoncygwin/xc/programs/Xserver/hw/xwin/winclip.c,v
retrieving revision 1.1.1.1.2.1
diff -u -p -r1.1.1.1.2.1 winclip.c
--- winclip.c 7 Feb 2002 21:34:19 - 1.1.1.1.2.1
+++ winclip.c 10 Apr 2002 02:39:46 -
@@ -248,3 +248,33 @@ winPixmapToRegionNativeGDI (PixmapPtr pP
#endif
return(pReg);
}
+
+HRGN
+makeNativeRgn (RegionPtr const pRegion)
+{
+ BoxPtr pbox;
+ int nbox;
+ HRGN rv;
+ nbox = REGION_NUM_RECTS (pRegion);
+ pbox = REGION_RECTS (pRegion);
+ rv = CreateRectRgn (pbox-x1, pbox-y1, pbox-x2, pbox-y2);
+ --nbox;
+ ++pbox;
+ while (nbox--)
+{
+ int combinerv;
+ HRGN tempRgn;
+ tempRgn = CreateRectRgn (pbox-x1, pbox-y1, pbox-x2, pbox-y2);
+ combinerv = CombineRgn (rv, rv, tempRgn, RGN_OR);
+ if (combinerv == ERROR)
+ {
+ ErrorF (makeNativeRgn: Failed to create native region %u\n,
GetLastError());
+ DeleteObject (rv);
+ return NULL;
+ }
+ DeleteObject (tempRgn);
+ ++pbox;
+}
+ return rv;
+}
+
Index: winsetsp.c
===
RCS file: /cvsroot/xoncygwin/xc/programs/Xserver/hw/xwin/winsetsp.c,v
retrieving revision 1.1.1.1.2.8
diff -u -p -r1.1.1.1.2.8 winsetsp.c
--- winsetsp.c 19 Feb 2002 20:31:25 - 1.1.1.1.2.8
+++ winsetsp.c 10 Apr 2002 02:39:46 -
@@ -27,6 +27,7 @@
*
* Authors:Harold L Hunt II
* Alan Hourihane [EMAIL PROTECTED]
+ * Robert Collins [EMAIL PROTECTED]
*/
/* $XFree86: xc/programs/Xserver/hw/xwin/winsetsp.c,v 1.6 2001/10/22
15:21:12 alanh Exp $ */
@@ -48,8 +49,6 @@ winSetSpansNativeGDI (DrawablePtr pDrawa
HBITMAP hbmpOrig = NULL;
BITMAPINFO bmi;
HRGN hrgn;
- int n;
- BoxPtr pbox;
/* Branch on the drawable type */
switch (pDrawable-type)
@@ -67,8 +66,6 @@ winSetSpansNativeGDI (DrawablePtr pDrawa
while (iSpans--)
{
- n = REGION_NUM_RECTS (pGC-pCompositeClip);
- pbox = REGION_RECTS (pGC-pCompositeClip);
ZeroMemory (bmi, sizeof (BITMAPINFO));
bmi.bmiHeader.biSize = sizeof (BITMAPINFOHEADER);
@@ -85,14 +82,14 @@ winSetSpansNativeGDI (DrawablePtr pDrawa
bmi.bmiColors[1].rgbGreen = 255;
bmi.bmiColors[1].rgbRed = 255;
}
-
- while (n--)
+
+ hrgn = makeNativeRgn (pGC-pCompositeClip);
+ if (hrgn)
{
- hrgn = CreateRectRgn (pbox-x1, pbox-y1, pbox-x2,
pbox-y2);
SelectClipRgn (pGCPriv-hdcMem, hrgn);
DeleteObject (hrgn);
hrgn = NULL;
-
+
StretchDIBits (pGCPriv-hdcMem,
pPoints-x, pPoints-y,
*piWidths, 1,
@@ -102,7 +99,6 @@ winSetSpansNativeGDI (DrawablePtrpDrawa
(BITMAPINFO *) bmi,
DIB_RGB_COLORS,
g_copyROP[pGC-alu]);
- pbox++;
}
pSrcs += PixmapBytePad (*piWidths, pDrawable-depth);
@@
Re: info: single install xfree86 + minimal cygwin?
On Tue, Apr 09, 2002 at 07:10:15PM -0700, Ian Burrell wrote: Christopher Faylor wrote: Yes, a -75dpi part of a tar file will look like a version number. Can you use an underscore instead? I could use an underscore. I got it to work by changing it to dpi75. Shouldn't the name in the setup.ini file override that version number parsing? Name? Do you mean version? If you put a version in setup.hint it is currently ignored. If you try to use something like curr: 4.2.0-1 I believe that may confuse the upset parser. cgf
Re: info: single install xfree86 + minimal cygwin?
Christopher Faylor wrote: Name? Do you mean version? If you put a version in setup.hint it is currently ignored. The name from the @ line and the version header could be used to override the parsing of file names into name and version. - Ian -- [EMAIL PROTECTED] http://www.znark.com/
Re: info: single install xfree86 + minimal cygwin?
On Tue, Apr 09, 2002 at 07:50:04PM -0700, Ian Burrell wrote: Christopher Faylor wrote: Name? Do you mean version? If you put a version in setup.hint it is currently ignored. The name from the line and the version header could be used to override the parsing of file names into name and version. No, the name doesn't override this, currently. cgf
xfree packages
I finished making some xfree packages. They are distributed binary archives repackaged as cygwin packages. I made a package directory that can be used with setup.exe from a local directory and over the network. I changed my mind about the division of the packages I proposed. I got rid of the multiple doc and fonts packages cause I was having trouble with the naming and directories. Plus, I assumed the people would want to install them together. The packages are now: xfree-base xfree-devel xfree-docs xfree-fonts xfree-xfs xfree-xnest xfree-xvfb xfree-xprt I don't have a machine that people can easily download the full files from. I can post the setup.* files and scripts I used to build the packages. - Ian -- [EMAIL PROTECTED] http://www.znark.com/
