All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Becker <chemobejk@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RESEND] core: enhance printvars for variables with newlines
Date: Sun, 16 Dec 2018 17:33:48 +0200	[thread overview]
Message-ID: <CAOJ2eMdF2qZL6yFenfO6xVeZxf_gBgBejQ=PX6HpcEvs26pRCw@mail.gmail.com> (raw)
In-Reply-To: <20181216161430.1752d2f0@windsurf.home>

Hi,

On Sun, Dec 16, 2018 at 5:14 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> You did not answer my question: why didn't you use features of
> Buildroot such as "make <pkg>-build" or "make <pkg>-rebuild" ?

That would require the buildroot source tree to be available. Plus
adding all internal components, even the ones that have nothing to
with buildroot and do not use any of its host build tools, to the
buildroot meta build system for buildroot build to recognize the
generated build artefacts.

> How in practice you were using those commands extracted from Buildroot
> variables to achieve "modular builds" ?

That depends on the module, e.g.

* buildroot: output/target/, host/ plus selected buildroot meta build
system source files required for flash image build + module install
script
* kernel: output from modules_install & install + module install script
* ... (you get the picture)

But definitely no source code is included in the module build
artefact. All internal components have been removed from buildroot
meta build system, i.e. buildroot module build only builds components
included in its component list, i.e. buildroot module build only needs
to be executed after pulling changes from upstream.

Regards, Stefan

  reply	other threads:[~2018-12-16 15:33 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       ` [Buildroot] [PATCH RESEND] " Thomas Petazzoni
2018-12-16 14:57         ` Stefan Becker
2018-12-16 15:14           ` Thomas Petazzoni
2018-12-16 15:33             ` Stefan Becker [this message]
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='CAOJ2eMdF2qZL6yFenfO6xVeZxf_gBgBejQ=PX6HpcEvs26pRCw@mail.gmail.com' \
    --to=chemobejk@gmail.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.