Re: [AD] Why are the DirectX GUIDs defined in Allegro?

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


On 25.08.2013 01:56, Trent Gamblin wrote:
There may have been a problem linking dxguid on older versions of MinGW (the
DirectX that comes with MinGW.) It might be ok now since it's recommended to
use the official DXSDK.

Ok, thanks. I've just copied the definitions I needed from Wine's source code so I don't have to deal with it for now.


-----Original Message-----
From: torhu
Sent: Saturday, August 24, 2013 2:12 PM
To: Coordination of admins/developers of the game programming library
Allegro
Subject: [AD] Why are the DirectX GUIDs defined in Allegro?

In wjoydxnu.cpp, there are lots of lines like this:
DEFINE_PRIVATE_GUID(__al_GUID_XAxis,
0xA36D02E0,0xC9F3,0x11CF,0xBF,0xC7,0x44,0x45,0x53,0x54,0x00,0x00);

Does anyone know why are they redefined instead of just using the
definitions from the DirectX SDK?

I'm asking because I need the GUID for for the wide (UNICODE) version of
DirectInput8, which is not defined in Allegro. So I'm thinking about
just deleting those definitions and switching to the ones from the
DirectX SDK.  That means we need to link with dxguid.lib.

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk





Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/