All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Use of buildroot in an embedded linux project
Date: Mon, 16 Mar 2009 20:12:53 +0100	[thread overview]
Message-ID: <20090316201253.6b8c6c1a@surf> (raw)
In-Reply-To: <49BE4EE4.9000709@yahoo.fr>

Le Mon, 16 Mar 2009 14:06:44 +0100,
Hichem Boussetta <boussettahichem@yahoo.fr> a ?crit :

> I am working on a project about building embedded linux systems, and
> I have to choose between many tools that generate cross gnu
> toolchains and root filesystem (buildroot, scratchbox, ELDK...). So,
> it would be grateful if someone could tell me about the advantages of
> using buildroot and about its limitations, because I heard that we
> found some difficulties to cross compile certain packages, like
> Kerberos5.

I don't have all the advantages/drawbacks in my mind, but here are a
few.

Drawbacks :

 * Only uClibc toolchains can be generated by Buildroot ;

 * External toolchain support is still experimental (this is only a
   problem if you plan to use a toolchain that has been generated by
   Buildroot) ;

 * No package management (ipkg, opkg) like you could have with
   OpenEmbedded, for example.

Advantages :

 * Simple enough so that a single human being can manage to understand
   how it works and tune it according to the needs of the project, and
   that you don't spend 5 days trying to figure out how the damn thing
   works.

 * Pretty good support from the Buildroot community.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2009-03-16 19:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 13:06 [Buildroot] Use of buildroot in an embedded linux project Hichem Boussetta
2009-03-16 19:12 ` 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=20090316201253.6b8c6c1a@surf \
    --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.