RE: ddraw.h, dinput.h and dsound.h in Cygwin/MinGW

Danny Smith wrote:
> From: "Peter Ekberg"
>> View it as interfacing with the Wine versions
>> of the DirectX libraries. I mean, why wouldn't you want to support
>> DirectX apps compiled with MinGW running on Wine?
> 
> That is a worthy objective, but it is not the objective of the w32api
> package. 

But it is! Sort of anyway. w32api is missing some of the DirectX
headers. If they were available the above would work (if Wine is
up for the challenge), and as an added bonus it would work elsewhere
as well, which should be in line with the objectives of the w32api.
Or are MinGW and Wine not two sides of the same coin?

> This setup
>> doesn't (necessarily) involve any proprietary closed-source
>> libraries. 
>> 
>> Then, the LGPL header files may or may not work with some random
>> proprietary closed-source library. When it does happen to work, it
>> must surely be an extremely unlikely set of coincidences...
> 
> Then it should be a separate package.   The w32api package designed to
> work (in high probability not as unlikely coincidence) with a
> non-random set of libraries that are part of the OS.

Oh come on, my "unlikely coincidence" statement is dripping
with irony, how did you not notice? Give the Wine people some
credit, I haven't even tried to run my apps on Wine, but the apps
do work with their headers and the official DirectX dlls, and we
can sure as hell rule out coincidence from that equation.

The ultimate ddraw.h, dinput.h and dsound.h in Wine look very similar
to their counterparts in the w32api. Take advantage of that fact!

Cheers,
Peter