Jérémie Dumas

The function returns a boolean indicating success, so if the flag ERROR_ON_MISMATCH is set, deserialization should stop and return false when types do not match.

Awesome, thanks!

@hankstag I think I've pushed a fix regarding the demangling of std::string on Windows. The problem is that when you as `typeid(T).name()` to the compiler you don't always get `"T"`...

> Debian GNU/Linux 8.1 Do you mean you have Debian 8? That's pretty old. What version of gcc are you compiling with?

Our nightly builds of libigl are tested with gcc 8, 9 and 10. Could you try with those and see if it works for you?

You need to build your project with CMake. If you are under anything that is not directly under `include/igl/`, then there are additional third-party dependencies, which can be brought into...

There is nothing to fix, you just need to setup your CMake project correctly (enable `LIBIGL_WITH_TRIANGLE`, and link against the CMake target `igl::triangle`).

Do not install libigl. Use it as a sub-project as shown in the [libigl-example-project](https://github.com/libigl/libigl-example-project).

Because properly packaging C++ dependencies is hard work. The support for an "installed" version of libigl was a community contribution, and anything beyond the core library requires installing/exporting extra dependencies...

Thanks! Honestly I would drop the overload with the `std::rand()` initialization. People shouldn't be tempted to use non-deterministic functions.