all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: 29764@debbugs.gnu.org
Subject: [bug#29764] [PATCH] gnu: lollypop: Use meson-build-system.
Date: Fri, 22 Dec 2017 09:51:19 +0100	[thread overview]
Message-ID: <87r2rnb0xk.fsf@gnu.org> (raw)
In-Reply-To: <20171218.111916.1061558544436379881.post@thomasdanckaert.be> (Thomas Danckaert's message of "Mon, 18 Dec 2017 11:19:16 +0100 (CET)")

Hello Thomas,

Thomas Danckaert <post@thomasdanckaert.be> skribis:

> this patch replaces the “pseudo meson build system” for lollypop by
> the real thing ;-) (By the way, the current build doesn't succeed
> anymore.)
>
> Thomas
>
>>From fb89164e2983ebb61b0920d52fcce04d6ac9e9da Mon Sep 17 00:00:00 2001
> From: Thomas Danckaert <thomas.danckaert@gmail.com>
> Date: Mon, 18 Dec 2017 11:10:27 +0100
> Subject: [PATCH] gnu: lollypop: Use meson-build-system.
>
> * gnu/packages/gnome.scm (lollypop) [build-system]: Use meson-build-system.
> [arguments]: Remove phases for "pseudo meson build system", enable
> glib-or-gtk?
> [native-inputs]: Add glib:bin and gtk+:bin, remove ninja.
> [inputs]: Remove gtk+ and meson.

Go for it!

I suspect the error Catonano reports is not new and might be because
GI_TYPELIB_PATH lacks an entry or something along these lines.  This can
be investigated separately though.

Thanks,
Ludo’.

  parent reply	other threads:[~2017-12-22  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 10:19 [bug#29764] [PATCH] gnu: lollypop: Use meson-build-system Thomas Danckaert
2017-12-21 20:54 ` Catonano
2017-12-22  8:50   ` Thomas Danckaert
2017-12-22  8:51 ` Ludovic Courtès [this message]
2017-12-22 19:02   ` Catonano
2017-12-26 12:13     ` Thomas Danckaert
2017-12-26 13:56       ` Catonano
2017-12-27 15:24         ` bug#29764: " Thomas Danckaert

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r2rnb0xk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=29764@debbugs.gnu.org \
    --cc=post@thomasdanckaert.be \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.