Frictional Games Forum (read-only)

Full Version: [Help] Compiling Penumbra - VS 2017 Error
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi, after usccessfully reinstalling my Windows 10 from scratch I managed to fic quite alot of bugs in VS. I tried opening and compiling the sources in VS 2017 and both HPL1Engine and OALWrapper compiled fine under VS 2017 but for some reason Penumbra source fails with this error.

https://pasteboard.co/HUkmafj.png

Please help me fix this thanks!
Can't see the huge ass image link

We are in the same boat, i'm also trying to compile the source but in VS2015, after some internet search was able to make everything compile minus the penumbra.exe, get two linking errors:

Error LNK2001 unresolved external symbol __imp___vsnprintf Penumbra
H:\UnamedGame\PenumbraOverture\angelscript.lib(as_string.obj) 1

Error LNK2001 unresolved external symbol __imp___vsnprintf Penumbra H:\UnamedGame\PenumbraOverture\angelscript.lib(as_string_util.obj) 1

This seems to be caused by the very old angelscript.lib and unfortunatly using a modern lib causes many compilation errors, so right now it seems i can't compile the engine. Sad
(12-31-2018, 08:58 PM)Argoon Wrote: [ -> ]Can't see the huge ass image link

We are in the same boat, i'm also trying to compile the source but in VS2015, after some internet search was able to make everything compile minus the penumbra.exe, get two linking errors:

Error LNK2001 unresolved external symbol __imp___vsnprintf Penumbra
H:\UnamedGame\PenumbraOverture\angelscript.lib(as_string.obj) 1

Error LNK2001 unresolved external symbol __imp___vsnprintf Penumbra H:\UnamedGame\PenumbraOverture\angelscript.lib(as_string_util.obj) 1

This seems to be caused by the very old angelscript.lib and unfortunatly using a modern lib causes many compilation errors, so right now it seems i can't compile the engine. Sad

Damn man, now what? I can't do anything fun with Penumbra right now sadly then.
The DirectX libraries you are using are compiled with an older version of Visual Studio than you are using. Microsoft sometimes makes changes to their C runtime, creating incompatibilities between libraries compiled with different versions. __vsnprintf was an internal symbol in older versions of their C runtime, it does not exist in the 2015 RC version.