Bug Report

Before opening an issue on creating a pull request, please check the following:

Tip

  • Make sure you read the FAQ before asking a new question, search existing issues for a problem similar to yours.

  • Make sure you read the information contained in the libigl homepage as well as the tutorial.

General Issues

  • Make sure you are up-to-date with the master branch, and verify that your issue has not been fixed already before opening an issue on github.

  • To report a problem about the website (out-of-date content, erroneous instructions or errors in the tutorial), please open your issue in the designated repository for the website.

Compilation Issues

  • If you are on Windows, did you select the x64 version of the Visual Studio compiler?

  • If you have a CMake issue, make sure you follow the same approach as the libigl-example-project to build libigl with your project, and make sure that you can compile the example project.

  • If you have an issue with a submodule, then you are using an old version of libigl. Please read this page about the transition to v2.0.0.

  • If you have an issue with downloading an external dependency using the CMake build, nuke the external/ folder and try again.

  • If you have an issue with a missing template, check that your code compiles with the header-only option of libigl activated. Turn OFF the CMake option LIBIGL_USE_STATIC_LIBRARY: either modify your CMakeCache.txt via CMake GUI or ccmake, or delete your CMakeCache.txt and re-run cmake -DLIBIGL_USE_STATIC_LIBRARY=OFF .. in your build folder.

  • If none of these solve your problem, then please report your issue in the bug tracker!