From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: buildroot@busybox.net
Subject: [Buildroot] multiple BR2_EXTERNAL layers?
Date: Fri, 17 Jul 2015 10:47:24 -0700 [thread overview]
Message-ID: <55A93FAC.2040705@mentor.com> (raw)
In-Reply-To: <20150717164612.GA3637@free.fr>
On 07/17/2015 09:46 AM, Yann E. MORIN wrote:
> On 2015-07-17 09:23 -0700, Hollis Blanchard spake thusly:
>> My team has a bunch of testcases in separate directories. Many of
>> these use simple bare metal executables, but some include Linux. I
>> would like to adopt Buildroot, but keep testcase-specific bits (Linux
>> config files, device trees, etc) in its own directory. At the same
>> time, some components (e.g. test applications) should be shared
>> across testcases. So I want to use BR2_EXTERNAL="/project/testcase
>> /project/shared", but that doesn't seem to be possible right now...?
> Indeed no... However, I have already posted a patch series that does
> implement support for multiple br2-external trees. It is not finished
> yet (i.e. it is in a rather rough state) but works. The project has
> not decided yet if we wanted to support multiple br2-external trees.
> We have to talk about it a bit more. But your message is a clear
> indication that there is a need, and that I'm not the only one with
> that need. Please have a look at the series I posted, test it and
> report on the list whether it Works For You (TM). Also, voice your
> opinion on the cover-letter (having more than a single user (me) with
> the same need will give weight to the proposal).
OK, thanks for the background. I will try to take a look at your series.
In the meantime though, I think I can put the shared content in a local
branch, and use BR2_EXTERNAL for testcase-specific content. I will
explore that first.
Hollis Blanchard
Mentor Graphics Emulation Division
prev parent reply other threads:[~2015-07-17 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 16:23 [Buildroot] multiple BR2_EXTERNAL layers? Hollis Blanchard
2015-07-17 16:46 ` Yann E. MORIN
2015-07-17 17:47 ` Hollis Blanchard [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=55A93FAC.2040705@mentor.com \
--to=hollis_blanchard@mentor.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