[CMake] perennial question, how to setup environment for simple tests

Ian Monroe ian at monroe.nu
Fri Apr 3 10:55:14 EDT 2009


On Thu, Apr 2, 2009 at 10:28 PM, Philip Lowman <philip at yhbt.com> wrote:
> On Thu, Apr 2, 2009 at 3:19 PM, Ian Monroe <ian at monroe.nu> wrote:
>>
>> I've seen this question in the archives, but I was wondering if
>> there's been any progress since I last saw it asked (>1 year ago).
>>
>> I have some unit tests. I need to run a command or two and set some
>> environmental variables before all the tests start. Does CMake have a
>> solution for this yet? Are there any common practices to handle what
>> I'm guessing is a pretty common thing?
>>
>> I notice that CTest would allow me to setup a test environment, but
>> since it requires hardcoding the source and build directory it seems
>> pretty inappropriate as a common-repo script used by multiple
>> developers. Possibly the solution is to figure out how CTest can be
>> used anyways.
>
> This feature has been implemented in CMake CVS for some time thanks to David
> Cole.  If someone would commit the patch I sent in so it shows up in the
> documentation (attached to this bug) they could then close this bug.
>
> http://public.kitware.com/Bug/view.php?id=7885
>
> also this duplicate bug as well.
> http://public.kitware.com/Bug/view.php?id=6391

Hey that's good to hear. I'll look forward to cmake 2.8 then.

In the meantime I've just created a sh script and then execute that as
the test. Not very portable, but then again I don't think these tests
are either so its OK for me at the moment. :)

Ian


More information about the CMake mailing list