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/MINGW64 build is broken #502
Comments
We've known about the linker issue for probably a week now, CI complains every build. I don't have a Windows machine to troubleshoot so I'm at the mercy of our handful of Windows devs, none of whom have stepped up to fix it. Check history of CMakeLists.txt for the last few commits and you'll probably find the offending change? As far as the first problem, good catch. Once the build is broken, further breakage is easy to miss. |
AFAIK the ultimate problem is that yaml-cpp ends up being linked twice on Windows and you get multiply defined symbols. From the error message it seems that it's trying to pull in libyaml-cpp.a which is wrong (this should be dynamically linked, not statically). |
Agreed on the issue. |
In the first broken CI build, where Using the old yaml-cpp in place of ${YAML_LIBRARIES} does allow the build to progress further, but there's some string/wstring breakage in PreferenceManager.cpp I need to resolve next. |
Ok, I think all of the build failures are fixed finally. Thanks! |
I'm trying to build using the instructions from the manual, but I encountered some errors.
First error, which was able to resolve by adding .c_str():
Second error, which I've not yet resolved:
Seems like there is an issue with how yaml-cpp is being linked. Perhaps something different about how DLLs vs SOs work.
I know windows support is experimental, but do you know the last time it work working so I can try to bisect?
The text was updated successfully, but these errors were encountered: