Ah wait, ignore my last answer to this email. I misunderstood the way the IMPORTS var influences the make process.
I now see that it's actually the IMPORTS which are the libs, the executable gets linked with. (and not the dll it is run with like I though in the other mails) However, I see no problem in the existing makefiles then, as linking with d3dx9 should work. Can't help you with that though as I don't have a working Windows installation ATM though :-/
Hi,
any idea to fix this problem?
David
2008/9/11 Tony Wasserka <tony.wasserka@freenet.de mailto:tony.wasserka@freenet.de>
On Mi, 2008-09-10 at 18:16 +0200, Tony wrote: Hi, At least for all Windows versions below Vista, the d3dx9 importlib does exist (and d3dx9_36 does not), I installed a recent dx9-runtime on my w2k test system, but a d3dx9.dll is not present (d3dx9_36.dll exist). I get always a blocking popup, when the testlist is created. You are speaking about the IMPORT d3dx9_36.dll. I was talking about the IMPORTLIB which is called d3dx9.lib, which is part of the DirectX SDK and used to compile d3dx9 applications, whereas the dll file is used to run them.