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] BR2_EXTERNAL - Broken in 2015.08.01????
Date: Fri, 6 Nov 2015 16:54:42 +0100	[thread overview]
Message-ID: <20151106165442.687e5e08@free-electrons.com> (raw)
In-Reply-To: <CAN34foyWQxHW1t=157ePm8JDfxAT6NoCarGPxOtsXh6C56gJsw@mail.gmail.com>

Dear Stephen Beckwith,

On Fri, 6 Nov 2015 10:22:03 -0500, Stephen Beckwith wrote:

> *And you also state:*
> 
> Package "foo" *must*:
> 
>  * Be implemented in package/foo/foo.mk

Yes, in the main Buildroot tree. In the BR2_EXTERNAL tree, it can be
anywhere you want, as long as the directory name is "foo". I.e, it can
be in

	baz/boz/foo/foo.mk
	package/vendor/foo/foo.mk

> Back to the original problem:  I have a External setup, with "packages"
> specified in a custom directory structure, NOT in a "package" directory yet
> the top level make does NOT build these external packages.  Why?  They are
> only built if I explicity:  make <package> - then it works just fine. . .

Because you named wrongly the Config.in option for those packages....

> I modified the ?leaf? config.in to declare BR2_EXTERNAL_<PKG> - re-run the
> menu config, deslect, re-select, save, verify that the BR2_EXTERNAL_<PKG>
> =y is in the top level .config.

Why do you insist on using BR2_EXTERNAL_<pkg>, while I have been
telling you (as well as the manual and the training slides) that you
should be using BR2_PACKAGE_<pkg> ?

If you don't read what I write, how do you expect things to work ?

> Still does not build from ?make? (there is build directory present.)

Yes, because your Config.in options incorrectly start with
BR2_EXTERNAL_ while they should start with BR2_PACKAGE_.

The code that decides if a package should be built or not is in
package/pkg-generic.mk, and the relevant pieces are:

$(2)_KCONFIG_VAR = BR2_PACKAGE_$(2)
...
ifeq ($$($$($(2)_KCONFIG_VAR)),y)
PACKAGES += $(1)
endif

So, a package named 'foo' is built if BR2_PACKAGE_FOO=y.

Best regards,

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

  reply	other threads:[~2015-11-06 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 13:16 [Buildroot] BR2_EXTERNAL - Broken in 2015.08.01???? Stephen Beckwith
2015-11-05 13:29 ` Thomas Petazzoni
2015-11-05 21:57   ` Stephen Beckwith
2015-11-05 22:05     ` Thomas Petazzoni
2015-11-06 14:12       ` Stephen Beckwith
2015-11-06 14:41         ` Thomas Petazzoni
2015-11-06 15:22           ` Stephen Beckwith
2015-11-06 15:54             ` Thomas Petazzoni [this message]
2015-11-06 16:04               ` Stephen Beckwith
2015-11-06 16:51                 ` Thomas Petazzoni

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=20151106165442.687e5e08@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