Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] docs/manual: dependency documentation updates
Date: Tue, 31 Dec 2019 18:12:17 +0100	[thread overview]
Message-ID: <20191231171217.GA3519@scaer> (raw)
In-Reply-To: <20191016175545.12855-1-danwalkes@trellis-logic.com>

Dan, All,

On 2019-10-16 11:55 -0600, Dan Walkes spake thusly:
> Update dependency documentation to detail the order-only relationship
> associated with the DEPENDENCIES variable.  See the thread at [1] for
> details.
> 
> [1] http://lists.busybox.net/pipermail/buildroot/2019-October/262685.html
> 
> Signed-off-by: Dan Walkes <danwalkes@trellis-logic.com>

Applied to master, after a slight rephrasing, and a bit of indentation
fixup. Thanks.

Regards,
Yann E. MORIN.

> ---
>  docs/manual/adding-packages-generic.txt |  8 +++++---
>  docs/manual/rebuilding-packages.txt     | 10 ++++++++++
>  2 files changed, 15 insertions(+), 3 deletions(-)
> 
> diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
> index b402767b05..af94f5b1ec 100644
> --- a/docs/manual/adding-packages-generic.txt
> +++ b/docs/manual/adding-packages-generic.txt
> @@ -358,9 +358,11 @@ not and can not work as people would expect it should:
>  * +LIBFOO_DEPENDENCIES+ lists the dependencies (in terms of package
>    name) that are required for the current target package to
>    compile. These dependencies are guaranteed to be compiled and
> -  installed before the configuration of the current package starts. In
> -  a similar way, +HOST_LIBFOO_DEPENDENCIES+ lists the dependencies for
> -  the current host package.
> +  installed before the configuration of the current package starts.
> +  However, modifications to configuration of these dependencies will
> +  not force a rebuild of the current package. In a similar way,
> +  +HOST_LIBFOO_DEPENDENCIES+ lists the dependencies for the current
> +  host package.
>  
>  * +LIBFOO_EXTRACT_DEPENDENCIES+ lists the dependencies (in terms of
>    package name) that are required for the current target package to be
> diff --git a/docs/manual/rebuilding-packages.txt b/docs/manual/rebuilding-packages.txt
> index 6faa67adcb..326cd1fe82 100644
> --- a/docs/manual/rebuilding-packages.txt
> +++ b/docs/manual/rebuilding-packages.txt
> @@ -65,6 +65,16 @@ can help you understand how to work with Buildroot:
>     there is no need for a full rebuild: a simple +make+ invocation
>     will take the changes into account.
>  
> + * 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 +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.
> +
>  Generally speaking, when you're facing a build error and you're unsure
>  of the potential consequences of the configuration changes you've
>  made, do a full rebuild. If you get the same build error, then you are
> -- 
> 2.17.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-12-31 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 17:55 [Buildroot] [PATCH 1/1] docs/manual: dependency documentation updates Dan Walkes
2019-12-31 17:12 ` Yann E. MORIN [this message]
2020-01-02  0:41   ` Dan Walkes
2020-01-02  8:30     ` Yann E. MORIN
2020-01-10 14:08   ` Peter Korsgaard

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=20191231171217.GA3519@scaer \
    --to=yann.morin.1998@free.fr \
    --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