3party/pugixml
0
0
Fork 0
mirror of https://github.com/zeux/pugixml.git synced 2024-12-25 20:14:10 +08:00
Code Issues Projects Releases Wiki Activity
pugixml/CMakeLists.txt

283 lines
9.6 KiB
CMake
Raw Normal View History

Update CMake version to 3.5...3.30 This should retain compatibility with earlier version of CMake and suppress the deprecation warning for quite some time.
2024-11-17 08:25:06 +09:00
cmake_minimum_required(VERSION 3.5...3.30)
build: Fix CMake PUGIXML_STATIC_CRT behavior Implementation of PUGIXML_STATIC_CRT for newer CMake versions (3.15+) depend on MSVC_RUNTIME_LIBRARY, but this only works if the policy is defined *before* the project.
2023-04-21 13:24:59 -07:00
# Policy configuration; this *MUST* be specified before project is defined
if(POLICY CMP0091)
cmake_policy(SET CMP0091 NEW) # Enables use of MSVC_RUNTIME_LIBRARY
endif()
Update version to 1.14 everywhere
2023-09-07 11:55:13 -07:00
project(pugixml VERSION 1.14 LANGUAGES CXX)
Add CMake option on MSVC- STATIC_CRT
2015-12-03 12:33:44 +02:00
:construction: Begin moving pugixml to modern(ish) CMake :arrow_up: Bump CMake minimum to 3.4 :bug: pugixml no longer requires a C compiler to be found or set to compile correctly. This speeds up configuration and building on windows. :construction: Begin laying groundwork to backport MSVC_RUNTIME_LIBRARY property
2019-09-28 10:47:15 -07:00
include(CMakePackageConfigHelpers)
include(CMakeDependentOption)
include(GNUInstallDirs)
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
cmake_dependent_option(PUGIXML_USE_VERSIONED_LIBDIR
:construction: Begin moving pugixml to modern(ish) CMake :arrow_up: Bump CMake minimum to 3.4 :bug: pugixml no longer requires a C compiler to be found or set to compile correctly. This speeds up configuration and building on windows. :construction: Begin laying groundwork to backport MSVC_RUNTIME_LIBRARY property
2019-09-28 10:47:15 -07:00
"Use a private subdirectory to install the headers and libraries" OFF
"CMAKE_SOURCE_DIR STREQUAL PROJECT_SOURCE_DIR" OFF)
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
cmake_dependent_option(PUGIXML_USE_POSTFIX
:construction: Begin moving pugixml to modern(ish) CMake :arrow_up: Bump CMake minimum to 3.4 :bug: pugixml no longer requires a C compiler to be found or set to compile correctly. This speeds up configuration and building on windows. :construction: Begin laying groundwork to backport MSVC_RUNTIME_LIBRARY property
2019-09-28 10:47:15 -07:00
"Use separate postfix for each configuration to make sure you can install multiple build outputs" OFF
"CMAKE_SOURCE_DIR STREQUAL PROJECT_SOURCE_DIR" OFF)
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
cmake_dependent_option(PUGIXML_STATIC_CRT
:construction: Begin moving pugixml to modern(ish) CMake :arrow_up: Bump CMake minimum to 3.4 :bug: pugixml no longer requires a C compiler to be found or set to compile correctly. This speeds up configuration and building on windows. :construction: Begin laying groundwork to backport MSVC_RUNTIME_LIBRARY property
2019-09-28 10:47:15 -07:00
"Use static MSVC RT libraries" OFF
"MSVC" OFF)
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
cmake_dependent_option(PUGIXML_BUILD_TESTS
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
"Build pugixml tests" OFF
Remove BUILD_TESTING as prerequisite for the PUGIXML_BUILD_TESTS; it was always set by including CTest, now CTest is conditionally included later on
2023-10-06 10:02:15 +02:00
"CMAKE_SOURCE_DIR STREQUAL PROJECT_SOURCE_DIR" OFF)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Re-introduced the custom build defines The ability to use custom build defines were removed in commit: 1c5a0bb32583fd294022e68e66b541bf6ff71a67 This commit will reintroduce this feature, but using a prefixed variable name.
2021-06-15 09:00:31 +02:00
# Custom build defines
Use target_compile_definitions for custom defines Replace `add_definitions` with `target_compile_definitions` for specified targets. Multiple options are separated using the `separate_arguments` function, which converts any string using space-separated arguments into a semicolon-separated list.
2021-06-19 11:22:31 +02:00
set(PUGIXML_BUILD_DEFINES CACHE STRING "Build defines for custom options")
separate_arguments(PUGIXML_BUILD_DEFINES)
Re-introduced the custom build defines The ability to use custom build defines were removed in commit: 1c5a0bb32583fd294022e68e66b541bf6ff71a67 This commit will reintroduce this feature, but using a prefixed variable name.
2021-06-15 09:00:31 +02:00
Reverted to use of global BUILD_SHARED_LIBS option This commit reverts back to exposing the global variable BUILD_SHARED_LIBS. Since building static libraries are the default for CMake (i.e. BUILD_SHARED_LIBS=OFF) the option to build both static and shared libraries were moved into a conditional option. So the option PUGIXML_BUILD_SHARED_AND_STATIC is now only visible when the global BUILD_SHARED_LIBS variable is set to ON. The change also prevents the case were the user first enables BUILD_SHARED_LIBS and then enables PUGIXML_BUILD_SHARED_AND_STATIC to then again disable BUILD_SHARED_LIBS.
2021-06-19 12:51:27 +02:00
# Technically not needed for this file. This is builtin CMAKE global variable.
Auto-detect std::string_view support by default Instead of opting in std::string_view support via PUGIXML_STRING_VIEW define, always enable it when C++17 is supported; this still requires enabling C++17 support in the compiler, which this change doesn't attempt to do yet.
2024-10-30 10:31:49 -07:00
option(BUILD_SHARED_LIBS "Build shared instead of static library" OFF)
Reverted to use of global BUILD_SHARED_LIBS option This commit reverts back to exposing the global variable BUILD_SHARED_LIBS. Since building static libraries are the default for CMake (i.e. BUILD_SHARED_LIBS=OFF) the option to build both static and shared libraries were moved into a conditional option. So the option PUGIXML_BUILD_SHARED_AND_STATIC is now only visible when the global BUILD_SHARED_LIBS variable is set to ON. The change also prevents the case were the user first enables BUILD_SHARED_LIBS and then enables PUGIXML_BUILD_SHARED_AND_STATIC to then again disable BUILD_SHARED_LIBS.
2021-06-19 12:51:27 +02:00
# Expose option to build PUGIXML as static as well when the global BUILD_SHARED_LIBS variable is set
cmake_dependent_option(PUGIXML_BUILD_SHARED_AND_STATIC_LIBS
"Build both shared and static libraries" OFF
"BUILD_SHARED_LIBS" OFF)
Update version to 1.12
2022-02-08 19:56:41 -08:00
Add options to build targets Add custom options to the build targets via generator expressions.
2021-06-26 23:16:24 +02:00
# Expose options from the pugiconfig.hpp
Add Cmake options for pugiconfig.hpp Add Cmake options variables for each of the defines in pugiconfig.hpp.
2021-06-23 11:05:34 +02:00
option(PUGIXML_WCHAR_MODE "Enable wchar_t mode" OFF)
option(PUGIXML_COMPACT "Enable compact mode" OFF)
Added cmake option to disable install rules
2023-10-12 02:05:35 +04:00
option(PUGIXML_INSTALL "Enable installation rules" ON)
Add Cmake options for pugiconfig.hpp Add Cmake options variables for each of the defines in pugiconfig.hpp.
2021-06-23 11:05:34 +02:00
Add options to build targets Add custom options to the build targets via generator expressions.
2021-06-26 23:16:24 +02:00
# Advanced options from pugiconfig.hpp
Add Cmake options for pugiconfig.hpp Add Cmake options variables for each of the defines in pugiconfig.hpp.
2021-06-23 11:05:34 +02:00
option(PUGIXML_NO_XPATH "Disable XPath" OFF)
option(PUGIXML_NO_STL "Disable STL" OFF)
option(PUGIXML_NO_EXCEPTIONS "Disable Exceptions" OFF)
Auto-detect std::string_view support by default Instead of opting in std::string_view support via PUGIXML_STRING_VIEW define, always enable it when C++17 is supported; this still requires enabling C++17 support in the compiler, which this change doesn't attempt to do yet.
2024-10-30 10:31:49 -07:00
mark_as_advanced(PUGIXML_NO_XPATH PUGIXML_NO_STL PUGIXML_NO_EXCEPTIONS)
Add Cmake options for pugiconfig.hpp Add Cmake options variables for each of the defines in pugiconfig.hpp.
2021-06-23 11:05:34 +02:00
Store definitions in variable to avoid duplication Store compile definitions in variable to avoid duplicated generator expressions.
2021-06-28 19:51:20 +02:00
set(PUGIXML_PUBLIC_DEFINITIONS
$<$<BOOL:${PUGIXML_WCHAR_MODE}>:PUGIXML_WCHAR_MODE>
$<$<BOOL:${PUGIXML_COMPACT}>:PUGIXML_COMPACT>
$<$<BOOL:${PUGIXML_NO_XPATH}>:PUGIXML_NO_XPATH>
$<$<BOOL:${PUGIXML_NO_STL}>:PUGIXML_NO_STL>
Initial support for std::string_view (#633) When PUGIXML_STRING_VIEW define is set and C++17 is available, add std::string_view support to a few functions. In the future, string view support will be enabled without the need for an extra define, but for now the support is opt-in to reduce compatibility risks. PR is based on initial contribution by @brandl-muc.
2024-10-22 13:31:54 -07:00
$<$<BOOL:${PUGIXML_NO_EXCEPTIONS}>:PUGIXML_NO_EXCEPTIONS>
)
Store definitions in variable to avoid duplication Store compile definitions in variable to avoid duplicated generator expressions.
2021-06-28 19:51:20 +02:00
Adjust MSVC runtime settings as requested. The block of code can be removed in the future if CMake 3.15 ever becomes the minimum
2019-10-01 10:20:30 -07:00
# This is used to backport a CMake 3.15 feature, but is also forwards compatible
:construction: Begin moving pugixml to modern(ish) CMake :arrow_up: Bump CMake minimum to 3.4 :bug: pugixml no longer requires a C compiler to be found or set to compile correctly. This speeds up configuration and building on windows. :construction: Begin laying groundwork to backport MSVC_RUNTIME_LIBRARY property
2019-09-28 10:47:15 -07:00
if (NOT DEFINED CMAKE_MSVC_RUNTIME_LIBRARY)
set(CMAKE_MSVC_RUNTIME_LIBRARY
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
MultiThreaded$<$<CONFIG:Debug>:Debug>$<$<NOT:$<BOOL:${PUGIXML_STATIC_CRT}>>:DLL>)
:construction: Begin moving pugixml to modern(ish) CMake :arrow_up: Bump CMake minimum to 3.4 :bug: pugixml no longer requires a C compiler to be found or set to compile correctly. This speeds up configuration and building on windows. :construction: Begin laying groundwork to backport MSVC_RUNTIME_LIBRARY property
2019-09-28 10:47:15 -07:00
endif()
CMake now uses C++17 if supported by the compiler We only set this when C++ version or requirement flag is not overridden externally to be able to rely on CMake automatically downgrading the standard version when the compiler doesn't support it. CXX_STANDARD 17 also requires CMake 3.8 or later; on earlier versions we use the old behavior and set C++11.
2024-10-30 12:02:30 -07:00
# Set the default C++ standard to C++17 if not set; CMake will automatically downgrade this if the compiler does not support it
# When CMAKE_CXX_STANDARD_REQUIRED is set, we fall back to C++11 to avoid breaking older compilers
if (NOT DEFINED CMAKE_CXX_STANDARD_REQUIRED AND NOT DEFINED CMAKE_CXX_STANDARD AND NOT CMAKE_VERSION VERSION_LESS 3.8)
cmake: set the minimum version before the project call
2018-01-18 10:43:05 -05:00
CMake now uses C++17 if supported by the compiler We only set this when C++ version or requirement flag is not overridden externally to be able to rely on CMake automatically downgrading the standard version when the compiler doesn't support it. CXX_STANDARD 17 also requires CMake 3.8 or later; on earlier versions we use the old behavior and set C++11.
2024-10-30 12:02:30 -07:00
set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED OFF)
elseif (NOT DEFINED CMAKE_CXX_STANDARD)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
set(CMAKE_CXX_STANDARD 11)
Add: Windows DLL version info header (#298) Closes #294
2019-09-19 16:27:40 +02:00
endif()
Set svn:eol-style to native for all text files git-svn-id: http://pugixml.googlecode.com/svn/trunk@607 99668b35-9821-0410-8761-19e4c4f06640
2010-07-19 09:57:32 +00:00
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
if (PUGIXML_USE_POSTFIX)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
set(CMAKE_RELWITHDEBINFO_POSTFIX _r)
set(CMAKE_MINSIZEREL_POSTFIX _m)
set(CMAKE_DEBUG_POSTFIX _d)
Add BUILD_DEFINES parameter to CMakeLists.txt git-svn-id: https://pugixml.googlecode.com/svn/trunk@1000 99668b35-9821-0410-8761-19e4c4f06640
2014-07-28 16:08:43 +00:00
endif()
Adjust MSVC runtime settings as requested. The block of code can be removed in the future if CMake 3.15 ever becomes the minimum
2019-10-01 10:20:30 -07:00
if (CMAKE_VERSION VERSION_LESS 3.15)
set(msvc-rt $<TARGET_PROPERTY:MSVC_RUNTIME_LIBRARY>)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Adjust MSVC runtime settings as requested. The block of code can be removed in the future if CMake 3.15 ever becomes the minimum
2019-10-01 10:20:30 -07:00
set(msvc-rt-mtd-shared $<STREQUAL:${msvc-rt},MultiThreadedDebugDLL>)
set(msvc-rt-mtd-static $<STREQUAL:${msvc-rt},MultiThreadedDebug>)
set(msvc-rt-mt-shared $<STREQUAL:${msvc-rt},MultiThreadedDLL>)
set(msvc-rt-mt-static $<STREQUAL:${msvc-rt},MultiThreaded>)
unset(msvc-rt)
set(msvc-rt-mtd-shared $<${msvc-rt-mtd-shared}:-MDd>)
set(msvc-rt-mtd-static $<${msvc-rt-mtd-static}:-MTd>)
set(msvc-rt-mt-shared $<${msvc-rt-mt-shared}:-MD>)
set(msvc-rt-mt-static $<${msvc-rt-mt-static}:-MT>)
endif()
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
set(versioned-dir $<$<BOOL:${PUGIXML_USE_VERSIONED_LIBDIR}>:/pugixml-${PROJECT_VERSION}>)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
set(libs)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Reverted to use of global BUILD_SHARED_LIBS option This commit reverts back to exposing the global variable BUILD_SHARED_LIBS. Since building static libraries are the default for CMake (i.e. BUILD_SHARED_LIBS=OFF) the option to build both static and shared libraries were moved into a conditional option. So the option PUGIXML_BUILD_SHARED_AND_STATIC is now only visible when the global BUILD_SHARED_LIBS variable is set to ON. The change also prevents the case were the user first enables BUILD_SHARED_LIBS and then enables PUGIXML_BUILD_SHARED_AND_STATIC to then again disable BUILD_SHARED_LIBS.
2021-06-19 12:51:27 +02:00
if (BUILD_SHARED_LIBS)
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
add_library(pugixml-shared SHARED
${PROJECT_SOURCE_DIR}/scripts/pugixml_dll.rc
${PROJECT_SOURCE_DIR}/src/pugixml.cpp)
add_library(pugixml::shared ALIAS pugixml-shared)
list(APPEND libs pugixml-shared)
Fix exported symbols under clang-cl (Closes #503) This also turns the define for PUGIXML_API into an `$<IF:>`, instead of an `$<IF:>` with an empty true condition. If this is inadequate, I will undo it, and place them on separate lines as they were before, but will most likely use an inverse `$<NOT:>` instead of an `$<IF:>`.
2022-10-20 13:35:04 -07:00
string(CONCAT pugixml.msvc $<OR:
$<STREQUAL:${CMAKE_CXX_COMPILER_FRONTEND_VARIANT},MSVC>,
$<CXX_COMPILER_ID:MSVC>
>)
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
set_property(TARGET pugixml-shared PROPERTY EXPORT_NAME shared)
target_include_directories(pugixml-shared
PUBLIC
$<BUILD_INTERFACE:${PROJECT_SOURCE_DIR}/src>)
target_compile_definitions(pugixml-shared
Make some compile definitions public Moved needed defines to public section of target_compile_definitions.
2021-06-28 13:36:55 +02:00
PUBLIC
Move advanced memory settings into target defs. Moved the advanced memory options into target_compile_definitions using generator expressions.
2021-06-28 12:41:11 +02:00
${PUGIXML_BUILD_DEFINES}
Store definitions in variable to avoid duplication Store compile definitions in variable to avoid duplicated generator expressions.
2021-06-28 19:51:20 +02:00
${PUGIXML_PUBLIC_DEFINITIONS}
Make some compile definitions public Moved needed defines to public section of target_compile_definitions.
2021-06-28 13:36:55 +02:00
PRIVATE
Fix exported symbols under clang-cl (Closes #503) This also turns the define for PUGIXML_API into an `$<IF:>`, instead of an `$<IF:>` with an empty true condition. If this is inadequate, I will undo it, and place them on separate lines as they were before, but will most likely use an inverse `$<NOT:>` instead of an `$<IF:>`.
2022-10-20 13:35:04 -07:00
PUGIXML_API=$<IF:${pugixml.msvc},__declspec\(dllexport\),__attribute__\(\(visibility\("default"\)\)\)>
Correctly set default visibility on non-windows compilers This fixes compilation of pugixml with -fvisibility=hidden. Without this patch, one would get lots of unresolved symbols when consuming pugixml as a shared library.
2022-04-20 13:00:41 +02:00
)
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
target_compile_options(pugixml-shared
PRIVATE
${msvc-rt-mtd-shared}
${msvc-rt-mtd-static}
${msvc-rt-mt-shared}
${msvc-rt-mt-static})
endif()
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Reverted to use of global BUILD_SHARED_LIBS option This commit reverts back to exposing the global variable BUILD_SHARED_LIBS. Since building static libraries are the default for CMake (i.e. BUILD_SHARED_LIBS=OFF) the option to build both static and shared libraries were moved into a conditional option. So the option PUGIXML_BUILD_SHARED_AND_STATIC is now only visible when the global BUILD_SHARED_LIBS variable is set to ON. The change also prevents the case were the user first enables BUILD_SHARED_LIBS and then enables PUGIXML_BUILD_SHARED_AND_STATIC to then again disable BUILD_SHARED_LIBS.
2021-06-19 12:51:27 +02:00
if (NOT BUILD_SHARED_LIBS OR PUGIXML_BUILD_SHARED_AND_STATIC_LIBS)
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
add_library(pugixml-static STATIC
${PROJECT_SOURCE_DIR}/src/pugixml.cpp)
add_library(pugixml::static ALIAS pugixml-static)
list(APPEND libs pugixml-static)
set_property(TARGET pugixml-static PROPERTY EXPORT_NAME static)
target_include_directories(pugixml-static
PUBLIC
$<BUILD_INTERFACE:${PROJECT_SOURCE_DIR}/src>)
Move advanced memory settings into target defs. Moved the advanced memory options into target_compile_definitions using generator expressions.
2021-06-28 12:41:11 +02:00
target_compile_definitions(pugixml-static
Make some compile definitions public Moved needed defines to public section of target_compile_definitions.
2021-06-28 13:36:55 +02:00
PUBLIC
Move advanced memory settings into target defs. Moved the advanced memory options into target_compile_definitions using generator expressions.
2021-06-28 12:41:11 +02:00
${PUGIXML_BUILD_DEFINES}
Update CMakeLists.txt Remove memory configuration options and rely on automatic detection of long long
2021-08-07 09:51:54 -07:00
${PUGIXML_PUBLIC_DEFINITIONS})
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
target_compile_options(pugixml-static
PRIVATE
${msvc-rt-mtd-shared}
${msvc-rt-mtd-static}
${msvc-rt-mt-shared}
${msvc-rt-mt-static})
endif()
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Reverted to use of global BUILD_SHARED_LIBS option This commit reverts back to exposing the global variable BUILD_SHARED_LIBS. Since building static libraries are the default for CMake (i.e. BUILD_SHARED_LIBS=OFF) the option to build both static and shared libraries were moved into a conditional option. So the option PUGIXML_BUILD_SHARED_AND_STATIC is now only visible when the global BUILD_SHARED_LIBS variable is set to ON. The change also prevents the case were the user first enables BUILD_SHARED_LIBS and then enables PUGIXML_BUILD_SHARED_AND_STATIC to then again disable BUILD_SHARED_LIBS.
2021-06-19 12:51:27 +02:00
if (BUILD_SHARED_LIBS)
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
set(pugixml-alias pugixml-shared)
else()
set(pugixml-alias pugixml-static)
endif()
add_library(pugixml INTERFACE)
target_link_libraries(pugixml INTERFACE ${pugixml-alias})
add_library(pugixml::pugixml ALIAS pugixml)
set_target_properties(${libs}
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
PROPERTIES
MSVC_RUNTIME_LIBRARY ${CMAKE_MSVC_RUNTIME_LIBRARY}
EXCLUDE_FROM_ALL ON
Add POSITION_INDEPENDENT_CODE option Allow to use the static library in other dynamic librairies. This is a standard cmake option https://cmake.org/cmake/help/v3.11/prop_tgt/POSITION_INDEPENDENT_CODE.html#prop_tgt:POSITION_INDEPENDENT_CODE
2019-12-06 17:25:37 +01:00
POSITION_INDEPENDENT_CODE ON
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
SOVERSION ${PROJECT_VERSION_MAJOR}
Update CMakeLists.txt to rename the static and shared libraries to pugixml Don't call them pugixml-shared or pugixml-static, because this breaks pkgconfig calls and userspace tools.
2020-02-07 14:55:25 +01:00
VERSION ${PROJECT_VERSION}
OUTPUT_NAME pugixml)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
set_target_properties(${libs}
PROPERTIES
EXCLUDE_FROM_ALL OFF)
set(install-targets pugixml ${libs})
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
configure_package_config_file(
Update `check` command to output text on failure Move pugixml-config.cmake.in to scripts/ to prevent polluting the root
2019-09-30 22:00:04 -07:00
"${PROJECT_SOURCE_DIR}/scripts/pugixml-config.cmake.in"
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
"${PROJECT_BINARY_DIR}/pugixml-config.cmake"
:bug: Fix incorrect installation location for exported CMake targets
2019-10-17 21:44:48 -07:00
INSTALL_DESTINATION ${CMAKE_INSTALL_LIBDIR}
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
NO_CHECK_REQUIRED_COMPONENTS_MACRO
NO_SET_AND_CHECK_MACRO)
write_basic_package_version_file(
"${PROJECT_BINARY_DIR}/pugixml-config-version.cmake"
COMPATIBILITY SameMajorVersion)
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
if (PUGIXML_USE_POSTFIX)
Fix debug postfix in pkgconfig file In case of USE_POSTFIX, the POSTFIX is dependent on the CMAKE_BUILD_TYPE. Use the correct POSTFIX also in the generated pugixml.pc file. This results in the following contents of pugixml.pc: - Release: Libs: -L${libdir} -lpugixml - RelWithDebInfo Libs: -L${libdir} -lpugixml_r - MinSizeRel: Libs: -L${libdir} -lpugixml_m - Debug: Libs: -L${libdir} -lpugixml_d
2020-07-15 21:59:05 +02:00
if(CMAKE_BUILD_TYPE MATCHES RelWithDebInfo)
set(LIB_POSTFIX ${CMAKE_RELWITHDEBINFO_POSTFIX})
elseif(CMAKE_BUILD_TYPE MATCHES MinSizeRel)
set(LIB_POSTFIX ${CMAKE_MINSIZEREL_POSTFIX})
elseif(CMAKE_BUILD_TYPE MATCHES Debug)
set(LIB_POSTFIX ${CMAKE_DEBUG_POSTFIX})
endif()
endif()
Relative and absolute paths for a relocatable pkgconf file
2024-03-22 14:05:43 +01:00
# Handle both relative and absolute paths (e.g. NixOS) for a relocatable package
if(IS_ABSOLUTE "${CMAKE_INSTALL_INCLUDEDIR}")
set(PUGIXML_PC_INCLUDEDIR "${CMAKE_INSTALL_INCLUDEDIR}")
else()
set(PUGIXML_PC_INCLUDEDIR "\${prefix}/${CMAKE_INSTALL_INCLUDEDIR}")
endif()
if(IS_ABSOLUTE "${CMAKE_INSTALL_LIBDIR}")
set(PUGIXML_PC_LIBDIR "${CMAKE_INSTALL_LIBDIR}")
else()
set(PUGIXML_PC_LIBDIR "\${exec_prefix}/${CMAKE_INSTALL_LIBDIR}")
endif()
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
configure_file(scripts/pugixml.pc.in pugixml.pc @ONLY)
Added cmake option to disable install rules
2023-10-12 02:05:35 +04:00
export(TARGETS ${install-targets}
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
NAMESPACE pugixml::
Added cmake option to disable install rules
2023-10-12 02:05:35 +04:00
FILE pugixml-targets.cmake)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Added cmake option to disable install rules
2023-10-12 02:05:35 +04:00
if(PUGIXML_INSTALL)
if (NOT DEFINED PUGIXML_RUNTIME_COMPONENT)
set(PUGIXML_RUNTIME_COMPONENT Runtime)
endif()
Export targets from build directory This will allow projects to use pugixml from its build directory rather than having to install it.
2020-04-27 16:02:56 -04:00
Added cmake option to disable install rules
2023-10-12 02:05:35 +04:00
if (NOT DEFINED PUGIXML_LIBRARY_COMPONENT)
set(PUGIXML_LIBRARY_COMPONENT Library)
endif()
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Added cmake option to disable install rules
2023-10-12 02:05:35 +04:00
if (NOT DEFINED PUGIXML_DEVELOPMENT_COMPONENT)
set(PUGIXML_DEVELOPMENT_COMPONENT Development)
endif()
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Added cmake option to disable install rules
2023-10-12 02:05:35 +04:00
set(namelink-component)
if (NOT CMAKE_VERSION VERSION_LESS 3.12)
set(namelink-component NAMELINK_COMPONENT ${PUGIXML_DEVELOPMENT_COMPONENT})
endif()
install(TARGETS ${install-targets}
EXPORT pugixml-targets
RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR} COMPONENT ${PUGIXML_RUNTIME_COMPONENT}
LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} COMPONENT ${PUGIXML_LIBRARY_COMPONENT} ${namelink-component}
ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR} COMPONENT ${PUGIXML_DEVELOPMENT_COMPONENT}
INCLUDES DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}${versioned-dir})
install(EXPORT pugixml-targets
NAMESPACE pugixml::
DESTINATION ${CMAKE_INSTALL_LIBDIR}/cmake/pugixml COMPONENT ${PUGIXML_DEVELOPMENT_COMPONENT})
install(FILES
"${PROJECT_BINARY_DIR}/pugixml-config-version.cmake"
"${PROJECT_BINARY_DIR}/pugixml-config.cmake"
DESTINATION ${CMAKE_INSTALL_LIBDIR}/cmake/pugixml COMPONENT ${PUGIXML_DEVELOPMENT_COMPONENT})
install(FILES ${PROJECT_BINARY_DIR}/pugixml.pc
DESTINATION ${CMAKE_INSTALL_LIBDIR}/pkgconfig COMPONENT ${PUGIXML_DEVELOPMENT_COMPONENT})
install(
FILES
"${PROJECT_SOURCE_DIR}/src/pugiconfig.hpp"
"${PROJECT_SOURCE_DIR}/src/pugixml.hpp"
DESTINATION
${CMAKE_INSTALL_INCLUDEDIR}${versioned-dir} COMPONENT ${PUGIXML_DEVELOPMENT_COMPONENT})
endif()
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
Add PUGIXML as prefix to CMake options Added PUGIXML as prefix to all CMake options to avoid naming collisions with downstream projects. Removed the cached variable BUILD_DEFINES, since it was unused.
2021-01-11 16:13:52 +01:00
if (PUGIXML_BUILD_TESTS)
Only include CTest when building the pugixml tests
2023-10-06 09:51:29 +02:00
include(CTest)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
set(fuzz-pattern "tests/fuzz_*.cpp")
set(test-pattern "tests/*.cpp")
if (CMAKE_VERSION VERSION_GREATER 3.11)
list(INSERT fuzz-pattern 0 CONFIGURE_DEPENDS)
list(INSERT test-pattern 0 CONFIGURE_DEPENDS)
make pugixml build static and shared via cmake (#257)
2019-02-06 16:39:23 +01:00
endif()
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
file(GLOB test-sources ${test-pattern})
file(GLOB fuzz-sources ${fuzz-pattern})
list(REMOVE_ITEM test-sources ${fuzz-sources})
Update `check` command to output text on failure Move pugixml-config.cmake.in to scripts/ to prevent polluting the root
2019-09-30 22:00:04 -07:00
add_custom_target(check
COMMAND ${CMAKE_CTEST_COMMAND} --output-on-failure)
:sparkles: Update CMake to modern approach New Features: pugixml-shared and pugixml-static are "always" available, but not always built. This allows downstream projects to still use them, and to make sure our configurations are correct regardless of if they are being built. They are not always installed however. pugixml-shared and pugixml-static have ALIAS libraries of pugixml::shared and pugixml::static respectively. These names are also respected in the `find_package(pugixml CONFIG)` generated files, so its safe to use pugixml in a CMake project regardless of whether it is installed locally, or if its a subproject via `add_subdirectory`. pugixml will automatically select the correct library type based on BUILD_SHARED_LIBS. A pugixml::pugixml ALIAS is also available. CMAKE_MSVC_RUNTIME_LIBRARY from CMake 3.15 has been backported. CMake will now rely on generator expressions (a powerful abstraction in large projects with many subdirectories) for most work. This offloads work from the single-threaded configure stage to the multithreaded generation stage. pugixml now uses CTest as the runner. Some settings are automatically disabled if pugixml is used as a subdirectory. These are still able to be manually set, but are hidden from folks who choose to use CMake GUI.
2019-09-28 13:02:55 -07:00
add_executable(pugixml-check ${test-sources})
add_test(NAME pugixml::test
COMMAND pugixml-check
WORKING_DIRECTORY ${PROJECT_SOURCE_DIR})
add_dependencies(check pugixml-check)
target_link_libraries(pugixml-check
PRIVATE
Fix multiple-rules-for-target error The old logic for BUILD_SHARED_LIBS and BUILD_SHARED_AND_STATIC_LIBS would produce two targets with the same name and different build rules. The Makefile generator tolerated this, but the Ninja generator raised an error. Fix the logic so that only one shared and one static target gets built, and make the pugixml target an ALIAS of the one dictated by BUILD_SHARED_LIBS.
2020-04-27 13:26:37 -04:00
pugixml::pugixml)
scripts: Added BUILD_SHARED_LIBS option to CMakeLists.txt for building pugixml as a shared library. Fixes issue 113. git-svn-id: http://pugixml.googlecode.com/svn/trunk@812 99668b35-9821-0410-8761-19e4c4f06640
2011-07-20 04:21:49 +00:00
endif()
Reference in New Issue Copy Permalink