<div>If you use ctest scripts (<a href="http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest">http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest</a> ) like this one from vtk:</div>
<div><a href="http://www.vtk.org/Testing/Sites/hythloth.kitware/Linux-gcc41/20080220-0300-Nightly/Notes.html">http://www.vtk.org/Testing/Sites/hythloth.kitware/Linux-gcc41/20080220-0300-Nightly/Notes.html</a></div>
<div> </div>
<div>You can set the CTEST_ENVIRONMENT as it does:</div>
<div># set any extra envionment variables here<br>SET (CTEST_ENVIRONMENT<br> "DISPLAY=:50"<br> "CC=gcc-4.1"<br> "CXX=g++-4.1"<br> "CFLAGS=-Wall -W"<br> "CXXFLAGS=-Wall -W -Woverloaded-virtual -Wunused -Wno-deprecated"<br>
"LD_LIBRARY_PATH=${LD_LIBRARY_PATH}"<br> )<br><br>Also, the ctest scripts specify all of the cmake cache options for your project.</div>
<div>itk (<a href="http://www.itk.org/Testing/Dashboard/MostRecentResults-Nightly/Dashboard.html">http://www.itk.org/Testing/Dashboard/MostRecentResults-Nightly/Dashboard.html</a> )</div>
<div>and</div>
<div>vtk (<a href="http://www.vtk.org/Testing/Dashboard/MostRecentResults-Nightly/Dashboard.html">http://www.vtk.org/Testing/Dashboard/MostRecentResults-Nightly/Dashboard.html</a> )</div>
<div> </div>
<div>both make extensive use of ctest scripting. On these dashboards, click on the text icon next to the build name to see (for most builds) the ctest script that is used to create that configure/build/test submission.</div>
<div> </div>
<div>Bill<br></div>
<div class="gmail_quote">On Wed, Feb 20, 2008 at 10:28 AM, Jörg Becker <<a href="mailto:news@elke-joerg.de">news@elke-joerg.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Tuesday, 19. February 2008 19:20:46 Philip Lowman wrote:<br>> What you're looking for to the best of my knowledge doesn't exist in<br>
> CMake. I would file a feature request on the bugtracker for it. There<br>> probably should be a way for declaring custom environment variables and<br>> associating them with tests scheduled with ADD_TEST (the PATH environment<br>
> variable for Windows comes to mind as one possible use case).<br>><br>done<br><br>> If you're using the makefile generator you can obviously just declare<br>> environment variables prior to running your tests. If you're using Visual<br>
> Studio to execute your tests you're probably out of luck here. Best bet<br>> would be to revert to testing them in command line mode:<br>><br>I tried 'set( ENV{ICU_DATA} "foo" )' with the same result (variable not set<br>
within test session).<br><br>> (or for Unix/Makefile generator using bash)<br>> user@host:~/build$ export foo=bar (Unix, bash)<br>> user@host:~/build$ ctest<br>><br>Yes, this is the way it works. But it's not very comfortable.<br>
<br>'make test' would be much easier than 'make depend;export foo=bar;ctest'.<br>Especially if there where more than one environment variable to be set.<br>
<div>
<div></div>
<div class="Wj3C7c"><br><br>Thanks,<br>Jörg<br>_______________________________________________<br>CMake mailing list<br><a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br><a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br>