3rd party libraries for what?

[petrasvestartas]

Could you list a few methods that use these third party libraries?
I know they are big in themselves and hesitant to link libraries that must be linked by other libraries.

pyigl_include("" "core")
if(LIBIGL_COPYLEFT_CORE)
  pyigl_include("copyleft" "core")
endif()
if(LIBIGL_COPYLEFT_CGAL)
  pyigl_include("copyleft" "cgal")
endif()
if(LIBIGL_EMBREE)
  pyigl_include("" "embree")
endif()
if(LIBIGL_COPYLEFT_TETGEN)
  pyigl_include("copyleft" "tetgen")
endif()
if(LIBIGL_RESTRICTED_TRIANGLE)
  pyigl_include("restricted" "triangle")
endif()

[alecjacobson]

Sure. You can browse the functions here: https://github.com/libigl/libigl-python-bindings/tree/main/src

[petrasvestartas]

I would like to create nanobind using the official nanobind example example via scikit-built.
I already did this several times, including one for cgal that required eigen and boost.

From 5 years ago, I remember libigl required special CMake linking procedures, I have some questions:

• Since libigl contains source files, do you first build a static library and then link it to nanobind?
• How it is working currently, what should I know when I link these 3rd party libraries?
• Is embree, tetgen and triangle are header only libraries?
• Does the current libigl binding work on mac intel and m chips as well as manylinux and 64bit windows?
• What other information I should know?

Specially when I see things like this, I become confused:

    file(WRITE "${generated_dir}/BINDING_DECLARATIONS.in" "${BINDING_DECLARATIONS}")
    file(WRITE "${generated_dir}/BINDING_INVOCATIONS.in" "${BINDING_INVOCATIONS}")

The goal to change the wrapping method from pybind11 to nanobind for compas python infrastructure:
https://compas.dev/compas_libigl/latest/

[alecjacobson]

I'm not exactly sure what you mean. Do you want to rewrite your own libigl python bindings? Or do you want to use this but link to a different version of nanobind than the one pinned by libigl?

Happy to answer specific questions related to these maintained bindings.

[petrasvestartas]

Do you want to rewrite your own libigl python bindings?

Yes - I always start from this example: https://github.com/wjakob/nanobind_example. I want to build python binding only for this small subset of examples: https://compas.dev/compas_libigl/latest/examples/boundaries.html
For them do I need any third party libraries?

I am wondering how to do this in the simplest way and what linking would require, considering possible various operating systems.

[alecjacobson]

I don't think you'll need those dependencies for that specific set of functions.

fwiw, I think it might be better to contribute any missing bindings to this official project rather than rewriting them. I'm happy to merge PRs for functions that we don't have wrapped.

[petrasvestartas]

I agree, the thing is that I will need to combine this project with another c++ project at a later time.

For this reason I am asking details about wrapping, since I want to do as much on C++ side as possible.