kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/PerConfig/perconfig.cmake

41 lines
CMake
Raw Normal View History

Test add_test() generator expressions This teaches the 'testing' test to try generator expressions in arguments to add_test(NAME). This test case mimics a common use-case of passing executables to test driver scripts. We excercise the syntax for per-configuration target file names.
2009-08-11 17:56:02 +04:00
# Print values for human reference.
foreach(v
configuration
perconfig_file_dir
perconfig_file_name
perconfig_file
pcStatic_file
pcStatic_linker_file
pcShared_file
pcShared_linker_file
pcShared_soname_file
)
Introduce "generator expression" syntax to custom commands (#11209) Evaluate in the COMMAND arguments of custom commands the generator expression syntax introduced in commit d2e1f2b4 (Introduce "generator expressions" to add_test, 2009-08-11). These expressions have a syntax like $<TARGET_FILE:mytarget> and are evaluated during build system generation. This syntax allows per-configuration target output files to be referenced in custom command lines.
2010-12-09 00:13:07 +03:00
message(STATUS "${v}=${${v}}")
Test add_test() generator expressions This teaches the 'testing' test to try generator expressions in arguments to add_test(NAME). This test case mimics a common use-case of passing executables to test driver scripts. We excercise the syntax for per-configuration target file names.
2009-08-11 17:56:02 +04:00
endforeach()
# Verify that file names match as expected.
set(pc_file_components ${perconfig_file_dir}/${perconfig_file_name})
if(NOT "${pc_file_components}" STREQUAL "${perconfig_file}")
message(SEND_ERROR
"File components ${pc_file_components} do not match ${perconfig_file}")
endif()
if(NOT "${pcStatic_file}" STREQUAL "${pcStatic_linker_file}")
message(SEND_ERROR
"pcStatic_file does not match pcStatic_linker_file:\n"
" ${pcStatic_file}\n"
" ${pcStatic_linker_file}\n"
)
endif()
# Verify that the implementation files are named correctly.
foreach(lib pcStatic pcShared)
Use a more reliable regex for extracting binary INFO strings A few different regular expressions were being used in various places to extract info strings from binaries. This uses a consistent regex amongst all of them now. This also fixes the broken ABI detection for Cray compilers.
2014-09-04 01:00:48 +04:00
file(STRINGS "${${lib}_file}" info LIMIT_COUNT 1 REGEX "INFO:[A-Za-z0-9_]+\\[[^]]*\\]")
Remove .* expressions from beginning and end of MATCHES regexs All these expressions work the same: "foo" ".*foo.*" "^.*foo.*$" This assumes that the "Intel*" expressions were meant to be "Intel.*".
2014-04-11 20:17:46 +04:00
if(NOT "${info}" MATCHES "INFO:symbol\\[${lib}\\]")
Test add_test() generator expressions This teaches the 'testing' test to try generator expressions in arguments to add_test(NAME). This test case mimics a common use-case of passing executables to test driver scripts. We excercise the syntax for per-configuration target file names.
2009-08-11 17:56:02 +04:00
message(SEND_ERROR "No INFO:symbol[${lib}] found in:\n ${${lib}_file}")
endif()
endforeach()
execute_process(COMMAND ${perconfig_file} RESULT_VARIABLE result)
if(result)
message(SEND_ERROR "Error running:\n ${perconfig_file}\n(${result})")
endif()