James Hawkins wrote:
On Tue, Mar 25, 2008 at 4:27 AM, Paul Vriens paul.vriens.wine@gmail.com wrote:
James Hawkins wrote:
On Tue, Mar 25, 2008 at 4:08 AM, Paul Vriens paul.vriens.wine@gmail.com wrote:
Hi,
We didn't have a new winetest executable for the last few days. MinGW doesn't know anything about a d3dx9 dll (yet) that's imported in the d3dx9_36 tests.
Especially while in the process of getting ready for 1.0 we should have winetest run as much as possible.
My main focus will be adding tests btw until 1.0 is out. These will be both tests to proof the correctness of the current implementation as well as tests to show missing stuff. There are loads of functions for which we have no tests yet and with the 1.0 in sight I think it becomes very important to have tests for virtually every function we (have) implement(ed).
While that's a worthy goal, I think a better short-term goal for the run up to 1.0 is to fix the current failing tests in Windows.
But either way we need an up-to-date winetest executable ;-)
Are you currently working on this? Is it a problem that needs to be fixed on the mingw side?
It's indeed a mingw issue and has to be fixed on that side.
I've never touched mingw so I'm relying on either Hans Leidekker, Stefan Leichter or Paul Millar to take this up.
Cheers,
Paul (Vriens).