Closed patrikhuber closed 6 years ago
Hmm, I guess I need to update my custom type-casters - is that expected? I think it may have to do with my type-casters.
I ended up "fixing" (avoiding) this by replacing all my glm
types in the python bindings with Eigen
vectors and matrices. I didn't dig much deeper into why this pybind11 update broke my glm type casters. It was really hard to find out where exactly these errors originate from. Anyway I'm happy with using only Eigen
in the bindings, it means I don't have to maintain my own glm typecasters anymore.
There seems to be a bug in the Visual Studio compiler. We are waiting for this to be fixed. See: visualstudio.com
Hi!
The latest 3 commits to the master branch (
"Make it possible to generate constexpr signatures in C++11 mode"
,"Use semi-constexpr signatures on MSVC"
,"Simplify function signature annotation and parsing"
) by @dean0x7d broke compiling on the latest stable VS2017 (15.3.3) for me.The commit before that, f94d7598813d5f50f88ffad11f4622c02a3eb391, compiles fine, while the latest master commit fails to compile my bindings with the following errors:
I'm compiling with
/std:c++17
but it also fails without it.I should have time to create a MWE tomorrow or Wednesday, but I thought I'd already report it, maybe it helps even without a MWE. I'm happy to test any fixes. I'm wondering why pybind11's AppVeyor build doesn't catch that actually. I hope it's not a problem in my code but f94d7598813d5f50f88ffad11f4622c02a3eb391 compiles fine, while the newest master doesn't.