public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: new start method questions
Date: Fri, 10 Jun 2016 02:27:00 -0000 [thread overview]
Message-ID: <d3afa28f-1560-26c7-e6d3-1ab1df56793b@gmail.com> (raw)
In-Reply-To: <7892d5e91645a81686d1d3f2f40c0fe0@saf.bio.caltech.edu>
On 10/06/2016 02:55, mathog wrote:
> 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
> /usr/bin/startxwin"
>
> 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.
>
look on
/etc/X11/xinit/startxwinrc
It is calling xwin-xdg-menu
Regards
Marco
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2016-06-10 2:27 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
2016-06-10 2:27 ` Marco Atzeri [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d3afa28f-1560-26c7-e6d3-1ab1df56793b@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).