cygwin-innards-guru [Chris] - please comment RE: Windows server executable (as opposed to current CLI executable)

[Robert Collins]

Perhaps a better way would be to

before opening the server window, check to see if the parent process is
a cygwin process 
- if it is, operate as today.
- if it isn't, hide the console window that was automatically-opened.

I can just hear you saying "but why?". 
1) Lame folk like me that use startx will get the expected behaviour :]
2) there'll be no need to tail a file to see the output for debugging
purposes.
 
Unfortunately I don't know enough about the cygwin innards to point you
at the appropriate functions - thus the title...

Rob

> -----Original Message-----
> From: Harold Hunt [ mailto:huntharo@msu.edu ]
> Sent: Sunday, April 29, 2001 6:08 AM
> To: Cygx (E-mail)
> Subject: Windows server executable (as opposed to current CLI
> executable)
> 
> 
> I'd like to make the server a Windows executable, rather than a CLI
> executable, as this gets rid of the annoying command prompt 
> window that
> opens with each server window.  I have found, built, and 
> tested the extra
> compilation flags needed to make the server a Windows 
> executable; simply add
> the following flags to the final link of XWin.exe:
> 
> -mwindows -e _mainCRTStartup
> 
> There are two things holding me up from committing these changes:
> 1) I don't know how to specify flags to be used only when 
> linking the server
> executable.
> 2) stderr needs to be redirected to a file; however, it 
> doesn't make sense
> to pursue this until (1) has been addressed.
> 
> Any help and/or tips would be appreciated,
> 
> Harold
> 
>