Install pkgconfig and cmake files into arch-dependent locations#1055
Merged
jbeder merged 1 commit intojbeder:masterfrom Sep 20, 2022
tgurr:arch
Merged
Install pkgconfig and cmake files into arch-dependent locations#1055jbeder merged 1 commit intojbeder:masterfrom tgurr:arch
jbeder merged 1 commit intojbeder:masterfrom
tgurr:arch
Conversation
Owner
|
This sounds reasonable to me, but I've been bitten quite a bit lately by approving CMake changes I don't understand. Could you add a clause to the github action here that tests the behavior you'd like to see? That way it'll guarantee that the behavior you want is preserved even if people later update the CMake file. |
Contributor
Author
|
Thanks for the suggestion, however I'm not familiar with GitHub Actions and/or writing any tests so I'll most likely not being able to help with or contribute anything in this regard. |
felix2010
added a commit
to felix2010/yaml-cpp
that referenced
this pull request
Dec 30, 2021
After configure the file `yaml-cpp-config.cmake.in` the result ends up with empty variables. (see also the discussion in jbeder#774). Rework this file and the call to `configure_package_config_file` according the cmake documentation (https://cmake.org/cmake/help/v3.22/module/CMakePackageConfigHelpers.html?highlight=configure_package_config#command:configure_package_config_file) to overcome this issue and allow a simple `find_package` after install. As there was same discussion about the place where to install the `yaml-cpp-config.cmake` file, e.g. jbeder#1055, factor out the install location into an extra variable to make it easier changing this location in the future.
felix2010
added a commit
to felix2010/yaml-cpp
that referenced
this pull request
Dec 30, 2021
After configure the file `yaml-cpp-config.cmake.in` the result ends up with empty variables. (see also the discussion in jbeder#774). Rework this file and the call to `configure_package_config_file` according the cmake documentation (https://cmake.org/cmake/help/v3.22/module/CMakePackageConfigHelpers.html?highlight=configure_package_config#command:configure_package_config_file) to overcome this issue and allow a simple `find_package` after install. As there was same discussion about the place where to install the `yaml-cpp-config.cmake` file, e.g. jbeder#1055, factor out the install location into an extra variable to make it easier changing this location in the future.
felix2010
added a commit
to felix2010/yaml-cpp
that referenced
this pull request
Dec 30, 2021
After configure the file `yaml-cpp-config.cmake.in` the result ends up with empty variables. (see also the discussion in jbeder#774). Rework this file and the call to `configure_package_config_file` according the cmake documentation (https://cmake.org/cmake/help/v3.22/module/CMakePackageConfigHelpers.html?highlight=configure_package_config#command:configure_package_config_file) to overcome this issue and allow a simple `find_package` after install. As there was some discussion about the place where to install the `yaml-cpp-config.cmake` file, e.g. jbeder#1055, factor out the install location into an extra variable to make it easier changing this location in the future.
jbeder
pushed a commit
that referenced
this pull request
Apr 1, 2022
After configuring the file `yaml-cpp-config.cmake.in`, the result ends up with empty variables. (see also the discussion in #774). Rework this file and the call to `configure_package_config_file` according the cmake documentation (https://cmake.org/cmake/help/v3.22/module/CMakePackageConfigHelpers.html?highlight=configure_package_config#command:configure_package_config_file) to overcome this issue and allow a simple `find_package` after install. As there was some discussion about the place where to install the `yaml-cpp-config.cmake` file, e.g. #1055, factor out the install location into an extra variable to make it easier changing this location in the future. Also untabify CMakeLists.txt in some places to align with the other code parts in this file.
Contributor
Author
|
See also #1020. |
Owner
|
You know what, this is fine; if it breaks someone's build then I guess I can ask them to write a test. |
davemccann
pushed a commit
to davemccann/yaml-cpp
that referenced
this pull request
Jul 30, 2023
After configuring the file `yaml-cpp-config.cmake.in`, the result ends up with empty variables. (see also the discussion in jbeder#774). Rework this file and the call to `configure_package_config_file` according the cmake documentation (https://cmake.org/cmake/help/v3.22/module/CMakePackageConfigHelpers.html?highlight=configure_package_config#command:configure_package_config_file) to overcome this issue and allow a simple `find_package` after install. As there was some discussion about the place where to install the `yaml-cpp-config.cmake` file, e.g. jbeder#1055, factor out the install location into an extra variable to make it easier changing this location in the future. Also untabify CMakeLists.txt in some places to align with the other code parts in this file.
davemccann
pushed a commit
to davemccann/yaml-cpp
that referenced
this pull request
Jul 30, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This restores the CMake / installed files behaviour of version 0.6.3 which changed in 0.7.0, resulting in arch-dependent files ending up in /usr/share instead of $prefix/libdir. This is required on multiarch/cross layouts setting the prefix to e.g.
/usr/x86_64-pc-linux-gnuor/usr/i686-pc-linux-gnuso a pkg-config file in /usr/share likewould be wrong as it contains arch-specific code.