Windows 10: xash.dll "cannot be found" in latest build from master

[noodlecollie]

I'm having issues running xash3d.exe when compiled on either of my Windows 10 machines, in either debug or release. When I run the executable I get the error:

Unable to load the xash.dll: The specified module could not be found.

I vaguely remember having issues with this before, so I tried to use Dependency Walker to see whether I could deduce what was wrong. Unfortunately when I try and profile the executable, Dependency Walker hangs (apparently indefinitely) after the implicit modules plus IMM32.dll have been loaded.

The engine build works as expected on my Ubuntu machine.

[a1batross]

Dependency Walker hangs for me too. :(

But for me, it works. MSVC2017.

[noodlecollie]

Aha, I'm on 2019. I'll give 2017 a shot and see if it makes any difference.

[noodlecollie]

I've tried installing VS 2017 and using the different versions of MSVC that Waf reports are available (--msvc_version with 16.0, 15.9 and 15.0 when invoking configure), but that doesn't seem to have made any difference.

EDIT: Also tried generating a VS project and building from within VS2017 (after upgrading the projects), but still no change.

[a1batross]

I will look into this. But does autobuilds are not working too?

Sadly, Windows doesn't give better error reporting, compared to dlerror() in most it's implementations. :(

[noodlecollie]

If by autobuilds you mean executing waf build on the command line, those don't work either.

[a1batross]

I mean, xash3d-deploy repo. Look into newengine-master branch. Download xash-vc.7z, it's the engine built with MSVC.

[noodlecollie]

The engine build from that repo appears to work for me.

[a1batross]

Interesting...

Can you explain how you building and running the engine? Things are changing rapidly for the new engine.

Maybe you should try to use git bisect and find commit which fails build for you.

[noodlecollie]

The command line I use by default to build the engine is:

python waf configure --build-type=debug --prefix=build/install --sdl2=C:\Users\Vesper\Documents\SDL2-2.0.9 --vgui=C:\Users\Vesper\Documents\GitHub\vgui-dev build install

However, thinking about it, I have a suspicion that the missing dependency is either SDL2 or VGUI, given I have to provide them both to configure. I'll check to make sure that these are accessible from the installed output location.

EDIT: Turns out that was the issue after all. I've just swapped my main laptop from a Macbook to a Windows machine, so I'm used to SDL being accessible automatically via the Mac frameworks. Slightly misleading that Windows suggests it's an issue with xash.dll and makes no mention of its sub-dependencies.

[a1batross]

They must be put in same directory, where dlls that they linked against too. SDL2 must be near xash.dll and vgui.dll near vgui_support.dll and both of them is in the same directory where xash3d.exe is located. Just put all DLLs, except game dlls, in same directory and you will be fine. вс, 2 июн. 2019 г., 23:41 Jonathan Poncelet <notifications@github.com>:

…

The command line I use by default to build the engine is: python waf configure --build-type=debug --prefix=build/install --sdl2=C:\Users\Vesper\Documents\SDL2-2.0.9 --vgui=C:\Users\Vesper\Documents\GitHub\vgui-dev build install However, thinking about it, I have a suspicion that the missing dependency is either SDL2 or VGUI, given I have to provide them both to configure. I'll check to make sure that these are accessible from the installed output location. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#44?email_source=notifications&email_token=AAYQTAJTVFAXEKZZOBJTE23PYQWARA5CNFSM4HSBCJJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWX5S5Y#issuecomment-498063735>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAYQTAOOPKJL3ALE3SQF4LDPYQWARANCNFSM4HSBCJJQ> .

[noodlecollie]

I've made a note of all this. Thanks for the help in debugging.