Alexander Neumann
Alexander Neumann
I assume this was fixed with https://github.com/llvm/llvm-project/commit/80a49487e1b64d32d00f0c80cff746cfd4988b36
> What build options did you use when building the VSG? Probably just the default. I don't see anything of relevance in the below cmd line: ``` [1/1] "E:/vcpkg_cache/downloads/tools/cmake-3.30.1-windows/cmake-3.30.1-windows-i386/bin/cmake.exe" -E...
> Other compilers have been working fine for years with the code as is, so could there be an issue with the version of clang and CMake? No, how often...
I am only speaking about Windows. Feel free to give #1407 a spin in CI. I expect it to reproduce the error if it does not the next line might...
Yep same error in your CI: ``` 2025-02-25T17:17:42.8384980Z D:\a\VulkanSceneGraph\VulkanSceneGraph\include\vsg/platform/win32/Win32_Window.h(108,17): warning : unsafe buffer access [-Wunsafe-buffer-usage] [D:\a\VulkanSceneGraph\VulkanSceneGraph\src\vsg\vsg.vcxproj] 2025-02-25T17:17:46.3420071Z lld-link : error : undefined symbol: public: void __cdecl vsg::Object::setValue(class std::basic_string const &,...