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: <002001c1af75$e41af190$2801a8c0@dcuthbert2k>
From: "Dylan Cuthbert" <dylan AT q-games DOT com>
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: Thu, 7 Feb 2002 10:22:21 +0900
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

If this is the case, does this mean the problem I'm getting with
DirectInput8Create AT 20 not being found is due to differences in C++ name
mangling as another poster mentioned only C libraries being able to link.

Linking directly with the DirectX SDK .lib files cleared up all the
unresolved errors apart from just this single one, but I'm only calling a
few directx function calls as a test so presumably I'll come across the same
problem when I start using more function calls.

Thanks for the help, I feel I'm getting a few starting points to try out.

---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.com

----- Original Message -----
From: "Christopher Faylor" <cygwin AT cygwin DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Thursday, February 07, 2002 3: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/