Re: install location of X11 apps
> "Trevor" == Trevor Forbes <[EMAIL PROTECTED]> writes: Trevor> I would like to profer, as a general rule, that all "x11 only" apps to Trevor> have the --prefix=/usr/x11r6 rather than the present --prefix=/usr... It Trevor> makes it easer to manage the separation between x and non-x apps by Trevor> paths. Trevor> That is put all X-apps in: Trevor> /usr/X11r6/bin Trevor> /usr/X11r6/include Trevor> /usr/X11r6/lib Trevor> ...etc Trevor> It will also help reduce the number of files placed in /bin Trevor> What do you think? I favour that. Trevor> Trevor Ciao Volker
Re: pkgconfig [Was By the way... ]
Steven O'Brien wrote: > > There was no circular dependency for glib-1.2.10. In fact when I ported > it I had never heard of pkg-config. Oh, I misunderstood you. When you said you configured pkgconfig to build against your installed version of glib, I thought your installed version was 1.3.x, not 1.2.10. (1.3.x does depend on pkgconfig) Sorry for the confusion. > Anyway, I have built > pkgconfig-0.12.0, with your patch, and gnome-vfs configure works fine > with it. So if/when it is adopted as the "official" cygwin version I > will remove pkg-config from my website. Look for an updated package soon, and thanks for taking the time to test this. --Chuck
install location of X11 apps
I would like to profer, as a general rule, that all "x11 only" apps to have the --prefix=/usr/x11r6 rather than the present --prefix=/usr... It makes it easer to manage the separation between x and non-x apps by paths. That is put all X-apps in: /usr/X11r6/bin /usr/X11r6/include /usr/X11r6/lib ...etc It will also help reduce the number of files placed in /bin What do you think? Trevor
Re: xdmcp font problem
Hi, This is more of a workaround then a solution, your linux box is probably running a local font server. So you can use this to provide the fonts and probably avoid a crash. assuming the x font server is only available locally, you'll need to change it to use the network. below is a link detailing how to do this on linux mandrake. http://www.jeremywilkins.freeserve.co.uk/extend/remoteFontServer.html You then need to tell Xwin to use that font server, by adding "-fp tcp/:7100" without the quotes to the command line, eg. Xwin -query computerA -fp tcp/computerA:7100 -fullscreen Hope this helps Jeb - Original Message - From: "Lars Jensen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 01, 2002 11:04 PM Subject: xdmcp font problem > When I connect to a remote Linux box from my cygwin/xfree PC, and run > abiword through the connection, abiword crashes complaining that > > "cannot add fonts to the X font path" > > Then Abiwork crashes. > > I have 75dpi, 100dpi and scalable font (Xfscl) installed on the > Cygwin/xfree system. > > This does not happen when I login from the console on the linux box and > run abiword on the linux box, so the problem is not on the linux box. > Also this does not happen when I login with xdmcp to the linux box from > another linux box, and run abiword remotely. > > Any ideas how I might fix this? > > Thanks, > Lars. > > -- > Lars Jensen, TMCC/Vista B200, 7000 Dandini Blvd, Reno NV 89512-3999. > Internet: <[EMAIL PROTECTED]>, http://www.scsr.nevada.edu/~jensen > Tel: 775.673.7113 FAX: 775.674.7592 > >
source for xview
ftp://ftp.step.polymtl.ca/pub/Xview/libs/xview/Xview-3.2p1.4 __ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com
xdmcp font problem
When I connect to a remote Linux box from my cygwin/xfree PC, and run abiword through the connection, abiword crashes complaining that "cannot add fonts to the X font path" Then Abiwork crashes. I have 75dpi, 100dpi and scalable font (Xfscl) installed on the Cygwin/xfree system. This does not happen when I login from the console on the linux box and run abiword on the linux box, so the problem is not on the linux box. Also this does not happen when I login with xdmcp to the linux box from another linux box, and run abiword remotely. Any ideas how I might fix this? Thanks, Lars. -- Lars Jensen, TMCC/Vista B200, 7000 Dandini Blvd, Reno NV 89512-3999. Internet: <[EMAIL PROTECTED]>, http://www.scsr.nevada.edu/~jensen Tel: 775.673.7113 FAX: 775.674.7592
compiled qvwm fine, but!!
Hello All, I have been able to compile the QVWM into an qvwm.exe file but now want to move it out of the c:/cygwin/new directory that I can see when I run the shell. I tried to run it, but windows reports an error: libICE.dll could not be found. What dll's do I need to take the qvwm out of the shell space into a regular windows file space and where is this libICE.dll stored? Thanks in advance, Lonnie
compiling qvwm or blwm
Hello All, I am new to this list and have just been running the cygwin setup.exe program to try and get the compiler installed. In my current project, I would like to see about compiling either QVWM or BLWM so that I could run them under windows and was wondering if anyone has been able to do this? any help would be greatly appreciated. Cheers, Lonnie
Windowmaker gived error message upon start
Hi All, I was very happy to see the Windowmaker port and installed it. I did the initial config to make the GNUStep directory, then started it by putting "exec wmaker" inside .xinitrc. I get the error "Procedure entry point TiffGetFieldDefaulted could not be located in dynamic link library cygtiff3.dll." I imagine that there is something I need to update, or maybe I need to update everything. I wonder if someone can confirm that before I start downloading Mb. I think the version of Cygwin I am using is 1.3.9-1, at least thats what the install log says. Thanks, Rob.
Re: Cygwin/XFree86 setup.exe package problem
Harold Hunt wrote in <[EMAIL PROTECTED]> in gmane.os.cygwin.xfree on Sat, 27 Apr 2002 23:17:07 -0400: > That's because I screwed up when I modified Ian's build.sh script. I forgot > to make the symbolic links part of the Xlib package... and I think I > accidentally made the Xetc package contain invalid links. Oh well. I fixed > it now, I think. > I put a new setup.ini and XFree86-lib-4.2.0-2.tar.bz2 at > ftp://huntharo-4.user.msu.edu/pub/cygwin/ There is still a problem Harold. The links I'm getting have the correct directory names but aren't rooted i.e. app-defaults -> etc/X11/app-defaults fs -> etc/X11/fs lbxproxy -> etc/X11/lbxproxy proxymngr -> etc/X11/proxymngr rstart -> etc/X11/rstart twm -> etc/X11/twm xdm -> etc/X11/xdm xinit -> etc/X11/xinit xserver -> etc/X11/xserver xsm -> etc/X11/xsm You could link them like XftConfig and xkb are; app-defaults -> ../../../../etc/X11/app-defaults fs -> ../../../../etc/X11/fs lbxproxy -> ../../../../etc/X11/lbxproxy proxymngr -> ../../../../etc/X11/proxymngr rstart -> ../../../../etc/X11/rstart twm -> ../../../../etc/X11/twm xdm -> ../../../../etc/X11/xdm xinit -> ../../../../etc/X11/xinit xserver -> ../../../../etc/X11/xserver xsm -> ../../../../etc/X11/xsm -- Sam Edge
Cygwin XFree starting problem.
I'm currently facing the following Problem (which I've read questions about in this mailing list, but no answers): When I start XWin with startxwin.bat, startxwin.sh or with console always the same thing happens: For every xterm (which I started through the script) and for the Windowmanager (I tryed twm as well as icewm) a DOS Box opens. Then a window for XWin opens (I'll call it the white window from now on, but all that shows up in this one is a big white screen and on the upper left corner there seems to be the windowmanager with the xterms but its just way to small (about 80x100 pixel) to recognise it. When I close the xterm DOS boxes the black box on the upper left corner dissapears. The curser dissappers when I move it into the 'white window' but when I click into the left upper corner there seems to open a dialog window which starts to a appear the way I move the invisible mouse pointer over it. That's it for the problem description here's what my computer's like: I'm running Win98SE with DirectX Version 4.08.00.400 installed. I installed XFree with the Xinstall.sh in binary mode (I tryed to install it at first with the cygwin setup tool with the same result, but deinstalled that before reinstallation) The paths seem to be allright and nothing seems to be missing. I have a 100BaseT Network card, and standard (I guess) components else. At the first startup the XWin.log looked like this: ddxProcessArgument () - Initializing default screens winInitializeDefaultScreens () - w 1280 h 1024 ddxProcessArgument () - screen - argc: 5 i: 1 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines () - Windows 95/98/Me winDetectSupportedEngines () - DirectDraw installed winDetectSupportedEngines () - DirectDraw4 installed winDetectSupportedEngines () - Returning, supported engines 0017 winSetEngine () - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL () - Using Windows display depth of 16 bits per pixel winAdjustForAutoHide - Original WorkArea: 0 0 991 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 991 1280 winCreateBoundingWindowWindowed () - WindowClient w 1274 h 961 r 1274 l 0 b 961 t 0 winCreateBoundingWindowWindowed () - Returning winAllocateFBShadowDDNL () - lPitch: 2548 winInitVisualsShadowDDNL () - Masks f800 07e0 001f BPRGB 6 d 8 winLayerCreate () - dwDepth 8 winScreenInit () - returning Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! winCloseScreenShadowDDNL () - Freeing screen resources But ever after it looks like this: ddxProcessArgument () - Initializing default screens winInitializeDefaultScreens () - w 1280 h 1024 ddxProcessArgument () - screen - argc: 5 i: 1 According to the FAQ the 'unix should be set to root' shouldn't be a problem, and afaik the fonts that weren't found are optional Could you please help me with this? Many thanks in advance! Jens Drozd (Sorry for this long mail, but I wanted to describe it the best I could)
Re: pkgconfig [Was By the way... ]
On Tue, 30 Apr 2002 16:55:50 -0400 Charles Wilson <[EMAIL PROTECTED]> wrote: > What was the rationale for removing the included glib? It was put > into pkgconfig in order to break the recursive dependence: glib > requires pkgconfig which requires glib which ... > > Granted, the version of glib included in pkgconfig is old (but it's > capable enough for what pkgconfig needs) and has a one-line bug when > compiling on cygwin; I just patch that and move on... > > Anyway, if your version of pkgconfig (0.8.0 + local glib) compiled > gnome-vfs (on a particular date), yet the "official" cygwin version of > pkgconfig (0.10.0) failed to do so: > > I would think the problem is either: >something broke in the real pkgconfig sources between 0.8.0 and >0.10.0 or >gnome-vfs (on the particular date) was either exploiting a bug in > pkgconfig-0.8.0, or was otherwise broken. > > I don't think the answer is to use (and recommend) that cygwinners who > want gnome use a old version of pkgconfig with a circular > dependency... > > Thanks for offering to try with "real" pkgconfig-0.12.0. You'll > probably need to apply this patch (if you keep the included static > glib): > > --- pkgconfig-0.10.0-orig/glib-1.2.8/gstrfuncs.cMon Apr 17 > 11:05:16 2000 > +++ pkgconfig-0.10.0/glib-1.2.8/gstrfuncs.c Sat Feb 23 01:38:15 > 2002@@ -671,7 +671,7 @@ > char *msg; > > #ifdef HAVE_STRSIGNAL > - extern char *strsignal (int sig); > + extern const char *strsignal (int sig); > return strsignal (signum); > #elif NO_SYS_SIGLIST > switch (signum) > > I look forward to seeing the results of your experiment. There was no circular dependency for glib-1.2.10. In fact when I ported it I had never heard of pkg-config. Anyway, I have built pkgconfig-0.12.0, with your patch, and gnome-vfs configure works fine with it. So if/when it is adopted as the "official" cygwin version I will remove pkg-config from my website. Steven