Signed-off-by: Jacek Caban jacek@codeweavers.com --- Those are similar to old-style makefiles in a sense that recording is done in user space, rather than kernel space. However, they have an actual special king DC associated and some parts of the implementation (like bounding rect handling) uses driver interface.
dlls/gdi32/enhmfdrv/dc.c | 13 +------------ dlls/gdi32/enhmfdrv/graphics.c | 28 +++++++++++++++------------- dlls/gdi32/enhmfdrv/init.c | 1 + dlls/gdi32/gdi_private.h | 12 ++++++++++-- dlls/gdi32/gdidc.c | 16 ++++++++++++++++ dlls/gdi32/objects.c | 2 +- include/ntgdi.h | 1 + 7 files changed, 45 insertions(+), 28 deletions(-)
Hi,
While running your changed tests, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check?
Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=94232
Your paranoid android.
=== debiant2 (build log) ===
error: patch failed: dlls/gdi32/dc.c:1833 error: patch failed: dlls/gdi32/enhmfdrv/graphics.c:133 error: patch failed: dlls/gdi32/gdi_private.h:31 error: patch failed: include/ntgdi.h:89 Task: Patch failed to apply
=== debiant2 (build log) ===
error: patch failed: dlls/gdi32/dc.c:1833 error: patch failed: dlls/gdi32/enhmfdrv/graphics.c:133 error: patch failed: dlls/gdi32/gdi_private.h:31 error: patch failed: include/ntgdi.h:89 Task: Patch failed to apply
-
Jacek Caban -
Marvin