Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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 Doug Newgard (Scimmia) - Sunday, 07 October 2018, 22:33 GMT
Task Type Feature Request
Category Packages: Extra
Status Assigned
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

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

Comment by Peter Spiess-Knafl (cinemast) - Monday, 12 November 2018, 08:36 GMT
Is there anything I can help with?
Comment by Eli Schwartz (eschwartz) - Tuesday, 13 November 2018, 01:45 GMT
Why?

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.)
Comment by Adam (catch22) - Friday, 24 July 2020, 21:35 GMT
+1 vote for including the cmake package

Loading...