reactos/dll/win32/framedyn/CMakeLists.txt


spec2def(framedyn.dll framedyn.spec ADD_IMPORTLIB)

list(APPEND SOURCE
    main.c
    chstring.cpp
    provider.cpp
    ${CMAKE_CURRENT_BINARY_DIR}/framedyn.def)

add_library(framedyn MODULE ${SOURCE})
target_link_libraries(framedyn cpprt)
set_target_cpp_properties(framedyn WITH_EXCEPTIONS)
set_module_type(framedyn win32dll UNICODE)
add_importlibs(framedyn oleaut32 msvcrt kernel32 ntdll)
add_cd_file(TARGET framedyn DESTINATION reactos/system32/wbem FOR all)

if(NOT MSVC)
    add_asm_files(framedynex_asm alias_gcc.s)
    add_library(framedynex ${framedynex_asm})
    set_target_properties(framedynex PROPERTIES LINKER_LANGUAGE ASM)
else()
    target_compile_options(framedyn PRIVATE /Zc:wchar_t-)
endif()
* Revert r73869 because wmi was mentioned nowhere in CORE-9111, nor in our tree restructure wiki, nor any developers discussions. This is the ReactOS trunk, not a branch. svn path=/trunk/; revision=73870 2017-02-21 09:04:05 +00:00
			`spec2def(framedyn.dll framedyn.spec ADD_IMPORTLIB)`

			`list(APPEND SOURCE`
			`main.c`
			`chstring.cpp`
			`provider.cpp`
			`${CMAKE_CURRENT_BINARY_DIR}/framedyn.def)`

[CMAKE] Use modules instead of shared libraries There is no need to compile our DLLs as shared libraries since we are managing symbols exports and imports through spec files. On my system, this reduces the configure-time by a factor of two. 2019-03-20 13:19:48 +00:00			`add_library(framedyn MODULE ${SOURCE})`
[CMAKE] Get rid of the set_cpp macro Instead of messing with global variables and the like, we introduce two target properties: - WITH_CXX_EXCEPTIONS: if you want to use C++ exceptions - WITH_CXX_RTTI: if you need RTTI in your module You can use the newly introduced set_target_cpp_properties function, with WITH_EXCEPTIONS and WITH_RTTI arguments We also introduce two libraries : - cpprt: for C++ runtime routines - cppstl: for the C++ standard template library NB: On GCC, this requires to create imported libraries with the related built-in libraries:libsupc++, limingwex, libstdc++ Finally, we manage the relevant flags with the ad-hoc generator expressions So, if you don't need exceptions, nor RTTI, nor use any runtime at all: you simply have nothing else to do than add your C++ file to your module 2020-09-18 07:34:18 +00:00			`target_link_libraries(framedyn cpprt)`
			`set_target_cpp_properties(framedyn WITH_EXCEPTIONS)`
* Revert r73869 because wmi was mentioned nowhere in CORE-9111, nor in our tree restructure wiki, nor any developers discussions. This is the ReactOS trunk, not a branch. svn path=/trunk/; revision=73870 2017-02-21 09:04:05 +00:00			`set_module_type(framedyn win32dll UNICODE)`
			`add_importlibs(framedyn oleaut32 msvcrt kernel32 ntdll)`
			`add_cd_file(TARGET framedyn DESTINATION reactos/system32/wbem FOR all)`

			`if(NOT MSVC)`
			`add_asm_files(framedynex_asm alias_gcc.s)`
			`add_library(framedynex ${framedynex_asm})`
			`set_target_properties(framedynex PROPERTIES LINKER_LANGUAGE ASM)`
[CMAKE] Get rid of add_compile_flags Use add_compile_options and the like instead 2020-09-21 10:16:02 +00:00			`else()`
			`target_compile_options(framedyn PRIVATE /Zc:wchar_t-)`
* Revert r73869 because wmi was mentioned nowhere in CORE-9111, nor in our tree restructure wiki, nor any developers discussions. This is the ReactOS trunk, not a branch. svn path=/trunk/; revision=73870 2017-02-21 09:04:05 +00:00			`endif()`