[Buildroot] [PATCH] bluez5_utils: add autoreconf back
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Mon Dec 5 21:19:22 UTC 2016
Hello,
On Mon, 5 Dec 2016 22:16:03 +0100, Arnout Vandecappelle wrote:
> > Have you tried adding BLUEZ5_AUTORECONF = YES to your external.mk file?
>
> That won't work, because it's used in an ifeq in the autotools-package
> expansion, and external.mk is included after the packages.
Gah.
> It does work if you put it in override.mk, but that's not convenient in an
> external.
I guess you wanted to say "local.mk" and not "override.mk", right?
But in any case, I don't think we want to have a <pkg>_AUTORECONF = YES
in a package "just in case" someone has patches against this package in
his external tree. Otherwise, all autoconf packages should be
<pkg>_AUTORECONF = YES.
So, we've got two options here:
1. Say that having to change the original .mk file of a package in
Buildroot is a fact of life if you add custom patches for this
package.
2. Imagine a mechanism that allows the "external" stuff to set
autoreconf on a per-package basis.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
More information about the buildroot
mailing list