Add the stub function D3DXComputeTangent based on the staging patch. https://bugs.winehq.org/show_bug.cgi?id=41697 Since this will at least make the application go further. Even though the implementation is based on documentation https://learn.microsoft.com/en-us/windows/win32/direct3d9/d3dxcomputetangent
-- v5: d3dx9: Stub D3DXComputeTangent wineps: Store font substitution table in DEVMODE. wineps: Store data from PPD file used in unixlib in DEVMODE. wineps: Use standard DEVMODEW structure instead of PSDRV_DEVMODE when possible. wineps: Remove unused fields from PSDRV_DEVMODE. wineps: Remove gdi_physdev from print_ctx structure. winemac: Use the default IME implementation for ImeSetCompositionString. winex11: Use the default IME implementation for ImeSetCompositionString. kernelbase/tests: Use win_skip() for missing APIs. kernel32/tests: Use win_skip() for missing APIs. qcap/tests: Test the audio capture CLSID. qcap/tests: Test audio capture pin information. qcap/tests: Test audio capture pin interfaces. qcap/audiorecord: Add a stub source pin. qcap/audiorecord: Get rid of the AudioRecord typedef. kernelbase: Move Wow64EnableWow64FsRedirection() from kernel32 to kernelbase. win32u: Don't export wow64 Unix call functions. ntdll: Move the Unix function tables to avoid forward declarations, and make them static. ntdll: Add a helper function to free a range of pages. ntdll: Add logging for free ranges. ntdll: Support partial view release in NtFreeVirtualMemory(). ntdll: Factor out some view manipulation functions. ntdll: Fully support unaligned views in free ranges management. ntdll: Fix size validation in NtFreeVirtualMemory(). kernelbase: Validate nonzero size for MEM_RELEASE in VirtualFreeEx(). ntdll/tests: Add tests for freeing a part of view.
This merge request has too many patches to be relayed via email. Please visit the URL below to see the contents of the merge request. https://gitlab.winehq.org/wine/wine/-/merge_requests/2795
On Sat May 13 06:47:32 2023 +0000, Vijay Kiran Kamuju wrote:
I know that this makes staging rebase as mess, this is necessary to reduce the stalled patches to be mainlined as its been ages.
Right, but that's only the case if this stub actually helps the application from the referenced bug, otherwise it's exactly the opposite. So I reiterate Zeb's question, does this MR improve the application's functionality in any way?