Incredibly helpful, thanks very much Christof. For now I'll be lazy and
distribute on deken with the mess of libs ;)
On Thu, Jan 5, 2023 at 10:52 AM Christof Ressi
wrote:
> Thanks!
>
> I would say, distribute everything *except kernel32.dll* (this one is
> always present on Windows)
>
>
Thanks!
I would say, distribute everything /except kernel32.dll/ (this one is
always present on Windows)
ucrtbase(d).dll (Universal C Runtime) is always present on Windows 10,
but not necessarily on older Windows versions.
BTW, ucrtbased.dll is the debug version of ucrtbase.dll (without
If you want to learn the ugly details:
https://learn.microsoft.com/en-us/cpp/windows/deploying-native-desktop-applications-visual-cpp?source=recommendations=msvc-170
On 05.01.2023 16:20, Christof Ressi wrote:
so...just one last question (hopefully): what's the best practice for
packaging an
so...just one last question (hopefully): what's the best practice for
packaging an external like this? The dependencies are:
kernel32.dll is always present and must not be distributed.
msvcp140d.dll, ucrtbase.dll and vcruntime140*.dll are Microsoft C
runtime libraries.
Can you send me the
Finally, success! Thanks very much Christof. I'm guessing that the
additional dependencies were available on my compiling machine because I
have Visual Studio installed on that one, but not the other. So...just one
last question (hopefully): what's the best practice for packaging an
external like
Hey,
this can also happen when an auxiliary library cannot be found. You can
check missing dependencies with the Dependencies program (modern
successor to Dependency Walker): https://github.com/lucasg/Dependencies
Christof
On 05.01.2023 19:48, William Brent wrote:
Hi again, I've got a
Hi again, I've got a successful build using cmake, but now I've run into
another issue. The external loads and works just fine in Pd on the windows
machine I compiled with, but fails on another machine with:
"leapmotion.dll: The specified module could not be found. (126)"
I know this is the
