Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <19991009212638.9005.rocketmail@web108.yahoomail.com> Date: Sat, 9 Oct 1999 14:26:38 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: windows consoles To: Laszlo Vecsey , cygwin AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Laszlo Vecsey wrote: > Is it possible to make a windows executable that can optionally output to > a console at runtime? > > Normally when I compile with -mwindows, I can't printf to the console, and > windows returns me to the prompt when I run the program. I found that if I > include -luser32 and -lgd32 manually, and leave -mwindows out, I can still > use WinMain and do graphics, and still have the console! > > The problem with that is its all done at compile time, and I would need > two different binaries to get the different behaviors. What I'd like to do > now is compile just one binary and be able to determine at runtime > (through a commandline option) if windows should return me to the prompt > (no console), or stick around and let me write to stdout. Can this be > done? Isn't there a CreateConsole() function? ===== Earnie Boyd Newbies, please visit (If you respond to the list, then please don't cc me) __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com