[PATCH 3/5] d3d9: Don't expose wined3d internal flags to the application.

Henri Verbeet hverbeet at codeweavers.com
Wed Jan 11 08:05:29 CST 2012


On 2012-01-11 14:31, Alexandre Julliard wrote:
> Henri Verbeet <hverbeet at codeweavers.com> writes:
> 
>> ---
>>  dlls/d3d9/buffer.c        |    4 ++--
>>  dlls/d3d9/cubetexture.c   |    2 +-
>>  dlls/d3d9/surface.c       |    2 +-
>>  dlls/d3d9/texture.c       |    2 +-
>>  dlls/d3d9/volume.c        |    2 +-
>>  dlls/d3d9/volumetexture.c |    2 +-
>>  6 files changed, 7 insertions(+), 7 deletions(-)
> 
> This is causing test failures:
> 
> ../../../tools/runtest -q -P wine -M d3dx9_36.dll -T ../../.. -p d3dx9_36_test.exe.so mesh.c && touch mesh.ok
> mesh.c:331: Test succeeded inside todo block: Test createmesh1, result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test createmesh2, result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test createmeshfvf, result 0, expected 0
> mesh.c:2497: Tests skipped: D3DXCreateBox failed
> mesh.c:331: Test succeeded inside todo block: Test sphere (0, 2, 2), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test sphere (1, 2, 2), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test sphere (1, 3, 2), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test sphere (1, 4, 4), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test sphere (1, 3, 4), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test sphere (5, 6, 7), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test sphere (10, 11, 12), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test cylinder (0, 0, 0, 2, 1), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test cylinder (1, 1, 1, 2, 1), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test cylinder (1, 1, 2, 3, 4), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test cylinder (3, 2, 4, 3, 4), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test cylinder (2, 3, 4, 3, 4), result 0, expected 0
> mesh.c:331: Test succeeded inside todo block: Test cylinder (3, 4, 5, 11, 20), result 0, expected 0
> mesh.c:3679: Test succeeded inside todo block: Test text ('wine', 340282346638528859811704183484516925440.000000, 0.400000), result 0, expected 0
> mesh.c:3679: Test succeeded inside todo block: Test text ('wine', 0.001000, 0.000000), result 0, expected 0
> mesh.c:3679: Test succeeded inside todo block: Test text ('wine', 0.001000, 0.000000), result 0, expected 0
> mesh.c:3679: Test succeeded inside todo block: Test text ('wine', 0.001000, 340282346638528859811704183484516925440.000000), result 0, expected 0
> mesh.c:3679: Test succeeded inside todo block: Test text ('wine', 0.000000, 1.000000), result 0, expected 0
> make: *** [mesh.ok] Error 21
> 
Yeah, I don't usually run the d3dx9 tests, I should probably add them.
Please use the attached patch instead.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-d3d9-Don-t-expose-wined3d-internal-flags-to-the-appl.patch
Type: application/text
Size: 6798 bytes
Desc: not available
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20120111/a9db2774/attachment-0001.bin>


More information about the wine-devel mailing list