1
0
mirror of synced 2024-12-24 13:34:50 +01:00
ImHex/main/gui/CMakeLists.txt

82 lines
2.6 KiB
CMake
Raw Normal View History

project(main)
add_executable(main ${APPLICATION_TYPE}
source/main.cpp
source/crash_handlers.cpp
source/stacktrace.cpp
source/window/window.cpp
source/window/win_window.cpp
source/window/macos_window.cpp
source/window/linux_window.cpp
source/window/web_window.cpp
source/messaging/common.cpp
source/messaging/linux.cpp
source/messaging/macos.cpp
source/messaging/win.cpp
source/messaging/web.cpp
source/init/splash_window.cpp
source/init/tasks.cpp
source/init/run/common.cpp
source/init/run/native.cpp
source/init/run/web.cpp
source/init/run/cli.cpp
${IMHEX_ICON}
)
target_include_directories(main PUBLIC include)
setupCompilerFlags(main)
setupCompilerFlags(libimhex)
set(LIBROMFS_RESOURCE_LOCATION ${CMAKE_CURRENT_SOURCE_DIR}/romfs)
set(LIBROMFS_PROJECT_NAME imhex)
add_subdirectory(${CMAKE_CURRENT_SOURCE_DIR}/../../lib/external/libromfs ${CMAKE_CURRENT_BINARY_DIR}/main/gui/libromfs EXCLUDE_FROM_ALL)
add_dependencies(imhex_all main)
if (EMSCRIPTEN)
target_link_options(main PRIVATE -sUSE_GLFW=3 -sUSE_PTHREADS=1 -sALLOW_MEMORY_GROWTH=1)
target_link_options(main PRIVATE -sTOTAL_MEMORY=134217728)
target_link_options(main PRIVATE -sMAX_WEBGL_VERSION=2)
target_link_options(main PRIVATE -sEXPORTED_RUNTIME_METHODS=ccall)
target_link_options(main PRIVATE -sFETCH)
target_link_options(main PRIVATE -sWASM_BIGINT)
target_link_options(main PRIVATE -O1)
target_link_options(main PRIVATE -sLEGACY_GL_EMULATION)
target_link_options(main PRIVATE -fsanitize=null)
target_link_options(main PRIVATE -fsanitize-minimal-runtime)
target_link_libraries(main PRIVATE idbfs.js)
endif ()
set_target_properties(main PROPERTIES
build: Xcode accomodating CMake setup (#1688) ### Problem description This PR implements some rudimentary Xcode support for building and editing ImHex. ### Implementation description #### Problem 1: Xcode is a multi-configuration buildsystem The project is already rather CMake generator independent, thus it did not need to change much to support Xcode's multi-configuration paradigm: By default, CMake generates a `.xcodeproj` in which targets build their artifacts into the specified `<>_OUTPUT_DIRECTORY`, postfixed by the currently active configuration. To better fit the existing paradigm, I instead opted ot introduce `IMHEX_MAIN_OUTPUT_DIRECTORY`. This variable is equal to the previously used `RUNTIME_OUTPUT_DIRECTORY` when using other generators, and is changed to include a configuration specific _prefix_ when used with Xcode. The result is different output directories when using Xcode, and no changes when using any other generator. #### Problem 2: ImHex does not support AppleClang To allow building the codebase with Xcode, I have introduced `IMHEX_IDE_HELPERS_OVERRIDE_XCODE_COMPILER`. Specifying this option to `ON` will force CMake to honor the user specified compiler settings, even when using the Xcode generator. In practice this can be used together with the new "xcode" CMakePreset to build the project with mainline clang using `xcodebuild`, or Xcode itself by generating a buildsystem like so: ``` cmake --preset xcode -DCMAKE_PREFIX_PATH=/opt/homebrew/opt/llvm@17 ``` This solution is of course not without flaws. The inner workings are a particularly ugly hack, and mainline clang does not implement the necessary extensions to allow Xcode to index the code. Regardless this option is useful to enable future work in terms of bundling/signing macOS applications in the "intended" way using Xcode without additional source modifications. #### Problem 3: Vanilla CMake + Xcode = Bad developer UX By default, the CMake generated `.xcodeproj` is a mess. Tons of targets are scattered about, and source files are not organized beyond grouping them into a "Source Files" and "Header Files" group. Even "Header Files" is missing, because the ImHex build system does not regard private header files of libraries as sources of a target, and Xcode does not try to guess this information. The solution is twofold: * Additional code has been added which organizes the targets into a neat folder structure * Additional code was added behind a configuration flag `IMHEX_IDE_HELPERS_INTRUSIVE_IDE_TWEAKS` which automatically creates source file trees in Xcode targets, and discovers the non-declared header files via the folder convention. ### Screenshots N/A ### Additional things As a bonus: `IMHEX_OFFLINE_BUILD` assumes that ImHex-Patterns is cloned into the source tree. I have added an additional fallback that tries to locate it as a sibling folder of `${CMAKE_SOURCE_DIR}`, as this meshes better with my filesystem setup. The setup was tested with `CMake 3.29.2`, `Xcode 15.2`, and `llvm@17` from homebrew.
2024-05-20 12:12:57 +02:00
OUTPUT_NAME "${IMHEX_APPLICATION_NAME}"
RUNTIME_OUTPUT_DIRECTORY "${IMHEX_MAIN_OUTPUT_DIRECTORY}"
)
target_compile_definitions(main PRIVATE IMHEX_PROJECT_NAME="${PROJECT_NAME}")
target_link_libraries(main PRIVATE libromfs-imhex libimhex libwolv ${LIBBACKTRACE_LIBRARIES} LLVMDemangle)
if (WIN32)
target_link_libraries(main PRIVATE usp10 wsock32 ws2_32 Dwmapi.lib Winmm.lib)
else ()
target_link_libraries(main PRIVATE pthread)
if (NOT APPLE)
find_package(Fontconfig)
if (TARGET Fontconfig::Fontconfig)
message(STATUS "Using Fontconfig version: ${Fontconfig_VERSION}")
target_link_libraries(main PRIVATE Fontconfig::Fontconfig)
target_compile_definitions(main PRIVATE IMHEX_HAS_FONTCONFIG)
endif ()
endif ()
endif ()
2024-02-29 19:48:16 +01:00
precompileHeaders(main ${CMAKE_CURRENT_SOURCE_DIR}/include)
if (APPLE)
add_compile_definitions(GL_SILENCE_DEPRECATION)
build: Xcode accomodating CMake setup (#1688) ### Problem description This PR implements some rudimentary Xcode support for building and editing ImHex. ### Implementation description #### Problem 1: Xcode is a multi-configuration buildsystem The project is already rather CMake generator independent, thus it did not need to change much to support Xcode's multi-configuration paradigm: By default, CMake generates a `.xcodeproj` in which targets build their artifacts into the specified `<>_OUTPUT_DIRECTORY`, postfixed by the currently active configuration. To better fit the existing paradigm, I instead opted ot introduce `IMHEX_MAIN_OUTPUT_DIRECTORY`. This variable is equal to the previously used `RUNTIME_OUTPUT_DIRECTORY` when using other generators, and is changed to include a configuration specific _prefix_ when used with Xcode. The result is different output directories when using Xcode, and no changes when using any other generator. #### Problem 2: ImHex does not support AppleClang To allow building the codebase with Xcode, I have introduced `IMHEX_IDE_HELPERS_OVERRIDE_XCODE_COMPILER`. Specifying this option to `ON` will force CMake to honor the user specified compiler settings, even when using the Xcode generator. In practice this can be used together with the new "xcode" CMakePreset to build the project with mainline clang using `xcodebuild`, or Xcode itself by generating a buildsystem like so: ``` cmake --preset xcode -DCMAKE_PREFIX_PATH=/opt/homebrew/opt/llvm@17 ``` This solution is of course not without flaws. The inner workings are a particularly ugly hack, and mainline clang does not implement the necessary extensions to allow Xcode to index the code. Regardless this option is useful to enable future work in terms of bundling/signing macOS applications in the "intended" way using Xcode without additional source modifications. #### Problem 3: Vanilla CMake + Xcode = Bad developer UX By default, the CMake generated `.xcodeproj` is a mess. Tons of targets are scattered about, and source files are not organized beyond grouping them into a "Source Files" and "Header Files" group. Even "Header Files" is missing, because the ImHex build system does not regard private header files of libraries as sources of a target, and Xcode does not try to guess this information. The solution is twofold: * Additional code has been added which organizes the targets into a neat folder structure * Additional code was added behind a configuration flag `IMHEX_IDE_HELPERS_INTRUSIVE_IDE_TWEAKS` which automatically creates source file trees in Xcode targets, and discovers the non-declared header files via the folder convention. ### Screenshots N/A ### Additional things As a bonus: `IMHEX_OFFLINE_BUILD` assumes that ImHex-Patterns is cloned into the source tree. I have added an additional fallback that tries to locate it as a sibling folder of `${CMAKE_SOURCE_DIR}`, as this meshes better with my filesystem setup. The setup was tested with `CMake 3.29.2`, `Xcode 15.2`, and `llvm@17` from homebrew.
2024-05-20 12:12:57 +02:00
endif ()