From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2] docs/manual: document meson-based packages
Date: Thu, 28 Dec 2017 23:35:25 +0100 [thread overview]
Message-ID: <20171228233525.375fcbd2@windsurf> (raw)
In-Reply-To: <20171228222539.GH3428@scaer>
Hello,
On Thu, 28 Dec 2017 23:25:39 +0100, Yann E. MORIN wrote:
> IIRC, I made the same comment in a previous iteration of this patch, and
> yes, meson really insists on having an empty build directory, otherwise it
> fails loudly... :-/
>
> This should have been part of the commit log *and* should be clearly
> stated in the manual that this is required.
Follow-up patches welcome :-)
meson support has been sitting in patchwork for a while, and nobody
made this comment. It was time to apply it, and it is always time to
apply follow-up patches :-)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-28 22:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 13:10 [Buildroot] [PATCH v4 0/2] Add support for Meson build Eric Le Bihan
2017-10-29 13:10 ` [Buildroot] [PATCH v4 1/2] meson: new package Eric Le Bihan
2017-11-24 10:54 ` Yegor Yefremov
2017-12-28 22:21 ` Thomas Petazzoni
2017-10-29 13:10 ` [Buildroot] [PATCH v4 2/2] docs/manual: document meson-based packages Eric Le Bihan
2017-11-24 13:51 ` Yegor Yefremov
2017-12-28 22:22 ` Thomas Petazzoni
2017-12-28 22:25 ` Yann E. MORIN
2017-12-28 22:35 ` Thomas Petazzoni [this message]
2017-12-28 22:46 ` Yann E. MORIN
2017-11-24 10:54 ` [Buildroot] [PATCH v4 0/2] Add support for Meson build Yegor Yefremov
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=20171228233525.375fcbd2@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 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.