From: DATACOM - Farina <farina@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-colorama: new package
Date: Tue, 04 Aug 2015 11:23:06 -0300 [thread overview]
Message-ID: <55C0CACA.4010105@datacom.ind.br> (raw)
In-Reply-To: <20150804153825.3a46c00e@free-electrons.com>
Hi Thomas,
On 04-08-2015 10:38, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 04 Aug 2015 10:31:50 -0300, DATACOM - Farina wrote:
>
>>> Do you intend to submit some packages that will use
>>> host-python-colorama?
>>
>> At this specific moment, no. But we are analyzing the ARM mbed package,
>> which are widely used libraries and tools for ARM microcontrollers, and
>> makes use of host-python-colorama on its build-system.
>
> But why do you use Buildroot to build something for a micro-controller?
> I don't really see the connection between using ARM mbed and Buildroot.
>
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.
Cheers,
--
Augusto Farina
DATACOM / R&D - Access
www.datacom.ind.br
next prev parent reply other threads:[~2015-08-04 14:23 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 [this message]
2015-08-04 17:43 ` Thomas Petazzoni
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=55C0CACA.4010105@datacom.ind.br \
--to=farina@datacom.ind.br \
--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.