Hello all,

On Sun, Sep 01, 2024 at 11:43:42PM +0200, Enrique Garcia wrote:
> [...]
> Interestingly, the cmake-based build _also_ creates the pkg-config
> configuration file, so I think that an easy way to solve the issue is to use
> cmake to build the Debian package, which hopefully won't introduce any
> regression since the already provided pgk-config file would still be 
> installed.

JFTR, it seems while building with cmake is indeed possible, there are
some upstream glitches that still need resolving, cf.

Exported symbols aren't consistent #715
https://github.com/akheron/jansson/issues/715
(various fixes suggested)

whereas some other things apparently were fixed already, but only in
newer versions than currently present in Debian, cf.

JSON_INTEGER_IS_LONG_LONG is part of API but it differs between cmake &
autotools (2.14) #696
https://github.com/akheron/jansson/issues/696
(resolved with 2.14.1)

Refactor tests to work better with CMake
https://github.com/akheron/jansson/commit/88375fb10ee775d0c07edd8394d09de34b7ebec3
(resolved with 2.14.1)

Use target-based cmake settings
https://github.com/akheron/jansson/commit/0f9c18dd1264704b55f41644aecbabf2567a9723
(resolved with 2.15.0)

Set minimum cmake version to 3.10
https://github.com/akheron/jansson/commit/aef13f87f18efec7c2a543045301602af6177a83
(resolved with 2.15.0)

cmake build with FetchContent
https://github.com/akheron/jansson/issues/724
(resolved with 2.15.0)

so switching to building with cmake first requires the new upstream
versions and then some more care.

On Sun, Apr 26, 2026 at 01:50:40PM +0200, David Heidelberg wrote:
> [...]
> Also I couldn't notice that package seems to abandoned.

JFTR, there exists https://bugs.debian.org/1130860 for handling that.

HTH,
Flo

Attachment: signature.asc
Description: PGP signature

Reply via email to