Thank you.
At the end, I realized that I could just call the standard Python installer
from CMake. This led to a more reliable install process and also a vastly
cleaner CMakeLists.txt file. My line for installing the Python code is
simply:
install(CODE "execute_process(COMMAND python setup.py i
Am 2013-03-27 05:46, schrieb Steve Andrews:
Thats very helpful. Thank you.
My other question was about how to get CMake to create directories at
installation time. Do you, or someone else, have suggestions about
that? Despite your advice, I think that I want the "make install"
step to put Pyt
That's very helpful. Thank you.
My other question was about how to get CMake to create directories at
installation time. Do you, or someone else, have suggestions about that?
Despite your advice, I think that I want the "make install" step to put
Python files into /usr/local/lib/python2.5/site-
Hi,
Am Dienstag, 26. März 2013 schrieb sandrews :
> Hi,
>
> My project is primarily C and C++, but also includes some Python code. I
> can get everything to build fine, and my CMakeLists.txt files uses the
> INSTALL(TARGETS ...) to so that the user can install the compiled code to
> the proper p
Hi,
My project is primarily C and C++, but also includes some Python code. I
can get everything to build fine, and my CMakeLists.txt files uses the
INSTALL(TARGETS ...) to so that the user can install the compiled code to
the proper place. However, part of the installation is to copy the Python
