Hi,
I have a mixed C++/Python project. The test suite includes executing
python files through a wrapper script. For example,
add_test(test_parallel_utils_py ${SYNERGIA2_BINARY_DIR}/synergia-local
-c "import nose; nose.main()"
test_parallel_utils.py)
One detail is important: the python
Hi,
Are there any CMake solutions for running tests in a cross-compiling
environment? Right now I have a lovely test suite that runs over sixty
different executables using the standard CMake and CTest setup. It works
exactly as I want under Linux, but now I need to run it on a
cross-compiling
On 08/05/2010 10:42 AM, David Cole wrote:
Shouldn't that be this?
add_custom_command(OUTPUT test_diagnostics_get_mean.icc
COMMAND python test_diagnostics_crosscheck.py
DEPENDS test_diagnostics_crosscheck.py)
add_executable(test_diagnostics test_diagnostics.cc
test_diagnostics_get_mean.ic
I cannot get the following simple build process to work. I must be
missing something.
I build a (test) executable test_diagnostics, which depends on a source
file test_diagnostics.cc and a generated file
test_diagnostics_get_mean.icc. I generate the latter with
python test_diagnostics_cr
On 06/25/2010 01:40 PM, Brad King wrote:
James Amundson wrote:
This bug is a favorite of mine. It has been reported on the mailing list
before. It is also in the bug tracker:
http://public.kitware.com/Bug/view.php?id=10312&nbn=1#bugnotes
In each case a patch has been given to solve
On 06/23/2010 04:10 PM, Alexander Neundorf wrote:
Hi,
On Wednesday 23 June 2010, Todd Gamblin wrote:
2. The FindMPI module's library search breaks because the the cross-compiler
name on BlueGene/P contains -l. Specifically, the GNU compute node compilers
on BlueGene/P are named like
On 02/26/2010 09:15 AM, Bill Hoffman wrote:
I am thinking that we should put python in the front of the list of
names.
Great. I have a detailed argument for why that's the right choice, but
I'll spare everyone if the decision is already made.
--Jim Amundson
_
On 02/25/2010 12:29 PM, Bill Hoffman wrote:
OK, so that is the problem
It looks for names in this order:
NAMES python2.6 python2.5 python2.4 python2.3 python2.2 python2.1
python2.0 python1.6 python1.5 python
Coincidently, I had a bug report that arose from the above ordering just
this a