X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Subject:	RE: How to link with third party libraries using gcc
Date:	Fri, 29 Jun 2007 15:31:14 -0400
Message-ID:	<FF8482A96323694490C194BABEAC24A0011F24D8@Email.cbord.com>
In-Reply-To:	<46855156.3020206@cygwin.com>
References:	<11331072 DOT post AT talk DOT nabble DOT com> <4682C0EE DOT D7088ADD AT dessent DOT net> <11342161 DOT post AT talk DOT nabble DOT com> <4683D230 DOT 9030705 AT cygwin DOT com> <11348820 DOT post AT talk DOT nabble DOT com> <007801c7b9b6$8d58ec30$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <11362016 DOT post AT talk DOT nabble DOT com> <FF8482A96323694490C194BABEAC24A0011F2243 AT Email DOT cbord DOT com> <46855156 DOT 3020206 AT cygwin DOT com>
From:	"Bob McConnell" <rvm AT CBORD DOT com>
To:	<cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id l5TJW8nM013103

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com 
> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Larry Hall (Cygwin)
> Sent: Friday, June 29, 2007 2:37 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: How to link with third party libraries using gcc
> 
> Bob McConnell wrote:
> 
> <snip>
> > 
> > Whether the libraries are linked dynamic or static is 
> irrelevant here.
> > The Windows libraries are stored in a different object 
> format than the
> > Unix and Cygwin libraries, and probably have different calling
> 
> The format of Windows and Cygwin libraries are the same.
> 
> > conventions. You can't use MS-Windows libraries without the 
> appropriate
> > tools, usually that means Visual Studio. Cygwin made no 
> attempt to be
> 
> You can use MS-Windows libraries with Cygwin.  Look under the 
> hood of Cygwin
> and you'll see Windows API calls.  The typical problems are 
> matching the
> calling conventions and managing resources (heap, etc), as 
> Dave has already
> pointed out.  But it's possible, as Cygwin itself illustrates.

So you are suggesting that with the proper header files and a little
fiddling I could build and run a Visual Studio.Net project on top of the
cygwin DLL and use additional Cygwin libraries in it? That is what it
sounds like to me. As an application programmer, I don't look under the
hood. I leave that to the kernel programmers that understand the
intricacies involved. I already have enough trouble debugging some
hardware vendors' libraries.

I have attempted to go the other way, with no success. I tried to use
Cygwin B.20 to write some MS-Windows services a few years ago. One was a
simple TCP/IP socket proxy, and I never could get it to talk with the
Service Control Manager. It took about two hours to get it running as a
daemon on Slackware and half a day to port it into MSVC6.

Bob McConnell

--
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 -