Re: [ITA] p11-kit NMU upgrade from 0.23.20 to 0.26.2 test
Jon Turney via Cygwin-apps <[email protected]> Thu, 12 Feb 2026 13:38:43 +0000
| Newsgroups | gmane.os.cygwin.applications |
|---|---|
| Message-ID | <[email protected]> |
On 11/02/2026 18:04, Brian Inglis via Cygwin-apps wrote:
> Hi folks,
>
> I would like to adopt p11-kit orphaned security package.
>
> I built an NMU test upgrade to the latest release in playground and in
> GH Scallywag CI, and it passes most tests.
>
> An intermediate release changed the build system from autotools to
> meson/ninja/cmake which made the upgrade interesting. ;^>
>
> The meson build created interface .DLLs instead of .SOs, except for the
> library .so, which was symlinked as ...bin/cygp11-kit-0.dll as before,
> although there is now a $S/$NAME/meson_post_install.sh to do so in the
> DESTDIR $D.
>
> That script takes a libdir arg, so is there any reason or some way to
> handle that as a postinstall script for libp11-kit0
>
> Another difference I noticed was that the build dir was
>
> $S/_build.$ARCH-pc-cygwin
>
> from which I did a lndirs into $B after meson-install, just in case it
> affected cygport processing.
> It would be good if we could persuade meson/ninja/cmake to use $B as usual.
Yeah, it would be nice if meson.cygclass used ${B} like everything else.
If I recall correctly, using that directory is a workaround to get the
form of paths that meson ends up writing into the ninja.build rules
(absolute? relative?) to interact correctly with the -ffile-prefix-map
option.
There's a few discussions on the topic in the archives here.
PTC, obviously.
> Any advice or feedback from experience with meson builds would be useful.