FS#73540 - [waylandpp] Invalid CMake-package-config, in 0.2.8-1
Attached to Project:
Community Packages
Opened by John Eivind Helset (jehelset) - Friday, 28 January 2022, 12:30 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 17 May 2023, 04:34 GMT
Opened by John Eivind Helset (jehelset) - Friday, 28 January 2022, 12:30 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 17 May 2023, 04:34 GMT
|
Details
Description:
CMake-package-config of 0.2.8-1 has wrong include paths in it. See f.ex. waylandpp-targets.cmake:66. Steps to reproduce: Create a CMake-config, find_pacakge(waylandpp) |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 17 May 2023, 04:34 GMT
Reason for closing: None
Additional comments about closing: Doesn't seem like an Arch packaging problem. If still an issue, please report upstream
Wednesday, 17 May 2023, 04:34 GMT
Reason for closing: None
Additional comments about closing: Doesn't seem like an Arch packaging problem. If still an issue, please report upstream
"/build/waylandpp/src/waylandpp-0.2.9/;${_IMPORT_PREFIX}/include"
```
project(testwaylandpp)
find_package(waylandpp REQUIRED)
```
It does not complain, so that would mean it finds waylandpp just fine?
see: https://cmake.org/cmake/help/latest/manual/cmake-packages.7.html#creating-relocatable-packages
do you have an example project that uses waylandpp where it errors out? since I don't have any issue building kodi with this waylandpp package, but maybe they assume the libs to be present in /usr/include without the use of the find_package since I don't seem to see that in the kodi source
```
cmake_minimum_required(VERSION 3.22 FATAL_ERROR)
project(waylandapp LANGUAGES CXX)
find_package(waylandpp)
add_executable(executable executable.cpp)
target_link_libraries(executable PUBLIC Waylandpp::wayland-client++)
```
where `executable.cpp` is some dummy file, and with `cmake -S . -B build`:
```
CMake Error in CMakeLists.txt:
Imported target "Waylandpp::wayland-client++" includes non-existent path
"/build/waylandpp/src/waylandpp-0.2.8/"
in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:
* The path was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and references files it does not
provide.
```
typically i'd use pkgconfig if there was no CMake-package available (or the provided one doesn't work).