[kdreports] new port

[drdanz]

• Changes comply with the maintainer guide.
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[jimwang118]

I got the following error when testing usage locally.

Severity	Code	Description	Project	File	Line	Suppression State	Details
Error		CMake Error at F:/kdp/scripts/buildsystems/vcpkg.cmake:859 (_find_package):
  By not providing "FindQtCore.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "QtCore", but
  CMake did not find one.

  Could not find a package configuration file provided by "QtCore" (requested
  version 6.0.0) with any of the following names:

    QtCoreConfig.cmake
    qtcore-config.cmake

  Add the installation prefix of "QtCore" to CMAKE_PREFIX_PATH or set
  "QtCore_DIR" to a directory containing one of the above files.  If "QtCore"
  provides a separate development package or SDK, be sure it has been
  installed.		F:/kdp/scripts/buildsystems/vcpkg.cmake	859		

[drdanz]

  Could not find a package configuration file provided by "QtCore" (requested
  version 6.0.0) with any of the following names:

    QtCoreConfig.cmake
    qtcore-config.cmake

That's weird, QtCoreConfig.cmake should be in the qtbase package, which is an explicit dependency, and it is normally found automatically (I don't see any other port doing anything strange to find Qt6). I tried adding an explicit dependency on the widget component, perhaps that was the problem since I set "default-features": false. @jimwang118 Could you please try again?

[jimwang118]

That's weird, QtCoreConfig.cmake should be in the qtbase package, which is an explicit dependency, and it is normally found automatically (I don't see any other port doing anything strange to find Qt6). I tried adding an explicit dependency on the widget component, perhaps that was the problem since I set "default-features": false. @jimwang118 Could you please try again?

Still reporting the same error.

[dg0yt]

The documented CMake usage for Qt6 is:

find_package(Qt6 REQUIRED COMPONENTS Core)

https://doc.qt.io/qt-6/cmake-get-started.html

This is what is supported in vcpkg.

[drdanz]

The documented CMake usage for Qt6 is:

find_package(Qt6 REQUIRED COMPONENTS Core)

https://doc.qt.io/qt-6/cmake-get-started.html

This is what is supported in vcpkg.

This is what the package is already doing, see https://github.com/KDAB/KDReports/blob/master/CMakeLists.txt#L118
It looks more like a problem in Qt6 port than in this... @jimwang118 Perhaps you are building on some untested platform/triplet? CI is passing on all tested platforms... Can you tell me what architecture are you building on, so that I can try reproducing it? Thanks

[jimwang118]

I just created a cmake project on VS, and then called usage to compile it, and the above problem was reported.

[iamsergio]

I just created a cmake project on VS, and then called usage to compile it, and the above problem was reported.

Does kdsoap work for you ? It's an existing port which is similar to kdreports

[jimwang118]

Does kdsoap work for you ? It's an existing port which is similar to kdreports

The kdsoap test is normal and can be used.

[drdanz]

Found the bug, it should be fixed now, I'll fix it upstream as well

---

Edit: bug is already fixed in latest master

[dg0yt]

You found the typo in the right file now.

I still think that dependency lookup up in the project and in the exported config should follow the same pattern, i.e.

find_package(Qt6 ${QT_MIN_VERSION} CONFIG REQUIRED COMPONENTS Core Widgets PrintSupport Xml)

should be paired with

find_dependency(Qt6 @QT_MIN_VERSION@ CONFIG COMPONENTS Core Widgets PrintSupport Xml)

which maps to exactly the same config lookup and targets, instead of requesting a different set of packages.
(Note that find_dependency is not to be used with REQUIRED.)

[jimwang118]

Usage test passed with x64-windows triplet.