From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: 60586@debbugs.gnu.org
Subject: [bug#60586] [PATCH v2 0/2] Switch p11-kit-next to meson-build-system
Date: Fri, 6 Jan 2023 23:55:32 +0100 [thread overview]
Message-ID: <cover.1673045732.git.vivien@planete-kraus.eu> (raw)
In-Reply-To: <cover.1672961565.git.vivien@planete-kraus.eu>
Dear guix,
Upstream recommends to build with meson (see README.md), and it happens to
solve the mingw cross-compilation failure.
I had to isolate meson from the other build tools, because one of the package
in (gnu packages build-tools) depends on openssl, which is in (gnu packages
tls) like p11-kit. So, using the meson build system would be a circular
dependency.
Since now meson has quite a few public variables, I figured out it could go to
its own file.
I had to read the git log twice to make sure I got the correct copyright
notices (including dates) for both meson-related stuff and the other packages
in (gnu packages build-tools).
Vivien Kraus (2):
gnu: move meson to (gnu packages meson).
gnu: p11-kit-next: Switch to meson-build-system.
gnu/local.mk | 1 +
gnu/packages/build-tools.scm | 169 ++---------------------
gnu/packages/freedesktop.scm | 3 +-
gnu/packages/geo.scm | 1 +
gnu/packages/gnome.scm | 1 +
gnu/packages/meson.scm | 204 ++++++++++++++++++++++++++++
gnu/packages/package-management.scm | 1 +
gnu/packages/python-science.scm | 1 +
gnu/packages/syndication.scm | 1 +
gnu/packages/tls.scm | 7 +-
gnu/packages/virtualization.scm | 1 +
guix/build-system/meson.scm | 2 +-
12 files changed, 230 insertions(+), 162 deletions(-)
create mode 100644 gnu/packages/meson.scm
base-commit: cce9ff2d5ada3d1e26e1c70205f21271a0065482
--
2.38.1
next prev parent reply other threads:[~2023-01-06 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 23:32 [bug#60586] [PATCH 0/1] Fix p11-kit for mingw Vivien Kraus via Guix-patches via
2023-01-05 22:08 ` [bug#60586] [PATCH 1/1] gnu: p11-kit: Fix mingw cross-compilation Vivien Kraus via Guix-patches via
2023-01-06 22:55 ` Vivien Kraus via Guix-patches via [this message]
2023-01-06 21:04 ` [bug#60586] [PATCH v2 1/2] gnu: move meson to (gnu packages meson) Vivien Kraus via Guix-patches via
2023-01-06 22:48 ` [bug#60586] [PATCH v2 2/2] gnu: p11-kit-next: Switch to meson-build-system Vivien Kraus via Guix-patches via
2023-01-06 23:05 ` [bug#60586] [PATCH v2 0/2] Switch p11-kit-next " Vivien Kraus via Guix-patches via
2023-01-07 3:15 ` [bug#60586] [PATCH v3 0/1] " Vivien Kraus via Guix-patches via
2023-01-06 22:48 ` [bug#60586] [PATCH v3 1/1] gnu: p11-kit-next: Switch " Vivien Kraus via Guix-patches via
2023-02-17 15:49 ` bug#60586: " Christopher Baines
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1673045732.git.vivien@planete-kraus.eu \
--to=guix-patches@gnu.org \
--cc=60586@debbugs.gnu.org \
--cc=vivien@planete-kraus.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).