reactos/modules/rosapps/applications/fraginator/CMakeLists.txt


list(APPEND SOURCE
	Fraginator.cpp
	MainDialog.cpp
	ReportDialog.cpp)

list(APPEND UNFRAG_SOURCE
	Unfrag.cpp
	Defragment.cpp
	DriveVolume.cpp)

add_executable(frag ${SOURCE} ${UNFRAG_SOURCE} Fraginator.rc)
target_link_libraries(frag cppstl)
set_target_cpp_properties(frag WITH_EXCEPTIONS)
set_module_type(frag win32gui UNICODE)
add_importlibs(frag user32 advapi32 shell32 comctl32 msvcrt kernel32 ntdll)
add_cd_file(TARGET frag DESTINATION reactos/system32 FOR all)

add_executable(unfrag ${UNFRAG_SOURCE})
target_link_libraries(unfrag cppstl)
set_target_cpp_properties(unfrag WITH_EXCEPTIONS)
target_compile_definitions(unfrag PRIVATE _CUI_)
set_module_type(unfrag win32cui UNICODE)
add_importlibs(unfrag advapi32 msvcrt kernel32 ntdll)
add_cd_file(TARGET unfrag DESTINATION reactos/system32 FOR all)
[ROSAPPS] Add Fraginator to build. This thing NEVER could have worked in that state in RBUILD. rc file was not even selected to have any chance of any dialog. Billions of things are defined a billion times in any language RC file. etcetc. svn path=/trunk/; revision=67309 2015-04-19 20:30:44 +00:00
			`list(APPEND SOURCE`
			`Fraginator.cpp`
			`MainDialog.cpp`
			`ReportDialog.cpp)`

			`list(APPEND UNFRAG_SOURCE`
			`Unfrag.cpp`
			`Defragment.cpp`
			`DriveVolume.cpp)`
[FRAGINATOR] Silence a ton of warnings. svn path=/trunk/; revision=73019 2016-10-22 12:13:34 +00:00
[ROSAPPS] Add Fraginator to build. This thing NEVER could have worked in that state in RBUILD. rc file was not even selected to have any chance of any dialog. Billions of things are defined a billion times in any language RC file. etcetc. svn path=/trunk/; revision=67309 2015-04-19 20:30:44 +00:00			`add_executable(frag ${SOURCE} ${UNFRAG_SOURCE} Fraginator.rc)`
[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(frag cppstl)`
			`set_target_cpp_properties(frag WITH_EXCEPTIONS)`
[ROSAPPS] Add Fraginator to build. This thing NEVER could have worked in that state in RBUILD. rc file was not even selected to have any chance of any dialog. Billions of things are defined a billion times in any language RC file. etcetc. svn path=/trunk/; revision=67309 2015-04-19 20:30:44 +00:00			`set_module_type(frag win32gui UNICODE)`
			`add_importlibs(frag user32 advapi32 shell32 comctl32 msvcrt kernel32 ntdll)`
			`add_cd_file(TARGET frag DESTINATION reactos/system32 FOR all)`

			`add_executable(unfrag ${UNFRAG_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(unfrag cppstl)`
			`set_target_cpp_properties(unfrag WITH_EXCEPTIONS)`
[CMAKE] target_compile_definitions() calls: Remove (now) useless '-D' (#3490) Documented as automatically removed, since CMake 3.12.4 at least. https://cmake.org/cmake/help/v3.12/command/target_compile_definitions.html 2021-03-03 03:16:02 +00:00			`target_compile_definitions(unfrag PRIVATE _CUI_)`
[ROSAPPS] Add Fraginator to build. This thing NEVER could have worked in that state in RBUILD. rc file was not even selected to have any chance of any dialog. Billions of things are defined a billion times in any language RC file. etcetc. svn path=/trunk/; revision=67309 2015-04-19 20:30:44 +00:00			`set_module_type(unfrag win32cui UNICODE)`
			`add_importlibs(unfrag advapi32 msvcrt kernel32 ntdll)`
[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			`add_cd_file(TARGET unfrag DESTINATION reactos/system32 FOR all)`