From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] packages build order and dependencies
Date: Fri, 12 Jul 2013 13:25:58 +0200 [thread overview]
Message-ID: <20130712132558.59e78252@skate> (raw)
In-Reply-To: <51DFE0C0.6010307@gmail.com>
Dear Jan Pohanka,
On Fri, 12 Jul 2013 12:56:00 +0200, Jan Pohanka wrote:
> I would like to clarify myself how the order of the package build is
> defined. I thought that when I specify the package dependency in
> Kconfig, then the top one should be built first. But it seems that I
> need also it to add MY_PACKAGE_DEPENDENCIES variable in mk file. Am I right?
What defines the order of build is the <pkg>_DEPENDENCIES variable in
the package .mk file.
> Like this example
> # Kconfig
> config MY_PACKAGE
> bool "my_package"
> depends on BR2_LINUX_KERNEL
The Config.in stuff doesn't take care of anything build order. It's
just here to ensure consistency of the configuration, i.e that when one
package selects libpng, all packages that can optionally use libpng are
informed and can use it.
> #my_package.mk
> ...
> #is this needed for building linux before my_package?
> MY_PACKAGE_DEPENDENCIES += linux
Yes, this is precisely what tells Buildroot to build the 'linux'
package, then the 'my-package' package.
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-07-12 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 10:56 [Buildroot] packages build order and dependencies Jan Pohanka
2013-07-12 11:25 ` 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=20130712132558.59e78252@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 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.