From:	moskewcz AT Princeton DOT EDU (Matthew Moskewicz)
Subject:	Re: DirectX support
23 Jan 1997 21:47:31 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<32E7B2EE.4910.cygnus.gnu-win32@Princeton.edu>
References:	<3 DOT 0 DOT 16 DOT 19970123083713 DOT 3d47555a AT btmpf3 DOT se DOT bel DOT alcatel DOT be>
Mime-Version:	1.0
X-Mailer:	Mozilla 3.01Gold (Win95; I)
Original-To:	Dirk Vangestel <gesteld AT se DOT bel DOT alcatel DOT be>
Original-CC:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Dirk Vangestel wrote:
> 
> Hi,
> 
> I'm looking to port a Unix application to Windows and I'd like to use
> DirectX to get direct access to the screen. Since the existing code relies
> heavily on the gcc compiler, I'd like to use the gnu-win32 tools.
> I don't think anyone has tried it yet (I'm new to gnu-win32 but I checked
> the archives) so I would appreciate some pointers on how to get it working.
> As far as I understand it, I will have to make some changes to the header
> files. But I'm not sure what is required... Do I only need to convert
> the DirectX headers? Or do I need to add some non-existing Win32 headers
> to gun-win32? Or can I use the standard Win32 headers instead of the gnu-win32
> headers? I do have VisualC++, so that shouldn't be a problem (as a temporary
> solution that is).
> I tried (briefly) to compile an example application but it complained about
> missing Win32 headers... I haven't tried adding the VisualC++ include path.
> Would that be enough to get it working?
> Also, can I just link the DirectX libraries with the gnu linker? I'd like
> to use only free tools since the project has to remain free. It's not really
> an option to have users buy VisualC++ just to recompile the application...
> (or I could have put the DirectX stuff in a separate source file and link
> the entire thing together with the MS linker. I don't like this option.)
> 
> Thanks,
> Dirk
> 
> -
> For help on using this list, send a message to
> "gnu-win32-request AT cygnus DOT com" with one line of text: "help".

I have tried it. Short answer: I never quite got it to work. 

If you're patient, I'm going to get back to work on it again soon, 
starting afresh with the DX3 SDK.

I'm planning to work without the win32 SDK headers, so that all 
that will be needed for DX is a pathched DX3 SDK. This might be
quite a pain, you might find things easier if you work with 
(rather than against) the win32 SDK headers.

In any case, you will need to build import libraries from the
directx dlls. I've seen several ways to do this posted. I have not
tried it, but RSXNT's makelib should get you pretty close. You'll 
still need to raid microsoft's .lib's or .h's to get the @(x*4) 
parts of the function names. It would be half-trivial to write a 
script that used makelib to grab the function name, then searched 
through the correct .lib to get the full function name.
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -