Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3C6171A9.2080702@syntrex.com> Date: Wed, 06 Feb 2002 19:10:49 +0100 From: Pavel Tsekov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: DirectX8/DirectInput + cygwin References: <002301c1aef8$228e5440$2801a8c0@dcuthbert2k> <3C610F7E.5020306@syntrex.com> <20020206172903.GE31367@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 ? -- 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/