FS#60285 - [jsoncpp] add cmake config file
Attached to Project:
Arch Linux
Opened by Michel (xantares) - Tuesday, 02 October 2018, 20:05 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:24 GMT
Opened by Michel (xantares) - Tuesday, 02 October 2018, 20:05 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:24 GMT
|
Details
Could the package be compiled with cmake so as to provide
the cmake config file with
-DJSONCPP_WITH_CMAKE_PACKAGE=ON (defaults to ON only in master) ? |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:24 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/jsoncpp/issues/1
Saturday, 25 November 2023, 20:24 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/jsoncpp/issues/1
Upstream has deprecated the cmake build system with the note "(Deprecated, but still works for now. The version string may soon be wrong.)"
They prefer meson, and their primary build instructions are targeted at meson.
There's a pkg-config generated by default, which provides generic support for dependency calculations via any build system or even just by running pkg-config via the command line. Why do we need some cmake-specific file that can only be created by using a deprecated build system?
Why does cmake encourage the use of Not-In-House dependency configurations? Why can't cmake config files just die already?
(In case you cannot tell, I'm very biased.)
I checked Fedora and Ubuntu. They both provide the cmake config files.
Could you provide why some technical reason why cmake config files should just die already? (I'm interested)