Why wlink does not find symbols IID_ID3D11Texture2D and IID_IDXGISurface1 in dxguid.lib in DXSDK June 2010?

[RodionKarimov]

Hello, I compile project, that uses DX11 from DXSDK June 2010 - it compiles fine, but on linking stage it does not find symbols IID_ID3D11Texture2D and IID_IDXGISurface1 in dxguid.lib .

wlink system nt_win option q option map name nova95.exe file {...} libpath ... lib ddraw.lib lib dxguid.lib lib dxgi.lib lib d3d11.lib lib d3dx11d.lib lib d3dcompiler.lib lib winmm.lib

Error! E2028: IID_ID3D11Texture2D is an undefined reference
Error! E2028: IID_IDXGISurface1 is an undefined reference

file winobjsr\GraphicsEngine.obj(...): undefined symbol IID_ID3D11Texture2D
file winobjsr\GraphicsEngine.obj(...): undefined symbol IID_IDXGISurface1

I replaced __uuidof () in :
SwapChain -> GetBuffer ( 0, __uuidof (IDXGISurface1), ( void ** ) & pSurface1 );
SwapChain -> GetBuffer ( 0, __uuidof ( ID3D11Texture2D ), ( LPVOID * ) & BackBuffer );
with :
SwapChain -> GetBuffer ( 0, IID_IDXGISurface1, ( void ** ) & pSurface1 );
SwapChain -> GetBuffer ( 0, IID_ID3D11Texture2D, ( LPVOID * ) & BackBuffer );
.
Everything compiles and all other symbols are defined; only these two from __uuidof () replacement are not found.
I open dxguid.lib as text and symbols IID_IDXGISurface1 and IID_ID3D11Texture2D are present there. So, it seems, that wlink does not find them.

I use ow_portable_v2_stable.

[jmalak]

I don't know what ow_portable_v2_stable is.
We don't create such distribution.
you can use our one OW 2.0 releases

[RodionKarimov]

I found other solution for this issue :
#include <initguid.h>
before including DX headers. And now application links without errors.

[jmalak]

proper solution is only to port DX 10, 11 and 12 to OW 2.0 otherwise you will have a trouble on run-time probably.
It is not a problem to remap symbols to be resolved by linker, but you need follow calling convention of such symbols and some of them are C++ objects which requires Microsoft C++ run-time libraries and appropriate Microsoft startup code, but OW use different C++ run-time and startup code. It is simply incompatible.

[RodionKarimov]

Understand. In this case - placement of DirectX 10, 11 and 12 in Dll and loading it in OW 2 application would be the best solution for now.

[jmalak]

If there is some Microsoft specific code as C++ then it is necessary to create OW specific library which can call Microsoft DLL's. This way is implemented DX9 there is some OW specific library which contains such objects compiled by OW and linked with application.
Anyway I think that also Microsoft use some compiled objects in separated library which are linked with application and is Microsoft C++ specific. OW use it similar way but it cannot be used with different toolchain because they are toolchain specific. They must be ported to OW to be compatible on source level it cannot be on binary level.

[RodionKarimov]

Placement of DirectX 10, 11 and 12 code in Dll, compiled by VC++, and loading it in OW 2 compiled application - should work for now. Till when you'll add support of DX 10, 11 and 12 to OW itself.