From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-colorama: new package
Date: Tue, 4 Aug 2015 19:43:19 +0200 [thread overview]
Message-ID: <20150804194319.52c69bf2@free-electrons.com> (raw)
In-Reply-To: <55C0CACA.4010105@datacom.ind.br>
Hello,
On Tue, 04 Aug 2015 11:23:06 -0300, DATACOM - Farina wrote:
> Our boards has PowerPC/ARM/MIPS running Linux. And also has ARM
> microcontrollers.
>
> So, when we build the main firmware (Linux + rootfs) with Buildroot, we
> also build the microcontroller firmware that goes inside the rootfs
> (using a secondary toolchain).
>
> With this way, we have just one build-system (Buildroot), with
> everything we need integrated on it.
>
> My apologies if it is not the Buildroot idea, but this kind of
> integration is facilitating our work.
Interesting use of Buildroot, definitely! I think it makes a lot of
sense to use Buildroot this way, so I understand better what you did.
I'm still a bit reluctant to add host packages in Buildroot without
users, but at least there is a very useful and interesting use case
behind it, so I might be tempted to apply your patch with the host
package included.
I'm obviously interested by the opinion of other Buildroot developers.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-04 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 20:36 [Buildroot] [PATCH 1/1] python-colorama: new package Augusto Farina
2015-08-04 8:55 ` Thomas Petazzoni
2015-08-04 13:31 ` DATACOM - Farina
2015-08-04 13:38 ` Thomas Petazzoni
2015-08-04 14:23 ` DATACOM - Farina
2015-08-04 17:43 ` Thomas Petazzoni [this message]
2015-09-06 23:01 ` Arnout Vandecappelle
2015-12-01 22:09 ` Thomas Petazzoni
2015-12-07 20:14 ` DATACOM - Farina
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=20150804194319.52c69bf2@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.