d3dx9__xx dlls
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
Re: d3dx9__xx dlls
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. No wine_d3dx9 is useful. What do we do if there's a d3dx9_37.dll next month? signature.asc Description: This is a digitally signed message part.
Re: d3dx9__xx dlls
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
Re: d3dx9__xx dlls
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 -- Michael Stefaniuc Tel.: +49-711-96437-199 Consulting Communications Engineer Fax.: +49-711-96437-111 Reg. Adresse: Red Hat GmbH, Hauptstätter Strasse 58, 70178 Stuttgart Handelsregister: Amtsgericht Stuttgart HRB 153243 Geschäftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich
Re: d3dx9__xx dlls
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 cheap in git and we do not loose the history. I also think that rename is not a good idea. I would like propose a new idea, why dont we have different spec files inside wine_d3dx for all different versions of dlls. Its something like we have done it in the ole32. But, it requires some makefile/configure cruft. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 Consulting Communications Engineer Fax.: +49-711-96437-111 Reg. Adresse: Red Hat GmbH, Hauptstätter Strasse 58, 70178 Stuttgart Handelsregister: Amtsgericht Stuttgart HRB 153243 Geschäftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich
Re: d3dx9__xx dlls
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 one. Renames are cheap in git and we do not loose the history. I also think that rename is not a good idea. Heh. I didn't say that i don't like renames. I said renames are a workable solution: read there's no technical reason why to not use them. I would like propose a new idea, why dont we have different spec files inside wine_d3dx for all different versions of dlls. Its something like we have done it in the ole32. But, it requires some makefile/configure cruft. There's no need to name that wine_d3dx. Nothing stops us to name it d3d9x and have all the other versions generated inside that. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 Sr. Network EngineerFax.: +49-711-96437-111
