This is the mail archive of the
mailing list for the Cygwin project.
Re: Command-line options for setup.exe
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Robert Collins <rbcollins at cygwin dot com>
- Cc: Max Bowsher <maxb at ukf dot net>, <cygwin at cygwin dot com>
- Date: Tue, 25 Feb 2003 18:26:03 -0500 (EST)
- Subject: Re: Command-line options for setup.exe
- Reply-to: cygwin at cygwin dot com
On 26 Feb 2003, Robert Collins wrote:
> On Wed, 2003-02-26 at 09:46, Max Bowsher wrote:
> > Igor Pechtchanski wrote:
> > > On Tue, 25 Feb 2003, Max Bowsher wrote:
> > >> No, building it as a MinGW app is fine.
> > >> But it must be run from a CYGWIN=tty shell.
> > >
> > > Oh, ok. I don't use "tty" myself, so I needed it built as a Cygwin
> > > app. Could it, perhaps, pop up a dialog box instead if stdout is not
> > > available? Is there any way of detecting whether output to stdout
> > > will be seen?
> > Detection is the tricky part. I can't figure out how.
> I wouldn't bother with detection. setup.exe is a gui, it's fine for it
> to show help as a gui.
> What is needed is this:
> The current libgetopt call to show the parameter help should become a
> convenience call over a lower interface.
> That interface should:
> * Provide a const interator to all the options in the optionset.
> That will let setup iterate over the options, extracting the help text
> and placing into a GUI text area (or a combobox etc etc).
Hmm, build a const String and pop up a MessageBox?
> This is also on my TODO, and why I haven't applied your trivial 'add
> help' option to setup - because it will need to be changed no matter
|\ _,,,---,,_ pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`' -. ;-;;,_ igor at watson dot ibm dot com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html