Re: d3dx9_36: Fix the tests for native Windows.

[Tony]

Hi,
At least for all Windows versions below Vista, the d3dx9 importlib does 
exist (and d3dx9_36 does not),
so either something is screwed up with your system or Vista is handling 
it otherwise (in that case we need
another solution though).

Best regards,
    Tony

d3dx9_36: Fix the tests for native Windows.

[David Adam]

Hi,

Yes, I learnt that in IRC. But there is a real problem. With a native box,
there is no d3dx9.dll. So, wine-test mustn't call it.
Currently, wine-test calls it and all the tests are skipped in a real
windows box. You can check it in the wine-webpage  that collects all the
test results.

David


2008/9/10 Tony <tony.wasserka(a)freenet.de>
> Hi,
> At least for all Windows versions below Vista, the d3dx9 importlib does
> exist (and d3dx9_36 does not),
> so either something is screwed up with your system or Vista is handling it
> otherwise (in that case we need
> another solution though).
>
> Best regards,
>   Tony

d3dx9_36: Fix the tests for native Windows.

[Tony Wasserka]

yeah, but your patch is only semi-correct in that regard.
What you are referring to (d3dx9.dll) is an import (IMPORTS) of the test 
program, i.e. a dll which is needed to run the program. What your patch 
is doing with that var is correct (i.e. we must use d3dx9_36 instead of 
d3dx9).
However, the IMPORTLIB is the lib which is used to compile the program. 
And if Vista didn't change anything about it (and I'm quite sure it 
didn't), this MUST be d3dx9(.lib), for some reason, which is only known 
by the Microsoft programmers.
So this means, your patch indeed fixed RUNNING the test applications 
under Windows, but now they won't COMPILE anymore, because the linker 
won't be able to find d3dx9_36.lib (the IMPORTLIB) This is assuming you 
didn't install Wines implementation of course; one should be able to 
compile the Wine D3DX9 tests out of the box with the official DirectX SDK.

Best regards,
 Tony
> Hi,
>
> Yes, I learnt that in IRC. But there is a real problem. With a native 
> box, there is no d3dx9.dll. So, wine-test mustn't call it.
> Currently, wine-test calls it and all the tests are skipped in a real 
> windows box. You can check it in the wine-webpage  that collects all 
> the test results.
>
> David
>
> 2008/9/10 Tony <tony.wasserka(a)freenet.de 
> <mailto:tony.wasserka(a)freenet.de>>
>
> Hi,
>     At least for all Windows versions below Vista, the d3dx9 importlib
>     does exist (and d3dx9_36 does not),
>     so either something is screwed up with your system or Vista is
>     handling it otherwise (in that case we need
>     another solution though).
>
> Best regards,
>       Tony

d3dx9_36: Fix the tests for native Windows.

[Detlef Riekenberg]

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.


-- 
 
By by ... Detlef

d3dx9_36: Fix the tests for native Windows.

[Tony Wasserka]

> 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.

d3dx9_36: Fix the tests for native Windows.

[David Adam]

Hi,

any idea to fix this problem?

David

2008/9/11 Tony Wasserka <tony.wasserka(a)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.

d3dx9_36: Fix the tests for native Windows.

[Tony Wasserka]

Your latest patch is already doing it right, IMPORTS must be changed to 
d3dx9_36 and IMPORTLIB must stay d3dx9.
> any idea to fix this problem?
>
> David
>
> 2008/9/11 Tony Wasserka <tony.wasserka(a)freenet.de 
> <mailto:tony.wasserka(a)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.

d3dx9_36: Fix the tests for native Windows.

[David Adam]

Hello,

In IRC, Julliard said that this change is wrong too. :(

David

2008/9/11 Tony Wasserka <tony.wasserka(a)freenet.de>
> Your latest patch is already doing it right, IMPORTS must be changed to
> d3dx9_36 and IMPORTLIB must stay d3dx9.
> > any idea to fix this problem?
> >
> > David
> >
> > 2008/9/11 Tony Wasserka <tony.wasserka(a)freenet.de <mailto:
> > tony.wasserka(a)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.

d3dx9_36: Fix the tests for native Windows.

[Tony Wasserka]

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(a)freenet.de 
> <mailto:tony.wasserka(a)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.