From: Sascha Hauer <s.hauer@pengutronix.de>
To: Giorgio Dal Molin <giorgio.nicole@arcor.de>
Cc: barebox@lists.infradead.org
Subject: Re: re-generate the builtin environment
Date: Mon, 19 Feb 2018 07:27:25 +0100 [thread overview]
Message-ID: <20180219062724.apr4izfpiv3pai7o@pengutronix.de> (raw)
In-Reply-To: <4066173.3341.1518772140511@mail.vodafone.de>
Hi Giorgio,
On Fri, Feb 16, 2018 at 10:09:00AM +0100, Giorgio Dal Molin wrote:
> Hi,
>
> I want to build a default environment in the barebox for my
> board.
>
>
> For this I defined the following vars in the .config file:
>
> ...
> CONFIG_DEFAULT_ENVIRONMENT=y
> CONFIG_DEFAULT_COMPRESSION_LZ4=y
> CONFIG_DEFAULT_ENVIRONMENT_GENERIC_NEW=y
> CONFIG_DEFAULT_ENVIRONMENT_GENERIC_NEW_DFU=y
> CONFIG_DEFAULT_ENVIRONMENT_PATH="arch/arm/boards/am335x-evm/defaultenv-am335x_evm"
> ...
>
> What I observe is that the first time I build barebox the default env is also built;
> but after that, if I modify something under CONFIG_DEFAULT_ENVIRONMENT_PATH and
> just rebuild the barebox dir. without a 'make clean' then the changes are missed.
>
> It this correct or do I do something wrong.
>
> The second question is: I noticed that in the board Makefile:
>
> arch/arm/boards/am335x-evm/Makefile
>
> one can add the definition:
>
> bbenv-y += defaultenv-am335x_evm
Try this one instead. Traditionally there has only been
CONFIG_DEFAULT_ENVIRONMENT_PATH. bbenv-y is for compiling different
separate environment snippets into the binary and to activate them
later in the code. Adding bbenv-y like above doesn't change anything,
the snippet needs to be loaded using:
defaultenv_append_directory(defaultenv_am335x_evm);
This is used for compiling barebox for multiple boards and decide during
runtime which board specific env should be used.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-02-19 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 9:09 Giorgio Dal Molin
2018-02-19 6:27 ` Sascha Hauer [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=20180219062724.apr4izfpiv3pai7o@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=giorgio.nicole@arcor.de \
/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