Following Alexandre (and I agree with him :D ), one only needs to
export the functions of d3dx9_36 (the latest one) to the older
d3dx9_xx dlls.
So, we just just need to implement the functions in the d3dx9_36 dll
repertory.
No wine_d3dx9 is useful.
David
Am Mittwoch, 28. November 2007 18:14:21 schrieb [EMAIL PROTECTED]:
Following Alexandre (and I agree with him :D ), one only needs to
export the functions of d3dx9_36 (the latest one) to the older
d3dx9_xx dlls.
So, we just just need to implement the functions in the d3dx9_36 dll
repertory.
Hello Stefan,
Stefan Dösinger schreef:
What do we do if there's a d3dx9_37.dll next month?
One thing that comes to mind is: git-mv d3dx9_36 d3dx9_37 and create a
forward dll for the old one.
Cheers,
Maarten
Maarten Lankhorst wrote:
Stefan Dösinger schreef:
What do we do if there's a d3dx9_37.dll next month?
One thing that comes to mind is: git-mv d3dx9_36 d3dx9_37 and create a
forward dll for the old one.
Renames are cheap in git and we do not loose the history.
bye
michael
--
On Nov 28, 2007 12:34 PM, Michael Stefaniuc [EMAIL PROTECTED] wrote:
Maarten Lankhorst wrote:
Stefan Dösinger schreef:
What do we do if there's a d3dx9_37.dll next month?
One thing that comes to mind is: git-mv d3dx9_36 d3dx9_37 and create a
forward dll for the old one.
Renames are
Vijay Kiran Kamuju wrote:
On Nov 28, 2007 12:34 PM, Michael Stefaniuc [EMAIL PROTECTED] wrote:
Maarten Lankhorst wrote:
Stefan Dösinger schreef:
What do we do if there's a d3dx9_37.dll next month?
One thing that comes to mind is: git-mv d3dx9_36 d3dx9_37 and create a
forward dll for the old
