Victor Perevertkin d10728a645 [CMAKE] Rely less on CMAKE_BUILD_TYPE variable ... Having conditional statements with CMAKE_BUILD_TYPE is an antipattern See https://stackoverflow.com/questions/66079007/having-conditional-statements-on-build-type-variable-a-good-design We use both single- and multi-config generators (Ninja and VS), so we can't really rely on CMAKE_BUILD_TYPE, because it's not always set. This commit alters some conditional flags to use <$CONFIG:...> generator expression, but is still not complete. Also, our default optimization level (4) now has what was always a de-facto flags		2021-04-15 06:44:56 +03:00
..
baseaddress.cmake
baseaddress_dwarf.cmake
baseaddress_msvc.cmake
baseaddress_msvc_x64.cmake
CMakeMacros.cmake	[BOOTDATA][CMAKE] Sort 2 directories out	2021-04-12 17:40:18 +02:00
compilerflags.cmake
config.cmake	[CMAKE] Unify configs for architectures	2021-04-15 06:44:52 +03:00
gcc.cmake	[CMAKE] Unify configs for architectures	2021-04-15 06:44:52 +03:00
host-tools.cmake
host-tools.in
init-section.lds
localization.cmake
midl-support.cmake
msvc.cmake	[CMAKE] Rely less on CMAKE_BUILD_TYPE variable	2021-04-15 06:44:56 +03:00
widl-support.cmake
writing_CmakeLists_for_ReactOS.txt