-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Build Failed While Enabling Swizzle #594
Comments
Hi, I am not seeing this issue in VS 2015 pro. Thanks, |
This said, this is a known bug and this is why this test was created. However, this doesn't prevent you to use GLM. Thanks, |
Thanks for your answer! 1>------ Build started: Project: xxx, Configuration: Debug Win32 ------ -------------here is mycode.cpp -------------- And when I removed the macro GLM_FORCE_SWIZZLE, it compiled successfully. So it did prevent me from using Swizzle. |
I could reproduce the issue... I'll look at it! |
This issue doesn't prevent you to use swizzle expressions. The compiler bug only prevent to declare globals using GLM types. I filled a bug to Microsoft a while ago... Thanks, |
The following code building with Visual Studio 2015 SP3 in debug and x64 using language extension cause the Visual C++ compiler to crash.
I'll provide a workaround for GLM 0.9.8.4. Thanks for reporting, |
Hello!
I'm building glm-0.9.8.3 using VS Community 2015 Update 3, enabling all test during CMake configuration and generation. Then, when the building came to "test-bug_ms_vec_static", it occurred a compiler internal error. Then I opened this test case and found it enables the SWIZZLE feature. Maybe this feature cause the compiler to use too much memory, but I've no idea how to fixed it. Is there any solution?
The text was updated successfully, but these errors were encountered: