From: Fredrik Salomonsson <plattfot@posteo.net>
To: Andy Tai <atai@atai.org>, help-guix@gnu.org
Subject: Re: meson needs certain version
Date: Tue, 10 Aug 2021 01:20:56 +0000 [thread overview]
Message-ID: <877dguumbr.fsf@d2.com> (raw)
In-Reply-To: <CAJsg1E9=L6L=KU0BCJCodoV+U-Yvcn0ggaN-FFXk+UfzM6mYAg@mail.gmail.com>
Hi,
Andy Tai <atai@atai.org> writes:
> Hi, I am trying to create package definition for some specific package
> and it uses meson for build. When I try to guix build the package,
> it fails with
>
> meson.build:1:0: ERROR: Meson version is 0.53.2 but project requires >= 0.54
>
> I find meson later than 0.53.2 in guix already, but how in package
> definition to specify to use a particular meson version? Thanks
>
I use something like this in my guix.scm for a package that uses meson
and requires a version newer than 0.53.2
---8<---------------------------------------------------------------------------
(use-modules
(guix build-system meson)
…
(gnu packages build-tools)
)
(define-public foo
(package
…
(build-system meson-build-system)
(arguments
`(#:meson ,meson-0.55))
…
))
--->8---------------------------------------------------------------------------
Note that the defintion of meson-0.55 in the build-tools.scm has the
comment
;; Added temporarily for packages that need it.
;; TODO: Remove when core-updates is merged.
(define-public meson-0.55
…
)
So it might be safer to use meson-next to avoid breakage if/when
meson-0.55 gets removed.
--
s/Fred[re]+i[ck]+/Fredrik/g
prev parent reply other threads:[~2021-08-10 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 23:10 meson needs certain version Andy Tai
2021-08-10 1:20 ` Fredrik Salomonsson [this message]
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=877dguumbr.fsf@d2.com \
--to=plattfot@posteo.net \
--cc=atai@atai.org \
--cc=help-guix@gnu.org \
/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.
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).