* [Buildroot] ~/buildroot/packages
@ 2017-05-18 15:08 moi moi
2017-05-18 15:53 ` Thomas Petazzoni
2017-05-18 16:23 ` Peter Korsgaard
0 siblings, 2 replies; 3+ messages in thread
From: moi moi @ 2017-05-18 15:08 UTC (permalink / raw)
To: buildroot
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). I run Debian 8.7.
regards, Tacocat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170518/7c8e2b1e/attachment.html>
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] ~/buildroot/packages
2017-05-18 15:08 [Buildroot] ~/buildroot/packages moi moi
@ 2017-05-18 15:53 ` Thomas Petazzoni
2017-05-18 16:23 ` Peter Korsgaard
1 sibling, 0 replies; 3+ messages in thread
From: Thomas Petazzoni @ 2017-05-18 15:53 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] ~/buildroot/packages
2017-05-18 15:08 [Buildroot] ~/buildroot/packages moi moi
2017-05-18 15:53 ` Thomas Petazzoni
@ 2017-05-18 16:23 ` Peter Korsgaard
1 sibling, 0 replies; 3+ messages in thread
From: Peter Korsgaard @ 2017-05-18 16:23 UTC (permalink / raw)
To: buildroot
>>>>> "moi" == moi moi <shmrcoffee800@gmail.com> writes:
> 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). I run Debian 8.7.
Well, not populate as in Buildroot generating this data - But yes, these
files are part of Buildroot. This is the meta data describing how to
build the 2000+ packages available in Buildroot.
Please have a look at the manual for details:
https://buildroot.org/downloads/manual/manual.html
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-05-18 16:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-05-18 15:08 [Buildroot] ~/buildroot/packages moi moi
2017-05-18 15:53 ` Thomas Petazzoni
2017-05-18 16:23 ` Peter Korsgaard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox