Mail Archives: cygwin/2004/10/13/17:04:44
On Wed, Oct 13, 2004 at 06:31:28PM +0100, Dave Korn wrote:
>> -----Original Message-----
>> From: cygwin-owner On Behalf Of Christopher Faylor
>> Sent: 13 October 2004 15:17
>
>> On Wed, Oct 13, 2004 at 01:01:07PM +0100, Dave Korn wrote:
>> >> -----Original Message-----
>> >> From: cygwin-owner On Behalf Of Rainer Hochreiter
>> >> Sent: 13 October 2004 08:32
>> >
>> >>is there a chance to install cygwin without gui dialog?
>> >>
>> >>my plan is to download all needed packages into a local
>> directory and
>> >>then install the packages from that local directory by
>> starting setup
>> >>from a command line without further user interaction.
>> >
>> >"setup.exe --help" gives this output, which for some bizarre
>> reason it
>> >places in the setup.log file...
>>
>> Probably because a GUI app can't communicate with the console.
>
>I thought if a GUI app called printf it generally caused a console to
>be opened for it. Maybe that's only with msvcrt. In any case, the
>fact is that it is being run from a cmdline and so it certainly can
>communicate with the console. The presence of command-line options in
>argc/argv could be taken as a fairly strong hint that it was being run
>from a shell rather than an icon. And there's always "isatty (1)" if
>you really really want to be sure.
This is a windows limitation. GUI apps (apps created with -mwindows)
can't send output to or receive input from the console. Of course, a
GUI can interpret command line information. It just cannot send output
to the console that started it.
You could use AllocConsole to create a separate console which the GUI
could then use, however.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -