If you used the command based ctest scripts, you have much
more control
of when the env vars are set.
This came up recently in a bug report:
http://public.kitware.com/Bug/view.php?id=4954
Basically, you want something like this:
CTEST_START (Nightly)
CTEST_UPDATE (SOURCE
Wheeler, Frederick W (GE, Research) wrote:
Thanks for this helpful tip, which is panning out well, though I'm still
testing/fixing a few things. I have a few follow-up questions, and I'm
grateful for any advice on any of them from anybody.
1. What is the right way to add a notes file when
CMake List:
I have a ctest/cmake issue where LD_LIBRARY_PATH must be set to run
test execs produced by ctest but that LD_LIBRARY_PATH setting causes
ctest/cmake to not run due to a library mismatch. Does anyone have a
solution or any advice? Details below.
After a recent upgrade to FreeBSD
On Mon, Sep 8, 2008 at 7:39 PM, Wheeler, Frederick W (GE, Research)
[EMAIL PROTECTED] wrote:
CMake List:
I have a ctest/cmake issue where LD_LIBRARY_PATH must be set to run
test execs produced by ctest but that LD_LIBRARY_PATH setting causes
ctest/cmake to not run due to a library mismatch.
Wheeler, Frederick W (GE, Research) wrote:
CMake List:
I have a ctest/cmake issue where LD_LIBRARY_PATH must be set to run
test execs produced by ctest but that LD_LIBRARY_PATH setting causes
ctest/cmake to not run due to a library mismatch. Does anyone have a
solution or any advice? Details
