2014-08-24 06:52:05 +05:30
|
|
|
# Enable modules to include each other's files
|
|
|
|
|
include_directories(.)
|
|
|
|
|
|
Port yuzu-emu/yuzu#2253: "Migrate off directly modifying CMAKE_* compilation-related flags directly" (#4714)
* CMakeLists: Move compilation flags into the src directory
We generally shouldn't be hijacking CMAKE_CXX_FLAGS, etc as a means to
append flags to the targets, since this adds the compilation flags to
everything, including our externals, which can result in weird issues
and makes the build hierarchy fragile.
Instead, we want to just apply these compilation flags to our targets,
and let those managing external libraries to properly specify their
compilation flags.
This also results in us not getting as many warnings, as we don't raise
the warning level on every external target.
* CMakeLists: Move off of modifying CMAKE_*-related flags
Modifying CMAKE_* related flags directly applies those changes to every
single CMake target. This includes even the targets we have in the
externals directory.
So, if we ever increased our warning levels, or enabled particular ones,
or enabled any other compilation setting, then this would apply to
externals as well, which is often not desirable.
This makes our compilation flag setup less error prone by only applying
our settings to our targets and leaving the externals alone entirely.
This also means we don't end up clobbering any provided flags on the
command line either, allowing users to specifically use the flags they
want.
2019-06-18 15:42:32 +05:30
|
|
|
# CMake seems to only define _DEBUG on Windows
|
|
|
|
|
set_property(DIRECTORY APPEND PROPERTY
|
|
|
|
|
COMPILE_DEFINITIONS $<$<CONFIG:Debug>:_DEBUG> $<$<NOT:$<CONFIG:Debug>>:NDEBUG>)
|
|
|
|
|
|
|
|
|
|
# Set compilation flags
|
|
|
|
|
if (MSVC)
|
|
|
|
|
set(CMAKE_CONFIGURATION_TYPES Debug Release CACHE STRING "" FORCE)
|
|
|
|
|
|
|
|
|
|
# Silence "deprecation" warnings
|
|
|
|
|
add_definitions(-D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS)
|
|
|
|
|
|
|
|
|
|
# Avoid windows.h junk
|
|
|
|
|
add_definitions(-DNOMINMAX)
|
|
|
|
|
|
|
|
|
|
# Avoid windows.h from including some usually unused libs like winsocks.h, since this might cause some redefinition errors.
|
|
|
|
|
add_definitions(-DWIN32_LEAN_AND_MEAN)
|
|
|
|
|
|
2019-04-16 03:02:47 +05:30
|
|
|
# Ensure that projects build with Unicode support.
|
|
|
|
|
add_definitions(-DUNICODE -D_UNICODE)
|
|
|
|
|
|
2019-05-07 23:36:20 +05:30
|
|
|
# /W3 - Level 3 warnings
|
|
|
|
|
# /MP - Multi-threaded compilation
|
|
|
|
|
# /Zi - Output debugging information
|
|
|
|
|
# /Zo - Enhanced debug info for optimized builds
|
|
|
|
|
# /permissive- - Enables stricter C++ standards conformance checks
|
|
|
|
|
# /EHsc - C++-only exception handling semantics
|
2019-05-10 01:19:27 +05:30
|
|
|
# /volatile:iso - Use strict standards-compliant volatile semantics.
|
2019-05-07 23:36:20 +05:30
|
|
|
# /Zc:externConstexpr - Allow extern constexpr variables to have external linkage, like the standard mandates
|
|
|
|
|
# /Zc:inline - Let codegen omit inline functions in object files
|
|
|
|
|
# /Zc:throwingNew - Let codegen assume `operator new` (without std::nothrow) will never return null
|
2020-03-31 22:24:28 +05:30
|
|
|
# /external:* - Suppress warnings from external headers
|
2019-05-07 23:32:29 +05:30
|
|
|
add_compile_options(
|
|
|
|
|
/W3
|
2020-03-31 22:24:28 +05:30
|
|
|
/MP
|
2019-05-07 23:32:29 +05:30
|
|
|
/Zi
|
|
|
|
|
/Zo
|
|
|
|
|
/permissive-
|
|
|
|
|
/EHsc
|
2019-05-10 01:19:27 +05:30
|
|
|
/volatile:iso
|
2019-05-07 23:36:20 +05:30
|
|
|
/Zc:externConstexpr
|
2019-05-07 23:32:29 +05:30
|
|
|
/Zc:inline
|
2020-03-31 22:24:28 +05:30
|
|
|
/Zc:throwingNew
|
|
|
|
|
/experimental:external
|
|
|
|
|
/external:I "${CMAKE_SOURCE_DIR}/externals"
|
|
|
|
|
/external:anglebrackets
|
|
|
|
|
/external:W0
|
2019-05-07 23:32:29 +05:30
|
|
|
)
|
Port yuzu-emu/yuzu#2253: "Migrate off directly modifying CMAKE_* compilation-related flags directly" (#4714)
* CMakeLists: Move compilation flags into the src directory
We generally shouldn't be hijacking CMAKE_CXX_FLAGS, etc as a means to
append flags to the targets, since this adds the compilation flags to
everything, including our externals, which can result in weird issues
and makes the build hierarchy fragile.
Instead, we want to just apply these compilation flags to our targets,
and let those managing external libraries to properly specify their
compilation flags.
This also results in us not getting as many warnings, as we don't raise
the warning level on every external target.
* CMakeLists: Move off of modifying CMAKE_*-related flags
Modifying CMAKE_* related flags directly applies those changes to every
single CMake target. This includes even the targets we have in the
externals directory.
So, if we ever increased our warning levels, or enabled particular ones,
or enabled any other compilation setting, then this would apply to
externals as well, which is often not desirable.
This makes our compilation flag setup less error prone by only applying
our settings to our targets and leaving the externals alone entirely.
This also means we don't end up clobbering any provided flags on the
command line either, allowing users to specifically use the flags they
want.
2019-06-18 15:42:32 +05:30
|
|
|
|
|
|
|
|
# /GS- - No stack buffer overflow checks
|
|
|
|
|
add_compile_options("$<$<CONFIG:Release>:/GS->")
|
|
|
|
|
|
|
|
|
|
set(CMAKE_EXE_LINKER_FLAGS_DEBUG "/DEBUG /MANIFEST:NO" CACHE STRING "" FORCE)
|
|
|
|
|
set(CMAKE_EXE_LINKER_FLAGS_RELEASE "/DEBUG /MANIFEST:NO /INCREMENTAL:NO /OPT:REF,ICF" CACHE STRING "" FORCE)
|
|
|
|
|
else()
|
2019-05-04 11:36:55 +05:30
|
|
|
add_compile_options(
|
|
|
|
|
-Wall
|
|
|
|
|
-Wno-attributes
|
|
|
|
|
)
|
Port yuzu-emu/yuzu#2253: "Migrate off directly modifying CMAKE_* compilation-related flags directly" (#4714)
* CMakeLists: Move compilation flags into the src directory
We generally shouldn't be hijacking CMAKE_CXX_FLAGS, etc as a means to
append flags to the targets, since this adds the compilation flags to
everything, including our externals, which can result in weird issues
and makes the build hierarchy fragile.
Instead, we want to just apply these compilation flags to our targets,
and let those managing external libraries to properly specify their
compilation flags.
This also results in us not getting as many warnings, as we don't raise
the warning level on every external target.
* CMakeLists: Move off of modifying CMAKE_*-related flags
Modifying CMAKE_* related flags directly applies those changes to every
single CMake target. This includes even the targets we have in the
externals directory.
So, if we ever increased our warning levels, or enabled particular ones,
or enabled any other compilation setting, then this would apply to
externals as well, which is often not desirable.
This makes our compilation flag setup less error prone by only applying
our settings to our targets and leaving the externals alone entirely.
This also means we don't end up clobbering any provided flags on the
command line either, allowing users to specifically use the flags they
want.
2019-06-18 15:42:32 +05:30
|
|
|
|
|
|
|
|
if (APPLE AND CMAKE_CXX_COMPILER_ID STREQUAL Clang)
|
|
|
|
|
add_compile_options("-stdlib=libc++")
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
# Set file offset size to 64 bits.
|
|
|
|
|
#
|
|
|
|
|
# On modern Unixes, this is typically already the case. The lone exception is
|
|
|
|
|
# glibc, which may default to 32 bits. glibc allows this to be configured
|
|
|
|
|
# by setting _FILE_OFFSET_BITS.
|
|
|
|
|
if(CMAKE_SYSTEM_NAME STREQUAL "Linux" OR MINGW)
|
|
|
|
|
add_definitions(-D_FILE_OFFSET_BITS=64)
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
if (MINGW)
|
|
|
|
|
add_definitions(-DMINGW_HAS_SECURE_API)
|
2019-08-14 07:40:22 +05:30
|
|
|
if (COMPILE_WITH_DWARF)
|
|
|
|
|
add_compile_options("-gdwarf")
|
|
|
|
|
endif()
|
Port yuzu-emu/yuzu#2253: "Migrate off directly modifying CMAKE_* compilation-related flags directly" (#4714)
* CMakeLists: Move compilation flags into the src directory
We generally shouldn't be hijacking CMAKE_CXX_FLAGS, etc as a means to
append flags to the targets, since this adds the compilation flags to
everything, including our externals, which can result in weird issues
and makes the build hierarchy fragile.
Instead, we want to just apply these compilation flags to our targets,
and let those managing external libraries to properly specify their
compilation flags.
This also results in us not getting as many warnings, as we don't raise
the warning level on every external target.
* CMakeLists: Move off of modifying CMAKE_*-related flags
Modifying CMAKE_* related flags directly applies those changes to every
single CMake target. This includes even the targets we have in the
externals directory.
So, if we ever increased our warning levels, or enabled particular ones,
or enabled any other compilation setting, then this would apply to
externals as well, which is often not desirable.
This makes our compilation flag setup less error prone by only applying
our settings to our targets and leaving the externals alone entirely.
This also means we don't end up clobbering any provided flags on the
command line either, allowing users to specifically use the flags they
want.
2019-06-18 15:42:32 +05:30
|
|
|
|
|
|
|
|
if (MINGW_STATIC_BUILD)
|
|
|
|
|
add_definitions(-DQT_STATICPLUGIN)
|
|
|
|
|
add_compile_options("-static")
|
|
|
|
|
endif()
|
|
|
|
|
endif()
|
2019-06-30 16:59:52 +05:30
|
|
|
|
|
|
|
|
if(CMAKE_SYSTEM_NAME STREQUAL "Linux" OR MINGW)
|
|
|
|
|
# GNU ar: Create thin archive files.
|
|
|
|
|
# Requires binutils-2.19 or later.
|
|
|
|
|
set(CMAKE_C_ARCHIVE_CREATE "<CMAKE_AR> qcTP <TARGET> <LINK_FLAGS> <OBJECTS>")
|
|
|
|
|
set(CMAKE_C_ARCHIVE_APPEND "<CMAKE_AR> qTP <TARGET> <LINK_FLAGS> <OBJECTS>")
|
|
|
|
|
set(CMAKE_CXX_ARCHIVE_CREATE "<CMAKE_AR> qcTP <TARGET> <LINK_FLAGS> <OBJECTS>")
|
|
|
|
|
set(CMAKE_CXX_ARCHIVE_APPEND "<CMAKE_AR> qTP <TARGET> <LINK_FLAGS> <OBJECTS>")
|
|
|
|
|
endif()
|
Port yuzu-emu/yuzu#2253: "Migrate off directly modifying CMAKE_* compilation-related flags directly" (#4714)
* CMakeLists: Move compilation flags into the src directory
We generally shouldn't be hijacking CMAKE_CXX_FLAGS, etc as a means to
append flags to the targets, since this adds the compilation flags to
everything, including our externals, which can result in weird issues
and makes the build hierarchy fragile.
Instead, we want to just apply these compilation flags to our targets,
and let those managing external libraries to properly specify their
compilation flags.
This also results in us not getting as many warnings, as we don't raise
the warning level on every external target.
* CMakeLists: Move off of modifying CMAKE_*-related flags
Modifying CMAKE_* related flags directly applies those changes to every
single CMake target. This includes even the targets we have in the
externals directory.
So, if we ever increased our warning levels, or enabled particular ones,
or enabled any other compilation setting, then this would apply to
externals as well, which is often not desirable.
This makes our compilation flag setup less error prone by only applying
our settings to our targets and leaving the externals alone entirely.
This also means we don't end up clobbering any provided flags on the
command line either, allowing users to specifically use the flags they
want.
2019-06-18 15:42:32 +05:30
|
|
|
endif()
|
|
|
|
|
|
2013-08-30 09:05:09 +05:30
|
|
|
add_subdirectory(common)
|
|
|
|
|
add_subdirectory(core)
|
2014-04-10 08:39:05 +05:30
|
|
|
add_subdirectory(video_core)
|
2016-02-21 18:43:52 +05:30
|
|
|
add_subdirectory(audio_core)
|
2017-07-08 01:04:15 +05:30
|
|
|
add_subdirectory(network)
|
2017-01-21 15:23:03 +05:30
|
|
|
add_subdirectory(input_common)
|
2016-03-20 20:28:24 +05:30
|
|
|
add_subdirectory(tests)
|
Port yuzu-emu/yuzu#2253: "Migrate off directly modifying CMAKE_* compilation-related flags directly" (#4714)
* CMakeLists: Move compilation flags into the src directory
We generally shouldn't be hijacking CMAKE_CXX_FLAGS, etc as a means to
append flags to the targets, since this adds the compilation flags to
everything, including our externals, which can result in weird issues
and makes the build hierarchy fragile.
Instead, we want to just apply these compilation flags to our targets,
and let those managing external libraries to properly specify their
compilation flags.
This also results in us not getting as many warnings, as we don't raise
the warning level on every external target.
* CMakeLists: Move off of modifying CMAKE_*-related flags
Modifying CMAKE_* related flags directly applies those changes to every
single CMake target. This includes even the targets we have in the
externals directory.
So, if we ever increased our warning levels, or enabled particular ones,
or enabled any other compilation setting, then this would apply to
externals as well, which is often not desirable.
This makes our compilation flag setup less error prone by only applying
our settings to our targets and leaving the externals alone entirely.
This also means we don't end up clobbering any provided flags on the
command line either, allowing users to specifically use the flags they
want.
2019-06-18 15:42:32 +05:30
|
|
|
|
2016-03-01 22:54:18 +05:30
|
|
|
if (ENABLE_SDL2)
|
2014-08-24 06:52:05 +05:30
|
|
|
add_subdirectory(citra)
|
|
|
|
|
endif()
|
Port yuzu-emu/yuzu#2253: "Migrate off directly modifying CMAKE_* compilation-related flags directly" (#4714)
* CMakeLists: Move compilation flags into the src directory
We generally shouldn't be hijacking CMAKE_CXX_FLAGS, etc as a means to
append flags to the targets, since this adds the compilation flags to
everything, including our externals, which can result in weird issues
and makes the build hierarchy fragile.
Instead, we want to just apply these compilation flags to our targets,
and let those managing external libraries to properly specify their
compilation flags.
This also results in us not getting as many warnings, as we don't raise
the warning level on every external target.
* CMakeLists: Move off of modifying CMAKE_*-related flags
Modifying CMAKE_* related flags directly applies those changes to every
single CMake target. This includes even the targets we have in the
externals directory.
So, if we ever increased our warning levels, or enabled particular ones,
or enabled any other compilation setting, then this would apply to
externals as well, which is often not desirable.
This makes our compilation flag setup less error prone by only applying
our settings to our targets and leaving the externals alone entirely.
This also means we don't end up clobbering any provided flags on the
command line either, allowing users to specifically use the flags they
want.
2019-06-18 15:42:32 +05:30
|
|
|
|
2014-08-24 06:52:05 +05:30
|
|
|
if (ENABLE_QT)
|
|
|
|
|
add_subdirectory(citra_qt)
|
2013-08-30 09:05:09 +05:30
|
|
|
endif()
|
2018-11-19 05:53:41 +05:30
|
|
|
if (ANDROID)
|
2018-12-25 02:32:47 +05:30
|
|
|
add_subdirectory(android/app/src/main/cpp)
|
|
|
|
|
else()
|
|
|
|
|
add_subdirectory(dedicated_room)
|
2018-11-19 05:53:41 +05:30
|
|
|
endif()
|
Port yuzu-emu/yuzu#2253: "Migrate off directly modifying CMAKE_* compilation-related flags directly" (#4714)
* CMakeLists: Move compilation flags into the src directory
We generally shouldn't be hijacking CMAKE_CXX_FLAGS, etc as a means to
append flags to the targets, since this adds the compilation flags to
everything, including our externals, which can result in weird issues
and makes the build hierarchy fragile.
Instead, we want to just apply these compilation flags to our targets,
and let those managing external libraries to properly specify their
compilation flags.
This also results in us not getting as many warnings, as we don't raise
the warning level on every external target.
* CMakeLists: Move off of modifying CMAKE_*-related flags
Modifying CMAKE_* related flags directly applies those changes to every
single CMake target. This includes even the targets we have in the
externals directory.
So, if we ever increased our warning levels, or enabled particular ones,
or enabled any other compilation setting, then this would apply to
externals as well, which is often not desirable.
This makes our compilation flag setup less error prone by only applying
our settings to our targets and leaving the externals alone entirely.
This also means we don't end up clobbering any provided flags on the
command line either, allowing users to specifically use the flags they
want.
2019-06-18 15:42:32 +05:30
|
|
|
|
2017-07-10 03:22:18 +05:30
|
|
|
if (ENABLE_WEB_SERVICE)
|
|
|
|
|
add_subdirectory(web_service)
|
|
|
|
|
endif()
|
