public inbox for
help / color / mirror / Atom feed
From: mathog <>
Subject: Re: new start method questions
Date: Fri, 10 Jun 2016 00:55:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 09-Jun-2016 16:32, mathog wrote:
> With an older version of Cygwin I had constructed a cut down
> distribution which included only the minimum pieces needed to run X11.
>  It was about 40Mb, installed.

This approach is not working well at all for the current release.  Last 
time around I just tossed things into a folder to temporarily hide them, 
and by process of elimination winnowed it down to that small size.  This 
time there are many, many, MANY more dll's that are required for the 
server to start, at least  via this method:

C:\cygwinX\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec 

For instance, cyggtk-x11-2.0.0.dll.  Take it out and the X11 server does 
not start.
That dll, according to "ldd" has everything but the kitchen sink linked 
into it.  It isn't linked directly into the server though, it is needed 
for "xwin-xdg-menu.exe",
an accessory program, which if removed from /usr/bin, also results in 
the server not starting.

Last time around the start bat script was just:

@echo off
set CYGXTOP=%~dp0
chdir "%CYGXTOP%\var\log\xwin"
move XWin.0.log.1 XWin.0.log.2
move XWin.0.log XWin.0.log.1
chdir "%CYGXTOP%\bin"
start Xwin :0 -multiwindow

Is there some reason that a similar cut down bat file would not work 
with the current cygwin X11 server? (With "-listen tcp" plus a windows 
firewall rule to only let it
talk to localhost.)


David Mathog
Manager, Sequence Analysis Facility, Biology Division, Caltech

Unsubscribe info:
Problem reports:

  reply	other threads:[~2016-06-10  0:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 23:32 mathog
2016-06-10  0:55 ` mathog [this message]
2016-06-10  2:27   ` Marco Atzeri
2016-06-10 17:05   ` mathog
2016-06-13 13:07     ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).