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 Date: Fri, 1 Oct 1999 23:06:22 -0400 From: "'cgf AT cygnus DOT com'" To: Hongwei CHU Cc: "'cygwin AT sourceware DOT cygnus DOT com'" Subject: Re: Did somebody try to compile cygwin1.dll by VC++? Message-ID: <19991001230622.D4363@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: Hongwei CHU , "'cygwin AT sourceware DOT cygnus DOT com'" References: <01BF0CB8 DOT 86915350 AT NTYANTAI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <01BF0CB8.86915350@NTYANTAI>; from Hongwei CHU on Sat, Oct 02, 1999 at 09:37:56AM +0900 On Sat, Oct 02, 1999 at 09:37:56AM +0900, Hongwei CHU wrote: >>It is very unlikely that this would work. > >Would you please explain that in a little bit more detail? There are several places in cygwin which use g++ extensions. Even if you managed to compile it that doesn't mean that the cygwin DLL would naturally play better with MSVC DLLs. The Cygwin DLL implements it's own I/O subsystem. It's not going to be aware of the MSVC subsystem just because it was compiled with MSVC. Please don't ask for further explanations. Feel free to prove me wrong on this. This is one of those things where you can easily demonstrate if this works by trying it. -chris -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com