From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv5 1/5] core: introduce the BR2_EXTERNAL variable
Date: Wed, 4 Dec 2013 23:05:05 +0100 [thread overview]
Message-ID: <20131204220505.GC3332@free.fr> (raw)
In-Reply-To: <1386183373-17611-2-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2013-12-04 19:56 +0100, Thomas Petazzoni spake thusly:
> This commit introduces the BR2_EXTERNAL environment variable, which
> will allow to keep Buildroot customization (board-specific
> configuration files or root filesystem overlays, package Config.in and
> makefiles, as well as defconfigs) outside of the Buildroot tree.
>
> This commit only introduces the variable itself, and ensures that it
> is available within Config.in options. This allows us to use
> $BR2_EXTERNAL in a 'source' statement in Config.in.
>
> Following patches extend the usage of BR2_EXTERNAL to other areas
> (packages and defconfigs).
>
> In details, this commit:
>
> * Introduces the BR2_EXTERNAL Kconfig option. This option has no
> prompt, and is therefore not visible to the user and also not
> stored in the .config file. It is automatically set to the value of
> the BR2_EXTERNAL environment variable. The only purpose of this
> BR2_EXTERNAL Kconfig option is to allow $BR2_EXTERNAL to be
> properly expanded when used inside Kconfig source statements.
>
> * Calculates the BR2_EXTERNAL value to use. If passed on the command
> line, then this value is taken in priority, and saved to a
> .br-external hidden file in the output directory. If not passed on
> the command line, then we read the .br-external file from the
> output directory. This allows the user to not pass the BR2_EXTERNAL
> value at each make invocation. If no BR2_EXTERNAL value is passed,
> we define it to support/dummy-external, so that the kconfig code
> finds an existing $(BR2_EXTERNAL)/package/Config.in file to
> include.
>
> * Passes the BR2_EXTERNAL into the *config environment, so that its
> value is found when parsing/evaluating Config.in files and .config
> values.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Two SoB by Thomas? But I like how they properly line up! ;-)
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-12-04 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 18:56 [Buildroot] [PATCHv5 0/5] Keeping customizations outside the Buildroot tree with BR2_EXTERNAL Thomas Petazzoni
2013-12-04 18:56 ` [Buildroot] [PATCHv5 1/5] core: introduce the BR2_EXTERNAL variable Thomas Petazzoni
2013-12-04 22:05 ` Yann E. MORIN [this message]
2013-12-04 18:56 ` [Buildroot] [PATCHv5 2/5] core: allow external Config.in/makefile code to be integrated Thomas Petazzoni
2013-12-04 22:07 ` Yann E. MORIN
2013-12-04 18:56 ` [Buildroot] [PATCHv5 3/5] core: allow external defconfigs to be used Thomas Petazzoni
2013-12-04 22:11 ` Yann E. MORIN
2013-12-04 18:56 ` [Buildroot] [PATCHv5 4/5] docs/manual: add explanations about BR2_EXTERNAL Thomas Petazzoni
2013-12-04 22:22 ` Yann E. MORIN
2013-12-04 18:56 ` [Buildroot] [PATCHv5 5/5] manual: fix manual generation with BR2_EXTERNAL support Thomas Petazzoni
2013-12-04 22:28 ` Yann E. MORIN
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=20131204220505.GC3332@free.fr \
--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