diff --git a/_sources/install.md.txt b/_sources/install.md.txt index 563011968..f848d193d 100644 --- a/_sources/install.md.txt +++ b/_sources/install.md.txt @@ -84,7 +84,7 @@ cmake -DCMAKE_C_COMPILER=/path/to/gcc -DCMAKE_CXX_COMPILER=path/to/g++ .. * When compiling with the Python bindings enabled CMake will sometimes choose the wrong Python binary and/or include files, resulting in a failed compilation. If this happens the correct paths can be directly as follows: ```bash -cmake -DPython=ON -DPYTHON_INCLUDE_DIRS=/path/to/python/include/dir -DPYTHON_EXECUTABLE=/path/to/python/binary .. +cmake -DPython=ON -DPYTHON_INCLUDE_DIR=/path/to/python/include/dir -DPYTHON_EXECUTABLE=/path/to/python/binary .. ``` If you are using conda environments, the paths should look something like: diff --git a/install.html b/install.html index c5dd39e74..093befb59 100644 --- a/install.html +++ b/install.html @@ -191,7 +191,7 @@
oxpyWhen running make
if you run into a problem at the end of compilation where it cannot find python.h
, this means that you don’t have the Python developer kit installed. See this StackOverflow answer on how to install with a variety of package managers. If you do have it installed, see the next bullet point.
When compiling with the Python bindings enabled CMake will sometimes choose the wrong Python binary and/or include files, resulting in a failed compilation. If this happens the correct paths can be directly as follows:
-cmake -DPython=ON -DPYTHON_INCLUDE_DIRS=/path/to/python/include/dir -DPYTHON_EXECUTABLE=/path/to/python/binary ..
+cmake -DPython=ON -DPYTHON_INCLUDE_DIR=/path/to/python/include/dir -DPYTHON_EXECUTABLE=/path/to/python/binary ..
If you are using conda environments, the paths should look something like: