kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/ModuleDefinition/CMakeLists.txt

32 lines
1.3 KiB
CMake
Raw Normal View History

Test use of module .def files for MS tools This adds a "ModuleDefinition" test enabled when using MSVC tools. It checks that .def files can be used to export .dll and .exe symbols and create corresponding .lib files that can be linked. See issue #9613.
2009-09-30 00:39:43 +04:00
cmake_minimum_required(VERSION 2.6)
project(ModuleDefinition C)
# Test .def file source recognition for DLLs.
add_library(example_dll SHARED example_dll.c example_dll.def)
Test generated module .def files Teach the ModuleDefinition test to cover the case that a .def file is generated by a custom command.
2012-04-02 18:40:13 +04:00
# Test generated .def file.
add_custom_command(OUTPUT example_dll_gen.def
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/example_dll_gen.def.in
COMMAND ${CMAKE_COMMAND} -E copy ${CMAKE_CURRENT_SOURCE_DIR}/example_dll_gen.def.in
${CMAKE_CURRENT_BINARY_DIR}/example_dll_gen.def
)
add_library(example_dll_gen SHARED example_dll_gen.c example_dll_gen.def)
Test use of module .def files for MS tools This adds a "ModuleDefinition" test enabled when using MSVC tools. It checks that .def files can be used to export .dll and .exe symbols and create corresponding .lib files that can be linked. See issue #9613.
2009-09-30 00:39:43 +04:00
# Test /DEF:<file> flag recognition for VS.
Fix ModuleDefinition test for Intel on Windows CMake defines MSVC only for a VS compiler, but the Intel compiler adds the preprocessor definition _MSC_VER. Instead of relying on separate tests to decide whether to use example_dll_2, we do one test in CMake and then add our own preprocessor definition.
2009-10-05 22:39:23 +04:00
if(MSVC OR "${CMAKE_C_COMPILER_ID}" MATCHES "^(Intel)$")
Test use of module .def files for MS tools This adds a "ModuleDefinition" test enabled when using MSVC tools. It checks that .def files can be used to export .dll and .exe symbols and create corresponding .lib files that can be linked. See issue #9613.
2009-09-30 00:39:43 +04:00
add_library(example_dll_2 SHARED example_dll_2.c)
set_property(TARGET example_dll_2 PROPERTY LINK_FLAGS
/DEF:"${ModuleDefinition_SOURCE_DIR}/example_dll_2.def")
Fix ModuleDefinition test for Intel on Windows CMake defines MSVC only for a VS compiler, but the Intel compiler adds the preprocessor definition _MSC_VER. Instead of relying on separate tests to decide whether to use example_dll_2, we do one test in CMake and then add our own preprocessor definition.
2009-10-05 22:39:23 +04:00
set_property(DIRECTORY APPEND PROPERTY COMPILE_DEFINITIONS EXAMPLE_DLL_2)
Test use of module .def files for MS tools This adds a "ModuleDefinition" test enabled when using MSVC tools. It checks that .def files can be used to export .dll and .exe symbols and create corresponding .lib files that can be linked. See issue #9613.
2009-09-30 00:39:43 +04:00
set(example_dll_2 example_dll_2)
endif()
# Test .def file source recognition for EXEs.
add_executable(example_exe example_exe.c example_exe.def)
set_property(TARGET example_exe PROPERTY ENABLE_EXPORTS 1)
Test generated module .def files Teach the ModuleDefinition test to cover the case that a .def file is generated by a custom command.
2012-04-02 18:40:13 +04:00
target_link_libraries(example_exe example_dll example_dll_gen ${example_dll_2})
Test use of module .def files for MS tools This adds a "ModuleDefinition" test enabled when using MSVC tools. It checks that .def files can be used to export .dll and .exe symbols and create corresponding .lib files that can be linked. See issue #9613.
2009-09-30 00:39:43 +04:00
# Test linking to the executable.
add_library(example_mod_1 MODULE example_mod_1.c)
target_link_libraries(example_mod_1 example_exe example_dll ${example_dll_2})