有人可以解释 pybind11 安装吗？

Question

The pybind11 documentation is generally good, but one area in which it is not is explaining the install process and the process of getting and running examples using cmake.

I've managed to figure out how to get and build examples. But it leads to more questions. Almost all the examples count on downloading the pybind11 repo into the examples folder and including the root folder of the repo in a cmake run (the root folder contains a cmakelists.txt file). The contents of that repo have a lot in common with the content which is added to a python environment when you install pybind11 using pip or conda. But the folder organization is completely different.

So I'm curious:

• Why the difference?
• Is there a way to use the content in the environment install in such a way that you don't also have to download the repo in order to build examples using cmake?
• Failing that, what is the best way to put the pybind11 repo in a common place so it doesn't have to be copied all over the place in order to build examples, or in order to provide the important added cmake functionality for one's own code?

I'm really uncomfortable in general not understanding the "how this works" aspect of such things, so this will really help me.

Answer 1

Not sure which examples you mention, but to install pybind11 in your system and use it in different projects, just follow the standard procedure for installing CMake based packages

mkdir build
cd build
cmake ../  # optionally you can specify -DPYBIND11_PYTHON_VERSION=<your python version>
make
sudo make install

Then in one of your other project's CMakeLists.txt you can use it eg like this:

find_package(pybind11 CONFIG REQUIRED)
message(STATUS "Found pybind11 v${pybind11_VERSION}: ${pybind11_INCLUDE_DIRS}")
add_library(<name of your lib> MODULE <your sources>)
target_link_libraries(mylib pybind11::module)

For more CMake commands consult pybind11Config.cmake .

Then if you don't want to install it in your system, you can just embed pybind11 repo in your project tree with add_subdirectory instead of find_package . All the offered features will be the same. The package is well designed and it detects whether it is used as master project or not and either defined INSTALL targets or not.

So I guess that your last 2 questions are answered?