Skip to main content
Up and Coming
July 25, 2014

Which libraries need to be linked?

Hi,

I just started to update to the new 0.4 SDK and I couldn´t find any informations about which libraries need to be linked when using the SDK.
So far after looking at the MSDN documentation I have figured out that I need to link the following:

'comsupp'
'OleAut32',
'Ole32',
Advapi32',
'wbemuuid',
'Ws2_32',
'Dbghelp'

Sadly the library is still not linking because of

libovr64.lib(OVR_Win32_RenderShim.obj) : error LNK2019: unresolved external symbol __imp_ImageDirectoryEntryToData referenced in function "__int64 (__cdecl*__cd
ecl SetProcAddressA(struct HINSTANCE__ *,char const *,char const *,__int64 (__cdecl*)(void)))(void)" (?SetProcAddressA@@YAP6A_JXZPEAUHINSTANCE__@@PEBD1P6A_JXZ@Z

Anyone knows what else I need to link?

It would be really great if the next SDK version would be a DLL instead of a static lib so we can avoid all this trouble and in a worst case just use the dependency walker to figure out what needs to be added to our distribution.

Michael

    3 replies

    Up and Coming
    July 25, 2014
    Got it, the kernel32.lib was the last one I was missing.
    New Participant
    August 3, 2014
    More to the point .. why is the 32bit dk2 libovr.lib linking to all of the win32 socket stuff? I'd like to have the networking split out into a separate link please, so I can ignore yours if I have my own!
    Up and Coming
    August 3, 2014
    Yes, I'd like to know that - why is it using sockets?

    I've made a DLL for Live for Speed to use to connect with the DK2. I was a bit shocked to find that the DLL is over 8MB in size. I don't know what it can be doing to need 8MB of code! I've been working on Live for Speed for over 12 years and the exe is only 2MB. Seems a bit nuts for my 2MB exe to load an 8MB DLL just to get a little device info and some tracking data.
    Live for Speed - www.lfs.net