[Buildroot] Package not building automatically.

[Buildroot] Package not building automatically.

[Samuel Hurst]

Hi All,

Apologies if this isn't the right place to ask this question.

I'm currently using Buildroot to build some images for Raspberry Pis to
be used as demonstrators. However, I've been hitting an issue where
Buildroot is not building certain packages unless I force them to build
manually (i.e. make <package-name>, instead of just running make).

In this case, I'm trying to get a Google QUIC library to build from
github. I'm wondering if it's something wrong with my Config.in and .mk
files that I've created:

== package/libquic/Config.in ===========================================
config BR2_PACKAGE_LIBQUIC
    bool "libquic"
    depends on BR2_TOOLCHAIN_HAS_THREADS
    select BR2_PACKAGE_ICU
    select BR2_PACKAGE_LIBEVENT
    help
        QUIC, a multiplexed stream transport over UDP

========================================================================

== package/libquic/libquic.mk ==========================================
#############################################################################
#
# QUIC Library
#
#############################################################################

LIBQUIC_VERSION = 8954789a056d8e7d5fcb6452fd1572ca57eb5c4e
LIBQUIC_SITE_METHOD = git
LIBQUIC_SITE = https://github.com/devsisters/libquic.git
LIBQUIC_SOURCE = libquic-$(LIBQUIC_VERSION).tar.gz
LIBQUIC_DEPENDENCIES = icu libevent
LIBQUIC_INSTALL_STAGING = YES

$(eval $(cmake-package))
========================================================================

The package shows up in the menuconfig interface and it is selected
(indeed, it is depended on by another package which does build as it
should). Can anyone cast some light onto what I might be doing wrong?


Best Regards,
Sam

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20161201/5fceedf8/attachment.asc>

[Buildroot] Package not building automatically.

[Thomas Petazzoni]

Hello,

On Thu, 1 Dec 2016 14:39:52 +0000, Samuel Hurst wrote:

> Apologies if this isn't the right place to ask this question.
> 
> I'm currently using Buildroot to build some images for Raspberry Pis to
> be used as demonstrators. However, I've been hitting an issue where
> Buildroot is not building certain packages unless I force them to build
> manually (i.e. make <package-name>, instead of just running make).
> 
> In this case, I'm trying to get a Google QUIC library to build from
> github. I'm wondering if it's something wrong with my Config.in and .mk
> files that I've created:
> 
> == package/libquic/Config.in ===========================================
> config BR2_PACKAGE_LIBQUIC
>     bool "libquic"
>     depends on BR2_TOOLCHAIN_HAS_THREADS
>     select BR2_PACKAGE_ICU
>     select BR2_PACKAGE_LIBEVENT
>     help
>         QUIC, a multiplexed stream transport over UDP
> 
> ========================================================================
> 
> == package/libquic/libquic.mk ==========================================
> #############################################################################
> #
> # QUIC Library
> #
> #############################################################################
> 
> LIBQUIC_VERSION = 8954789a056d8e7d5fcb6452fd1572ca57eb5c4e
> LIBQUIC_SITE_METHOD = git
> LIBQUIC_SITE = https://github.com/devsisters/libquic.git
> LIBQUIC_SOURCE = libquic-$(LIBQUIC_VERSION).tar.gz
> LIBQUIC_DEPENDENCIES = icu libevent
> LIBQUIC_INSTALL_STAGING = YES
> 
> $(eval $(cmake-package))
> ========================================================================
> 
> The package shows up in the menuconfig interface and it is selected
> (indeed, it is depended on by another package which does build as it
> should). Can anyone cast some light onto what I might be doing wrong?

Nothing looks wrong here. Are you sure that grep
BR2_PACKAGE_LIBQUIC .config shows that this package is enabled?

For a package to build, there's a few rules to respect:

 - the option must be named BR2_PACKAGE_<FOO>

 - the package must be in package/<foo>/<foo>.mk

 - the variables in foo.mk must be prefixed by <FOO>

All three conditions seem to be respected on what you're showing.

Unrelated, but the LIBQUIC_SOURCE variable is useless, since you have
specified LIBQUIC_SITE_METHOD = git. But that's definitely not the
reason why this package doesn't build.

Best regards,

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

[Buildroot] Package not building automatically.

[Samuel Hurst]

Hi Thomas,

Thanks for your quick response.

On 01/12/16 15:26, Thomas Petazzoni wrote:
> Hello,
> 
> Nothing looks wrong here. Are you sure that grep
> BR2_PACKAGE_LIBQUIC .config shows that this package is enabled?

Yes:

samuelh [buildroot]: grep BR2_PACKAGE_LIBQUIC .config
BR2_PACKAGE_LIBQUIC=y

> For a package to build, there's a few rules to respect:
> 
>  - the option must be named BR2_PACKAGE_<FOO>
> 
>  - the package must be in package/<foo>/<foo>.mk
> 
>  - the variables in foo.mk must be prefixed by <FOO>
> 
> All three conditions seem to be respected on what you're showing.

That's what was confusing me. I'll keep at it and see if anything comes
up. I'm starting to wonder if it might be some inconsistency of spaces
and tabs, would that trip up any of the scripts?

> Unrelated, but the LIBQUIC_SOURCE variable is useless, since you have
> specified LIBQUIC_SITE_METHOD = git. But that's definitely not the
> reason why this package doesn't build.

I'll keep that in mind :)

Thanks for the advice,
-Sam

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20161201/2e52e732/attachment.asc>