This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: Annoying DOS boxes when using startxwin.bat
- To: "Robert Collins" <robert dot collins at itdomain dot com dot au>, "cygx" <cygwin-xfree at cygwin dot com>
- Subject: RE: Annoying DOS boxes when using startxwin.bat
- From: "Harold Hunt" <huntharo at msu dot edu>
- Date: Mon, 1 Oct 2001 21:46:31 -0400
I like your idea. Assuming that it is possible though, I believe we would
still need to pass those compilation flags to prevent the DOS consoles from
popping up (especially on Windows 95/98/Me, which don't have 'start /B').
I'll admit I'm out of my league on figuring out how to do a virtual console
for all of the X programs...
Harold
> -----Original Message-----
> From: Robert Collins [mailto:robert.collins@itdomain.com.au]
> Sent: Monday, October 01, 2001 9:52 PM
> To: Harold Hunt; cygx
> Subject: RE: Annoying DOS boxes when using startxwin.bat
>
>
> This is just thinking-out-loud, but it sounds to me like what is needed
> is a virtual console for all the X proggys to write their output to.
> Something like the real X root console.
>
> And then _that_ becomes the route for output to a file vs output to a
> cygwin console (which BTW != dos box - it can be, or it can be a rxvt
> term, or a virtual console like ssh uses).
>
> Thoughts?
>
> Rob
>
> > -----Original Message-----
> > From: Harold Hunt [mailto:huntharo@msu.edu]
> > Sent: Tuesday, October 02, 2001 11:39 AM
> > To: cygx
> > Subject: Annoying DOS boxes when using startxwin.bat
> >
> >
> > I've just added functionality to send XWin.exe error messages
> > to a log file,
> > therefore I have also changed XWin.exe from a DOS executable
> > to a Windows
> > executable (by passing -mwindows -e _mainCRTStartup to gcc in
> > link stage).
> > This change prevents XWin.exe from opening a DOS window for
> > console output
> > when using startxwin.bat.
> >
> > However, other programs in startxwin.bat, such as twm.exe,
> > xterm.exe, and
> > xsetroot.exe will cause the window for startxwin.bat to stay
> > open after
> > those programs have started. One way to prevent this is to
> > add the above
> > link flags to each of the X clients. Another way would be to use
> > startxwin.sh instead of startxwin.bat; however, you will give up the
> > double-click start functionality if you choose that route.
> >
> > So, I'm wondering what people think about passing those
> > compilation flags to
> > each of the X clients. I tried it with twm.exe and didn't notice any
> > adverse effect.
> >
> > Alan, is there an easy way to pass those compilation flags to
> > each X client,
> > like the EXTRA_LDOPTIONS that we use for XWin.exe?
> >
> > Harold
> >
> >