From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] modifying buildroot for non- linux freertos
Date: Wed, 17 Apr 2013 10:17:12 +0200 [thread overview]
Message-ID: <20130417101712.7a06227b@skate> (raw)
In-Reply-To: <516E3FDA.6040109@mind.be>
Peter, Arnout,
On Wed, 17 Apr 2013 08:23:22 +0200, Arnout Vandecappelle wrote:
> I'm afraid that the expertise on the internal buildroot toolchain build
> process is not here anymore. Some buildroot developers understand how the
> .mk file works, but not really why things were done in that particular way...
>
> But anyway, I don't think you really need buildroot for this. Buildroot
> is meant for building packages for the target, and just builds some host
> packages that are needed for building some of these packages. I think
> crosstool-NG is a much better fit for your purpose. It's build system is
> pretty complex, but I think it's still easier to understand than the
> buildroot system. Also, crosstool-NG might be interested in adding
> support for newlib (as an alternative to uClibc) in its core infrastructure.
Crosstool-NG already has support for newlib.
Peter, I agree with Arnout here. The main point of Buildroot is to
build a root filesystem with Linux applications and libraries, and this
is not something you could re-use on FreeRTOS.
You should therefore definitely have a look at Crosstool-NG to produce
a newlib toolchain that works for FreeRTOS.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-04-17 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 21:53 [Buildroot] modifying buildroot for non- linux freertos Peter Saunderson
2013-04-17 6:23 ` Arnout Vandecappelle
2013-04-17 8:17 ` 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=20130417101712.7a06227b@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox