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 Reply-To: Cygwin List Message-Id: <6.0.1.1.0.20040327142256.036af398@127.0.0.1> X-Sender: Date: Sat, 27 Mar 2004 14:32:46 -0500 To: Joshua Daniel Franklin , Cygwin List From: Larry Hall Subject: Re: libdinput.a In-Reply-To: <20040327011841.A15134@ns1.iocc.com> References: <2D9DC0EB3919FE429946B0A6F08556BB0103F3F3 AT xt02 DOT brd DOT ro> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040308110329 DOT 039ced70 AT 127 DOT 0 DOT 0 DOT 1> <20040327011841 DOT A15134 AT ns1 DOT iocc DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 02:18 AM 3/27/2004, you wrote: >On Mon, Mar 08, 2004 at 11:07:08AM -0500, Larry Hall wrote: >> At 08:50 AM 3/8/2004, you wrote: >> >> >What version of DirectX is supported ? Or more exactly what version of DirectInput? >> >I need DirectInput 8, but LPDIRECTINPUT8, DirectInput8Create() are not recognized by libdinput.a (it seems like libdinput.a goes for DirectX 7). >> >Is the answer in the FAQ: >> >Why isn't package XXXX available in Cygwin? (Or, why is your package so out of date?) >> >If so, can I link a gcc compiled program from cygwin against the static Win32 libs xxxx.lib ? (the -mno-cygwin flag is for dynamic linking). >> >Is there by any chance a libdinput8.a like in Dev-C++ ? >> >If nothing else works, can I link the MSVC libs as stated in the FAQ in: >> >How do I link against .lib files? >> >I'm sorry if this question was asked before, it was not in the FAQ. >> > A. Sava >> >> >> Yeah, I'd say this entry is a bit out-of-date, though the information isn't >> wrong. You should be able to use the '.lib' files directly. Just list them >> like you would object files. Feel free to make whatever additions are >> necessary to the DirectX stuff to support your work. Please consider >> submitting patches for whatever you do. > >I'd love to correct the entry, which appears to be > > > >but I don't really know what's out-of-date. What's there is fine but a bit complicated for the (hopefully) typical case. Presuming that 'foo.lib' is a static or import library with C-callable entry points, you can list 'foo.lib' as an object file for gcc/g++, just like any other '*.o'. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/