The ENVIRONMENT property worked for me. Thank you!
And I will look at the python virtual environment.
On 05/03/12 07:12, Bradley Lowekamp wrote:
Hello,
For testing python another alternative is to create a python virtual
environment and install you python package into that. Here is an
exa
Hello,
For testing python another alternative is to create a python virtual
environment and install you python package into that. Here is an example of how
I have done that:
https://github.com/SimpleITK/SimpleITK/blob/master/Wrapping/CMakeLists.txt#L97
Brad
On May 2, 2012, at 9:26 PM, David C
Are you using "add_test" to add the tests in the CMakeLists file?
If so, you can set the test ENVIRONMENT property to set PYTHONPATH
when ctest executes the test. See property doc here:
http://cmake.org/cmake/help/v2.8.8/cmake.html#prop_test:ENVIRONMENT
On Wed, May 2, 2012 at 5:17 PM, Lori A.
I'm building Python modules using SWIG and CMake, and have run into a
problem running Python unit tests for these built modules. I can not
find a slick way to set the Python module search path when running the
test. The usual trick of setting sys.path in the scripts will not work
here because I
