X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Olumide <50295 AT web DOT de> Subject: Re: Using Cygwin compiled libs in Visual Studio Date: Sat, 04 Apr 2009 20:55:42 +0100 Lines: 16 Message-ID: References: <49D26A62 DOT 40303 AT cygwin DOT com> <20090404181111 DOT GA30828 AT ednor DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <20090404181111.GA30828@ednor.casa.cgf.cx> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com >> I guess what I find surprising is that gcc can be used to produce Windows >> XP runnable code. Here's a typical compilation command generated by the >> build process: >> ... > Why is this surprising? Cygwin *is* Windows XP runnable code. Is it? Pardon my n00bness but I recall once trying to run a Cygwin utility from Window's cmd, just for the fun of it. It didn't work. But back to the main question: will a library compiled under Cygwin in the manner I described be linkable in Visual Studio .NET? Your answer taken to the extreme, would suggest that I can link any of the core Cygwin (*.a) libraries and link it with the MS VS.NET toolchain. Thanks for not flaming. -- 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/