Home | History | Annotate | Download | only in ctest
      1 # Copyright (c) 2014-2015, Intel Corporation
      2 # All rights reserved.
      3 #
      4 # Redistribution and use in source and binary forms, with or without modification,
      5 # are permitted provided that the following conditions are met:
      6 #
      7 # 1. Redistributions of source code must retain the above copyright notice, this
      8 # list of conditions and the following disclaimer.
      9 #
     10 # 2. Redistributions in binary form must reproduce the above copyright notice,
     11 # this list of conditions and the following disclaimer in the documentation and/or
     12 # other materials provided with the distribution.
     13 #
     14 # 3. Neither the name of the copyright holder nor the names of its contributors
     15 # may be used to endorse or promote products derived from this software without
     16 # specific prior written permission.
     17 #
     18 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
     19 # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
     20 # WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
     21 # DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
     22 # ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
     23 # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
     24 # LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
     25 # ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
     26 # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
     27 # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
     28 
     29 # Ctest configuration variables must be set BEFORE include(Ctest)
     30 
     31 # Check process children and give detail for each leak
     32 set(MEMORYCHECK_COMMAND_OPTIONS
     33     "${MEMORYCHECK_COMMAND_OPTIONS} --trace-children=yes --leak-check=full")
     34 
     35 # As dash is not used to submit results, there is no way to see valgrind result.
     36 # Force it to log to stderr and fail in case of leak or error.
     37 set(MEMORYCHECK_COMMAND_OPTIONS
     38     "${MEMORYCHECK_COMMAND_OPTIONS} --error-exitcode=255 --log-fd=2")
     39 
     40 set(MEMORYCHECK_COMMAND_OPTIONS
     41     "${MEMORYCHECK_COMMAND_OPTIONS} --suppressions=${CMAKE_CURRENT_LIST_DIR}/valgrind.supp")
     42 
     43 # Enable tests, coverage, memcheck, ...
     44 # See http://www.cmake.org/Wiki/CMake/Testing_With_CTest#Dashboard_Preparation
     45 include(CTest)
     46 
     47 # Ctest requires its configuration to be placed at the build root
     48 configure_file(${CMAKE_CURRENT_LIST_DIR}/CTestCustom.cmake ${PROJECT_BINARY_DIR} COPYONLY)
     49 
     50 # Set environement variables so that executables and libraries can be find by tests.
     51 # (avoids a make install before make test)
     52 function(set_test_env TestName)
     53     # A cmake PROPERTY value is just a string.
     54     # The ENVIRONMENT PROPERTY is implemented as a semicolon separated
     55     # list of value pair. Each value pair being separated by `=`
     56     # Eg: the python env equivalent of `{"A":"1", "B":"/;/bin"}` is `A=1;B=/\;/bin`
     57     #
     58     # As a consequences cmake can not differentiate between a `;` that separates
     59     # two environment variable and a `;` contained in a variable.
     60     #
     61     # Thus all `;` in environment variables must be escaped
     62     # before inserting them in the ENVIRONMENT PROPERTY.
     63     string(REPLACE ";" "\\;" TEST_PATH "$ENV{PATH};$ENV{TEST_PATH}")
     64     string(REPLACE ";" "\\;" TEST_LD_LIBRARY_PATH "$ENV{LD_LIBRARY_PATH}")
     65     string(REPLACE ";" "\\;" TEST_PYTHONPATH "$ENV{PYTHONPATH}")
     66 
     67     if(WIN32)
     68         set(SEP "\\;")
     69     else()
     70         set(SEP ":")
     71     endif()
     72 
     73 
     74     # With nmake and nmake, executables are build in:
     75     #     ${CMAKE_RUNTIME_OUTPUT_DIRECTORY} => `bin/`
     76     #
     77     # Nevertheless Visual studio (and xcode) can build for debug and release
     78     # from the same build tree. As a result those multi-configuration
     79     # build systems build executables in:
     80     #     ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/$<CONFIGURATION> =>
     81     #         - `bin/Debug` for debug
     82     #         - `bin/Release` for release.
     83     #
     84     # In order to support both build system types add
     85     #     ${CMAKE_RUNTIME_OUTPUT_DIRECTORY} *and* ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/$<CONFIGURATION>
     86     # in the path.
     87     #
     88     # Note: Quotes are necessary. Otherwise `;` escapes are discarded
     89     # TODO: when cmake 3 will be used, split long lines with trailing backslash
     90     set_property(TEST ${TestName} PROPERTY ENVIRONMENT
     91                  "PATH=${CMAKE_RUNTIME_OUTPUT_DIRECTORY}${SEP}${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/$<CONFIGURATION>${SEP}${TEST_PATH}"
     92                  "LD_LIBRARY_PATH=${CMAKE_LIBRARY_OUTPUT_DIRECTORY}${SEP}${TEST_LD_LIBRARY_PATH}"
     93                  "PYTHONPATH=${PROJECT_BINARY_DIR}/bindings/python${SEP}${TEST_PYTHONPATH}")
     94 endfunction()
     95 
     96