Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <002301c31f91$b2cf87d0$0100a8c0@sazzer> From: "Graham Cox" To: References: <002f01c31f25$e1532740$0100a8c0 AT sazzer> <3ECAD160 DOT 8000807 AT rfk DOT com> Subject: Re: DirectX and Cygwin Date: Wed, 21 May 2003 13:08:31 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 On Wednesday, May 21, 2003 2:07 AM [GMT+0100=CET], Larry Hall (RFK Partners, Inc.) wrote: > So if --enable-stdcall-fixup isn't getting you what you want/need, why > not do it the "old-fashioned" way and simply declare the prototypes > for the needed functions with the correct calling convention? It's a > little more work but you're sure to get what you need. All the function prototypes are in the header files that come with the SDK. Compiling my code with these isn't a problem at all. The problem comes in when the linker tries to link my object files against the supplies library files, because the names seem to be different to what was expected. The library files have names like Direct3DCreate9, and the linker is looking for Direct3DCreate9 AT 4. As far as I can make out, ld should be able to tell that these two are the same thing and link one against the other, but it's not managing to. Therein lies the problem... -- Graham Cox 3rd year BSc/AI Student University of Sheffield -- 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/