[Buildroot] Using 2016.11-rc2: external packages and BR2_EXTERNAL ?

[Buildroot] Using 2016.11-rc2: external packages and BR2_EXTERNAL ?

[jerry at chordia.co.uk]

Greetings. Any thoughts on this one?  

 

This post (
<http://buildroot.uclibc.narkive.com/wXlmUu43/patch-br2-external-make-it-ava
ilable-to-post-build-image-scripts>
http://buildroot.uclibc.narkive.com/wXlmUu43/patch-br2-external-make-it-avai
lable-to-post-build-image-scripts) suggests BR2_EXTERNAL is exported to all
configure/make/shell stages.

 

Given the following external config.in

 

#---------------snip---------------------

source "$BR2_EXTERNAL_TARGET1_PATH/package/libxyz/Config.in"

source "$BR2_EXTERNAL/package/appxyz/Config.in"

#---------------snip---------------------

 

Any attempt to configure fails with

 

/home/user/br/external/target1/Config.in:2: can't open file
"/package/appxyz/Config.in"

 

What is the best way to ensure $BR2_EXTERNAL is available at the configure
stage?

 

TAIA and BR

 

Jerry.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20161212/374bc3ca/attachment.html>

[Buildroot] Using 2016.11-rc2: external packages and BR2_EXTERNAL ?

[Thomas Petazzoni]

Hello,

On Mon, 12 Dec 2016 08:50:20 -0000, jerry at chordia.co.uk wrote:

> What is the best way to ensure $BR2_EXTERNAL is available at the configure
> stage?

With the support for multi-br2-external in 2016.11, things have changed
a bit, and BR2_EXTERNAL no longer exists. It's name
BR2_EXTERNAL_<name_of_your_external>.

See the CHANGES file in Buildroot:

        It is now possible to specify multiple BR2_EXTERNAL
        directories. The required files in a BR2_EXTERNAL directory
        have changed to accomodate this feature. Refer to the
        documentation for details of how to update them. External
        trees now have a name and a description. Also, it is possible
        to override a defconfig in the external tree.

Best regards,

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

[Buildroot] Using 2016.11-rc2: external packages and BR2_EXTERNAL ?

[jerry at chordia.co.uk]

Hello Thomas

> With the support for multi-br2-external in 2016.11, things have changed a
bit,
> and BR2_EXTERNAL no longer exists. It's name
> BR2_EXTERNAL_<name_of_your_external>.

Thanks. I'm aware of the multi change. 

One problem is that this now makes it difficult to share packages. I'm
currently building for 3 different targets that share a common set of
packages. I think it would make sense to keep BR2_EXTERNAL as _well_ as the
'external' version to handle this case?

I did try modifying support/scripts/br_external as below but it does not
have the expected effect.

Or is there another/better way to do this? Any suggestions?

MTIA

Jerry.

---------------------------------snip-------------------------------
diff --git a/support/scripts/br2-external b/support/scripts/br2-external
index 055dc08..ea23399 100755
--- a/support/scripts/br2-external
+++ b/support/scripts/br2-external
@@ -147,6 +147,9 @@ do_mk() {
         printf 'export BR2_EXTERNAL_%s_PATH = %s\n' "${br2_name}"
"${br2_ext}"
         printf 'export BR2_EXTERNAL_%s_DESC = %s\n' "${br2_name}"
"${br2_desc}"
     done
+
+       # keep so we know the name of 'this' external
+       printf 'export BR2_EXTERNAL = %s\n' "${BR2_EXTERNAL}"
 }
 
 # Generate the kconfig snippet for the br2-external tree.

[Buildroot] Using 2016.11-rc2: external packages and BR2_EXTERNAL ?

[Thomas Petazzoni]

Hello,

On Mon, 12 Dec 2016 11:43:21 -0000, jerry at chordia.co.uk wrote:

> One problem is that this now makes it difficult to share packages. I'm

What do you mean by "share packages" ?

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

[Buildroot] Using 2016.11-rc2: external packages and BR2_EXTERNAL ?

[jerry at chordia.co.uk]

Hi Thomas,

> What do you mean by "share packages" ?

Code common to all targets but stored outside of the buildroot installation.


The issue is moot. The new mechanism will work as it stands.
 
Thanks again.

Jerry