Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <035a01c1af4b$b598e9f0$a7eb0544@CX535256D>
From: "Barubary" <barubary AT cox DOT net>
To: <cygwin AT cygwin DOT com>
References: <002301c1aef8$228e5440$2801a8c0 AT dcuthbert2k> <3C610F7E DOT 5020306 AT syntrex DOT com> <20020206172903 DOT GE31367 AT redhat DOT com> <3C6171A9 DOT 2080702 AT syntrex DOT com> <20020206181851 DOT GF11730 AT redhat DOT com>
Subject: Re: DirectX8/DirectInput + cygwin
Date: Wed, 6 Feb 2002 12:20:23 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

What about the more important problem that Microsoft's patented virtual
table system, which COM uses, isn't supported by GCC?

-- Barubary

----- Original Message -----
From: "Christopher Faylor" <cygwin AT cygwin DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Wednesday, February 06, 2002 10:18 AM
Subject: Re: DirectX8/DirectInput + cygwin


> On Wed, Feb 06, 2002 at 07:10:49PM +0100, Pavel Tsekov wrote:
> >Christopher Faylor wrote:
> >>On Wed, Feb 06, 2002 at 12:11:58PM +0100, Pavel Tsekov wrote:
> >>>Dylan Cuthbert wrote:
> >>>>I am linking directly with the .lib files supplied by Microsoft, and
> >>>>all the Directx8 GUID references seem to link fine so does anybody
have
> >>>>any idea what the problem might be?
> >>>>
> >>>Why ?  Link against those in /usr/lib.  gcc doesn't understand the MS
> >>>export libraries.
> >>
> >>Actually, gcc/ld should understand non-c++ import libraries.
> >
> >Is this a new feature or I was missing something all the time ?  What's
> >the point of tools which build .a files from dlls ?
>
> If you have an existing .lib import library it should work fine with ld.
> This has been the case for years.
>
> This is not to say that there haven't been bugs over the years, but AFAIK,
> there aren't any in the current version of cygwin.
>
> If it helps you can rename foo.lib to libfoo.a so that you can add -lfoo
> to the command line.
>
> You can also link against the dll itself, in many cases:
>
> gcc -o foo.exe foo.c blah.dll
>
> cgf
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/