With Qt6 itself having switched to CMake, more and more projects building on Qt also follow that.
In CMake for finding dependencies it is most convenient to have CMake config files provided by the library.
While QHexEdit provides pkgconfig files and one can use them in some way within CMake-based builds, it comes with some bit of struggle. So CMake config files instead would be most convenient.
Perhaps QHexEdit might switch itself from qmake to cmake soon? Then providing CMake config files might be most simple.
With Qt6 itself having switched to CMake, more and more projects building on Qt also follow that.
In CMake for finding dependencies it is most convenient to have CMake config files provided by the library.
While QHexEdit provides pkgconfig files and one can use them in some way within CMake-based builds, it comes with some bit of struggle. So CMake config files instead would be most convenient.
Perhaps QHexEdit might switch itself from qmake to cmake soon? Then providing CMake config files might be most simple.