-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[glm] Bump to 2023-06-08 & fix usage #32685
Conversation
Usage passed on |
Unfortunately for version precedence rules @christophe-lunarg Any chance of glm doing a real release soon? If upstream won't do a release I think we have no choice but to switch to |
@BillyONeal |
That would sort the right way. Do you think users would be 'surprised' at the changes they get since then? Has upstream indicated they are going for 'live at head'? If the changes since then aren't 'small bugfixes' then I think we should go |
Repology will say that vcpkg is lying about the version.
Then how about using |
I vote this. What's your opinion? |
@BillyONeal @dg0yt |
This update breaks our application (KiCad), because values in quaternions are stored differently compared to 0.9.9.8. Order in 0.9.9.8: Order in 2023-06-08: Looks like glm should be updated again, with |
@dsa-t |
Another thing is, |
Yes, this port currently use g-truc/glm@5c46b9c, which is more later than g-truc/glm@c660699 |
Changes from g-truc/glm@c660699 aren't in g-truc/glm@5c46b9c. See quat_cast, for example: |
./vcpkg x-add-version --all
and committing the result.