From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Linux kernel configuration changes and out of tree module builds
Date: Tue, 15 Oct 2019 10:13:03 +0200 [thread overview]
Message-ID: <20191015101303.459b9ff2@windsurf.home> (raw)
In-Reply-To: <CAAhKrJ2tKTbj=Tx+RHrk8BX7XBnbEjdKNM7YyHoKgb9wOmYYjw@mail.gmail.com>
Hello Dan,
On Mon, 14 Oct 2019 15:38:07 -0600
Dan Walkes <danwalkes@trellis-logic.com> wrote:
> Understood. How about this modification?
>
> * When a +FOO_DEPENDENCIES+ package is rebuilt or removed, the package
> foo is not automatically rebuilt. For example, if a package +bar+ is
> listed in +FOO_DEPENDENCIES+ with +FOO_DEPENDENCIES = bar+ and the
> configuration of the +bar+ package is changed, the configuration
> change would not result in a rebuild of package package +foo+
> automatically. In this scenario, you may need to either rebuild any
> packages in your build which reference +bar+ in their +DEPENDENCIES+,
> or perform a full rebuild to ensure any +bar+ dependent packages are
> up to date.
Seems good. Waiting for the documentation patches :-)
I think the main issue in our documentation is that currently this will
be added in the section of the documentation on how to add new
packages. But in fact, this explanation is not just relevant for people
adding new packages: it is relevant for people using Buildroot in
general. But well, the structure of our manual is not the best, and I
don't know where it could go. So at least, having the information
*somewhere* is better than not having it at all.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-10-15 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 20:00 [Buildroot] Linux kernel configuration changes and out of tree module builds Dan Walkes
2019-10-14 20:58 ` Thomas Petazzoni
2019-10-14 21:38 ` Dan Walkes
2019-10-15 8:13 ` Thomas Petazzoni [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191015101303.459b9ff2@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