On 20 August 2015 at 01:47, Józef Kucia jkucia@codeweavers.com wrote:
DXGID3D10* functions will be dropped once IDXGIDevice is moved to d3d11.
D3D10CoreRegisterLayers returns E_NOTIMPL on modern Windows systems.
I think the general idea of this patchset works (I haven't looked at all the details yet), but I don't think you can use d3d11 source files in d3d10core like that. If there's really no better way you can probably temporarily use PARENTSRC (look at e.g. d3dcompiler_47 for an example of how to use that), but it may be better to reorder things a bit so that you can essentially merge this patch with the one moving the files.
On Thu, Aug 20, 2015 at 10:08 AM, Henri Verbeet hverbeet@gmail.com wrote:
I think the general idea of this patchset works (I haven't looked at all the details yet), but I don't think you can use d3d11 source files in d3d10core like that. If there's really no better way you can probably temporarily use PARENTSRC (look at e.g. d3dcompiler_47 for an example of how to use that), but it may be better to reorder things a bit so that you can essentially merge this patch with the one moving the files.
I can avoid using d3d11 source files in d3d10core, if: * ID3D11Device stub is added to d3d10core before moving the files, * "[PATCH 4/7] Partially implement D3D11CoreCreateDevice" and "[PATCH 6/7] Implement D3D10CoreCreateDevice using D3D11CoreCreateDevice" are merged together with the patch moving the source files.
On 20 August 2015 at 11:13, Józef Kucia joseph.kucia@gmail.com wrote:
I can avoid using d3d11 source files in d3d10core, if:
- ID3D11Device stub is added to d3d10core before moving the files,
- "[PATCH 4/7] Partially implement D3D11CoreCreateDevice" and "[PATCH
6/7] Implement D3D10CoreCreateDevice using D3D11CoreCreateDevice" are merged together with the patch moving the source files.
That should work for me.
-
Henri Verbeet -
Józef Kucia