The number of functions reported in http://www.winehq.org/site/winapi_stats for the following dlls is
d3dx9_24 308 d3dx9_25 311 d3dx9_26 315 d3dx9_27 315 d3dx9_28 320 d3dx9_29 320 d3dx9_30 320 d3dx9_31 317 d3dx9_32 322 d3dx9_33 322 d3dx9_34 322 d3dx9_35 322 d3dx9_36 325
Nevertheless, the correct number is
d3dx9_24 320 d3dx9_25 323 d3dx9_26 327 d3dx9_27 327 d3dx9_28 332 d3dx9_29 332 d3dx9_30 332 d3dx9_31 329 d3dx9_32 334 d3dx9_33 334 d3dx9_34 334 d3dx9_35 334 d3dx9_36 336
On Fri, 22 Feb 2008, "Luis C. Busquets Pérez" wrote:
The number of functions reported in http://www.winehq.org/site/winapi_stats for the following dlls is
d3dx9_24 308
[...]
That's because d3dx9_36 has some forwards to functions that have not been declared in d3dx8, not even as a stub. It's allowed of course but winapi does not like it and thus ignores those.
Here's the list: d3dx9_36.spec: forward is broken: D3DXFresnelTerm => d3dx8.D3DXFresnelTerm d3dx9_36.spec: forward is broken: D3DXGetImageInfoFromFileA => d3dx8.D3DXGetImageInfoFromFileA d3dx9_36.spec: forward is broken: D3DXGetImageInfoFromFileInMemory => d3dx8.D3DXGetImageInfoFromFileInMemory d3dx9_36.spec: forward is broken: D3DXGetImageInfoFromFileW => d3dx8.D3DXGetImageInfoFromFileW d3dx9_36.spec: forward is broken: D3DXGetImageInfoFromResourceA => d3dx8.D3DXGetImageInfoFromResourceA d3dx9_36.spec: forward is broken: D3DXGetImageInfoFromResourceW => d3dx8.D3DXGetImageInfoFromResourceW d3dx9_36.spec: forward is broken: D3DXIntersectSubset => d3dx8.D3DXIntersectSubset d3dx9_36.spec: forward is broken: D3DXIntersectTri => d3dx8.D3DXIntersectTri d3dx9_36.spec: forward is broken: D3DXQuaternionSquadSetup => d3dx8.D3DXQuaternionSquadSetup d3dx9_36.spec: forward is broken: D3DXSplitMesh => d3dx8.D3DXSplitMesh d3dx9_36.spec: forward is broken: D3DXTessellateNPatches => d3dx8.D3DXTessellateNPatches
-
"Luis C. Busquets Pérez" -
Francois Gouget