Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ~/buildroot/packages
Date: Thu, 18 May 2017 17:53:24 +0200	[thread overview]
Message-ID: <20170518175324.19b2a7e5@free-electrons.com> (raw)
In-Reply-To: <CACo+m-trSpHVnX6ccbqQM+1x1FSfBWSj39C8Nk2+961VCT3hLQ@mail.gmail.com>

Hello,

On Thu, 18 May 2017 17:08:42 +0200, moi moi wrote:

> Is it normal behaviour of buildroot to populate the packages folder with
> 40+MBs of various .mk and .in files? Does buildroot copy packages from the
> host system? I have run menuconfig once but have not buildt a system with
> make. There are even folder for opencv and fetchmail there (which are
> present on my host system).

It seems like you really misunderstood what Buildroot's purpose is.
Those .mk and .in files describe how to build a large number of
software components to create an embedded Linux system.

Therefore, if you enable Busybox in your Buildroot configuration,
Buildroot will know how to download, build and install Busybox thanks
to the information available in package/busybox/.

The list of packages supported by Buildroot has *nothing* to do with
what is installed on your host system.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-05-18 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 15:08 [Buildroot] ~/buildroot/packages moi moi
2017-05-18 15:53 ` Thomas Petazzoni [this message]
2017-05-18 16:23 ` Peter Korsgaard

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=20170518175324.19b2a7e5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox