From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RESEND] core: enhance printvars for variables with newlines
Date: Sun, 16 Dec 2018 14:54:27 +0100 [thread overview]
Message-ID: <20181216145427.0274aed5@windsurf.home> (raw)
In-Reply-To: <CAOJ2eMc+3Bx40nWF=VALh6JzeaNVWPekyCGXAL2=a_YX4yJWug@mail.gmail.com>
Hello Stefan,
On Thu, 19 Apr 2018 10:14:40 +0300, Stefan Becker wrote:
> On Thu, Apr 19, 2018 at 1:27 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
> >
> > I'm still not convinced that this is such a great idea.
> >
> > 1. As explained in reply to your first iteration, there shouldn't be a need for
> > including Buildroot variables in a surrounding Makefile.
>
> There is nothing you can say that will change the fact that a
> monolithic meta build system is too slow for the CI of our own
> components. So let's just agree to disagree on this point.
I'm jumping back to this very old thread. Could you explain (perhaps
re-explain) what you're trying to do ?
If you need to just re-run a specific step of a specific package, why
don't you use "make foo-build", "make foo-rebuild", etc. ?
It seems very hackish to extract the commands that Buildroot executes
to execute them outside the context of Buildroot. This doesn't really
help to make a case for accepting a patch like you're proposing. Could
you first convince us that there is a valid and reasonable use-case,
and then we can discuss how to support this use-case with Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-16 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOJ2eMdEHvZeJ6rECyRkzMZN0UYJ2CYK4yMgR9d89P%2B-tWYJYw@mail.gmail.com>
2018-04-16 11:58 ` [Buildroot] [PATCH RESEND] core: enhance printvars for variables with newlines Stefan Becker
2018-04-16 12:28 ` Yann E. MORIN
2018-04-18 22:27 ` Arnout Vandecappelle
2018-04-19 7:14 ` Stefan Becker
2018-04-19 7:40 ` [Buildroot] [PATCH v2] " Stefan Becker
2018-04-19 8:08 ` Yann E. MORIN
2018-12-16 13:54 ` Thomas Petazzoni [this message]
2018-12-16 14:57 ` [Buildroot] [PATCH RESEND] " Stefan Becker
2018-12-16 15:14 ` Thomas Petazzoni
2018-12-16 15:33 ` Stefan Becker
2018-12-16 16:19 ` Stefan Becker
2018-12-17 20:08 ` Trent Piepho
2018-12-18 0:24 ` Carlos Santos
2018-12-18 1:19 ` Trent Piepho
2018-04-19 7:47 ` Yann E. MORIN
2018-04-19 7:58 ` Stefan Becker
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=20181216145427.0274aed5@windsurf.home \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox