From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Makefile: Support merged defconfigs
Date: Fri, 13 May 2016 14:59:44 +0200 [thread overview]
Message-ID: <20160513145944.4246bbdd@free-electrons.com> (raw)
In-Reply-To: <b44b67ae-4aa1-5740-cdf4-22f3296fc58f@mind.be>
Hello,
On Thu, 12 May 2016 23:58:55 +0200, Arnout Vandecappelle wrote:
> I tend to agree with Thomas's reasoning. However, I think it would be good if
> there was a clearer canonical way of using buildroot. Gustavoz' genconfig script
> could be part of that. I, for example, have a local.mk fragment that autodetects
> packages you have checked out in $(BR2_EXTERNAL)/src and adds OVERRIDE_SRCDIR
> for them. I remember there was this template br2-external github repo at some
> point that you could use as a basis to start your own br2-external project (but
> I can't find it back).
You're probably referring to
https://github.com/Openwide-Ingenierie/buildroot-submodule.
> I do think it is good if such supporting functionality is carried in the core
> buildroot repo. But it's better if it's a bit out of the way, not in the main
> Makefile, and probably called through some helper script.
>
> I have a similar feeling about the genimage template script BTW.
Should we create a section in the manual with some kind of "best
practices" or "going further" ideas?
Regarding Gustavo's 'genconfig' script, I am not sure it makes a lot of
sense to have something like that in the tree. All what it does is very
project-specific, and down the road, it simply calls the
merge_config.sh script, which is already in our tree.
So, for the specific situation of creating a defconfig by combining
fragments, isn't the problem more a documentation problem than anything
else?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-13 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 5:22 [Buildroot] [PATCH 1/1] Makefile: Support merged defconfigs Sam Bobroff
2016-05-10 1:04 ` Samuel Mendoza-Jonas
2016-05-11 4:34 ` Cyril Bur
2016-05-12 14:02 ` Thomas Petazzoni
2016-05-12 21:58 ` Arnout Vandecappelle
2016-05-13 12:59 ` 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=20160513145944.4246bbdd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.