On 12/16/2015 05:04 AM, Andreas Schneider wrote:
> similar to what I implemented in FindPerlLibs.cmake some years ago, I've
> added
> PYTHON_SITELIB to FindPythonLibs. With PYTHON_SITELIB you have the location
> where to install the python modules you built with cmake.
>
> Example:
>
> find_package(PythonInterp)
> find_package(PythonLibs)
>
> python_add_module(my_py my_py.c)
> install(TARGETS my_py DESTINATION ${CMAKE_INSTALL_PREFIX}/${PYTHON_SITELIB})
One of the goals of FindPythonLibs is to work when cross-compiling such
that one cannot run the interpreter natively. That is one reason we
don't just ask the interpreter where to get the libraries. There has
been some discussion about doing such lookups conditionally when we
can run the interpreter but also having a fallback.
If there is another way to get this information then please use it.
Otherwise I'd rather not guarantee that we provide the information.
Projects can always run the same execute_process call themselves.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
