d3dx: A few last questions...
"Luis C. Busquets Pérez"
luis.busquets at ilidium.com
Tue Jan 29 14:52:01 CST 2008
I have submitted a patch for this function and it is easily convertable
to the 13 different functions.
Anyway, propose another patch for it and let it be implemented.
tony.wasserka at freenet.de escribió:
>> The function D3DXCheckVersion must not be forwarded from each d3dx9_xx file to the 36 because D3DX_SDK_VERSION changes for each file.
> Thanks for your comment, though I don't know if this is needed:
> Comment from the d3dx9core.h of the DX SDK:
>> // D3DX_SDK_VERSION:
>> // -----------------
>> // This identifier is passed to D3DXCheckVersion in order to ensure that an
>> // application was built against the correct header files and lib files.
>> // This number is incremented whenever a header (or other) change would
>> // require applications to be rebuilt. If the version doesn't match,
>> // D3DXCheckVersion will return FALSE. (The number itself has no meaning.)
> So this function is only needed to ensure that no header file changed between the last
> build of an application. As this won't be the case in our wine implementation we can let
> all dlls use the same function.
> Also, the D3DX_SDK_VERSION is declared in d3dx9core.h, which means we can only have
> one definition of it at a time which even prevents us from caring about this function.
> By the way, I think this function is just a leftover from the times, when microsoft released
> updates of their D3DX library without renaming the dlls, were using a more actual dll
> could really lead to conflicts.
> Unbegrenzter Speicher, Top-Spamschutz, 120 SMS und eigene E-MailDomain inkl.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wine-devel