FindPython¶
Find Python interpreter, compiler and development environment (include directories and libraries).
Three components are supported:
Interpreter: search for Python interpreter.Compiler: search for Python compiler. Only offered by IronPython.Development: search for development artifacts (include directories and libraries).NumPy: search for NumPy include directories.
If no COMPONENTS is specified, Interpreter is assumed.
To ensure consistent versions between components Interpreter, Compiler,
Development and NumPy, specify all components at the same time:
find_package (Python COMPONENTS Interpreter Development)
This module looks preferably for version 3 of Python. If not found, version 2
is searched.
To manage concurrent versions 3 and 2 of Python, use FindPython3 and
FindPython2 modules rather than this one.
Note
If components Interpreter and Development are both specified, this
module search only for interpreter with same platform architecture as the one
defined by CMake configuration. This contraint does not apply if only
Interpreter component is specified.
Imported Targets¶
This module defines the following Imported Targets
(when CMAKE_ROLE is PROJECT):
Python::Interpreter- Python interpreter. Target defined if component
Interpreteris found. Python::Compiler- Python compiler. Target defined if component
Compileris found. Python::Python- Python library for Python embedding. Target defined if component
Developmentis found. Python::Module- Python library for Python module. Target defined if component
Developmentis found. Python::NumPy- NumPy Python library. Target defined if component
NumPyis found.
Result Variables¶
This module will set the following variables in your project (see Standard Variable Names):
Python_FOUND- System has the Python requested components.
Python_Interpreter_FOUND- System has the Python interpreter.
Python_EXECUTABLE- Path to the Python interpreter.
Python_INTERPRETER_ID- A short string unique to the interpreter. Possible values include:
- Python
- ActivePython
- Anaconda
- Canopy
- IronPython
Python_STDLIBStandard platform independent installation directory.
Information returned by
distutils.sysconfig.get_python_lib(plat_specific=False,standard_lib=True).Python_STDARCHStandard platform dependent installation directory.
Information returned by
distutils.sysconfig.get_python_lib(plat_specific=True,standard_lib=True).Python_SITELIBThird-party platform independent installation directory.
Information returned by
distutils.sysconfig.get_python_lib(plat_specific=False,standard_lib=False).Python_SITEARCHThird-party platform dependent installation directory.
Information returned by
distutils.sysconfig.get_python_lib(plat_specific=True,standard_lib=False).Python_Compiler_FOUND- System has the Python compiler.
Python_COMPILER- Path to the Python compiler. Only offered by IronPython.
Python_COMPILER_ID- A short string unique to the compiler. Possible values include:
- IronPython
Python_Development_FOUND- System has the Python development artifacts.
Python_INCLUDE_DIRS- The Python include directories.
Python_LIBRARIES- The Python libraries.
Python_LIBRARY_DIRS- The Python library directories.
Python_RUNTIME_LIBRARY_DIRS- The Python runtime library directories.
Python_VERSION- Python version.
Python_VERSION_MAJOR- Python major version.
Python_VERSION_MINOR- Python minor version.
Python_VERSION_PATCH- Python patch version.
Python_NumPy_FOUND- System has the NumPy.
Python_NumPy_INCLUDE_DIRS- The NumPy include directries.
Python_NumPy_VERSION- The NumPy version.
Hints¶
Python_ROOT_DIR- Define the root directory of a Python installation.
Python_USE_STATIC_LIBS- If not defined, search for shared libraries and static libraries in that order.
- If set to TRUE, search only for static libraries.
- If set to FALSE, search only for shared libraries.
Python_FIND_STRATEGYThis variable defines how lookup will be done. The
Python_FIND_STRATEGYvariable can be set to empty or one of the following:Python_FIND_REGISTRYOn Windows the
Python_FIND_REGISTRYvariable determine the order of preference between registry and environment variables. thePython_FIND_REGISTRYvariable can be set to empty or one of the following:FIRST: Try to use registry before environment variables. This is the default.LAST: Try to use registry after environment variables.NEVER: Never try to use registry.
Python_FIND_FRAMEWORKOn macOS the
Python_FIND_FRAMEWORKvariable determine the order of preference between Apple-style and unix-style package components. This variable can be set to empty or take same values asCMAKE_FIND_FRAMEWORKvariable.Note
Value
ONLYis not supported soFIRSTwill be used instead.If
Python_FIND_FRAMEWORKis not defined,CMAKE_FIND_FRAMEWORKvariable will be used, if any.Python_FIND_VIRTUALENVThis variable defines the handling of virtual environments. It is meaningfull only when a virtual environment is active (i.e. the
activatescript has been evaluated). In this case, it takes precedence overPython_FIND_REGISTRYandCMAKE_FIND_FRAMEWORKvariables. ThePython_FIND_VIRTUALENVvariable can be set to empty or one of the following:FIRST: The virtual environment is used before any other standard paths to look-up for the interpreter. This is the default.ONLY: Only the virtual environment is used to look-up for the interpreter.STANDARD: The virtual environment is not used to look-up for the interpreter. In this case, variablePython_FIND_REGISTRY(Windows) orCMAKE_FIND_FRAMEWORK(macOS) can be set with valueLASTorNEVERto select preferably the interpreter from the virtual environment.
Commands¶
This module defines the command Python_add_library (when
CMAKE_ROLE is PROJECT), which has the same semantics as
add_library() and adds a dependency to target Python::Python or,
when library type is MODULE, to target Python::Module and takes care of
Python module naming rules:
Python_add_library (my_module MODULE src1.cpp)
If library type is not specified, MODULE is assumed.