newly built gstreamer-1.0-0.dll entry point not found error when run on other Win 10
Built current master on Win 10 x64 with -v visualstudio today and I'm getting an error popup when trying to start any of the .exe files:
gst-launch-1.0.exe - Entry Point Not Found The procedure entry point g_libintl_bindtextdomain could not be located in the dynamic link library C:\gstreamer\1.0\x86_64\bin\gstreamer-1.0-0.dll
Errors in the dependencies tool report for gst-launch.exe:
gstreamer\1.0\x86_64\bin\intl-8.dll module has missing imports ext-ms-win-shell32-shellcom-l1-1-0.dll could not be found on disk C:\Windows\system32\WS2_32.dll has module missing imports
I've already had this (or very similar) issue last week when I was trying to bind the DLL from Python but then the problem went away somehow (perhaps an update to some python libraries?) so I didn't look into it. Now I'm getting it on my home PC and work laptop, with gstreamer built on both separately today.
More accurately, I built gst in a Win 10 x64 VM on my home PC, which works in the VM but doesn't work on the host; and another gst in a Win 10 Docker container on my work laptop, which doesn't work on the host. I'm aware that incompatibility between DLLs / VC runtime etc. between the machines could be the source of the error, but all have very similar software configurations (including nearly everything needed to build Gstreamer except for cmake, wix and miniconda instead of a central python install) and have all updates.
Moreover, a gstreamer build compiled in the VM about a month ago has worked on ALL machines I've tried it on so I'm wondering why the loss of mobility now. I can see that some system DLLs might be involved but ws2_32.dll seems to be the same on all of these systems, while shell32.dll is different, some have a recent version from April 2 - could that be the source of troubles?