On 27/08/07, Martijn Berger martijn.berger@gmail.com wrote:
+WINE_DEFAULT_DEBUG_CHANNEL(d3d10);
That's not a good idea. Also, since the dll isn't actually called d3dx9.dll, how do you intend to handle the different versions? (Arguably these dlls are outside Wine's scope, since they're not installed as part of the OS, and should be installed by the application that is using them.)
On Monday 27 August 2007 19:37, H. Verbeet wrote:
On 27/08/07, Martijn Berger martijn.berger@gmail.com wrote:
+WINE_DEFAULT_DEBUG_CHANNEL(d3d10);
That's not a good idea. Also, since the dll isn't actually called d3dx9.dll, how do you intend to handle the different versions?
There is an original d3dx9.dll which at some stage microsoft started to rename to d3dx9_16.dll .. d3dx9_32.dll or even further. There should be one base dll ('wined3dx_core or whatever, the name doesn't really matter). The invididual versions are created out of it using spec-file magic. In case of COM-interfaces it can be more complicated.
Regards, Roderick
-
H. Verbeet -
Roderick Colenbrander