-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows dependency on Microsoft Visual C++ Redistributable #23
Comments
Hey, Since the GitHub runners are also not VFX reference platform compliant, that might explain the .libs problems. Setting that up to be fully compliant is a bit out of the scope of this project, sorry. You could also try self compiling it. The .bat files in this repo should make it very straight forward, all you need to do is download the MSVC compiler (installing Visual Studio with the C++ packages should do the trick, make sure to install the v142/143 compiler version based on your Houdini version) . If you have issues there, I'd be happy to walk you through it. Cheers, |
Hi, I already successfully compiled it following the .bat instructions. I will ask around me if there's any way to get rid of that dependency. Thanks |
I did some more research, according to stackoverflow (and chatgpt) statically linking from dynamically linked files (as that is what Houdini ships with), is not straight forward. Could you share the error again that you are getting? I wonder what specifically is calling into standard clibs that is making it crash. What happens when you run:
|
I have not yet managed to reproduce the crash, but here is the log of the crash from a few days ago, when I reported this issue :
|
I uninstalled every MS Visual C++ redistributable I had on my pc, rebooted and the CachedResolver is still working (Houdini doesn't crash). So I'm a bit puzzled. Cheers |
Hi @LucaScheller
In a previous issue I told you about the CachedResolver crashing Houdini with a segmentation fault. I resolved the issue by re-installing the MS Visual C++ redistributable. I had the same issue again today. I suspect installing an old version of Thinkbox Deadline corrupted the installation, but I'm not certain that this is the cause.
My (noob) question is, could the CachedResolver be compiled for Windows in such a way to avoid this kind of dependency ? We are slowly starting to use it in production and I'm afraid this issue will happen more often as it will be used on more workstations at our studio.
Regards
The text was updated successfully, but these errors were encountered: