[OE-core] libcap: make -e causing trouble

[Christopher Larson]

On Thu, Apr 30, 2015 at 7:55 AM, Mike Crowe <mac at mcrowe.com> wrote:

> On Thursday 30 April 2015 at 07:39:25 -0700, Christopher Larson wrote:
> > On Thu, Apr 30, 2015 at 7:28 AM, Mike Crowe <mac at mcrowe.com> wrote:
> > > Unfortunately passing "-e" subtly changes the behaviour of libcap's
> > > Make.Rules under recursive make when prefix="" (which it is for us
> since
> > > we're using meta-micro.)
>
> [snip]
>
> > Given our use of make -e (with MAKEFLAGS= to try to prevent it from
> flowing
> > into submakes) was always a hack to try to let things "just work", I
> think
> > wherever possible we should stop relying on it, and explicitly pass
> > everything the way that particular make-based buildsystem expects,
> > personally. Better to be explicit than to rely on implicit "magic".
> > Further, that behavior encourages recipe maintainers to not even read the
> > buildsystem of the project they're creating a recipe for, which often
> leads
> > to problems down the road..
>
> I completely agree, but what is the best way to avoid "-e". Is there ever
> likely to be anything else in EXTRA_OEMAKE that would need to be preserved?
>
> I notice that autotools.bbclass just sets EXTRA_OEMAKE = "" so perhaps it's
> relatively safe to just assign it directly.


Yeah, generally it's safe. The recipe knows more about a make-based
buildsystem than any of our classes do anyway, since there are no real
standards. Autotools is a different story, of course.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150430/cfd76369/attachment-0002.html>