[OE-core] [PATCH 2/2] cmake: Avoid accidentally including libacl.h

[Chris Larson]

On Tue, Apr 8, 2014 at 6:51 AM, Mike Crowe <mac at mcrowe.com> wrote:

> The cmake recipe doesn't depend on libacl yet cmake will detect libacl.h
> and use it by default. This risks build failures if libacl.h is unstaged
> during the build and it also means that the build cmake will sometimes
> support ACLs and sometimes not.
>

Is this not also a concern for the non-native recipe? And wouldn't it be
better yet to use PACKAGECONFIG, rather than hardcoding the disable of acl
support?
-- 
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/20140408/a06273a0/attachment-0002.html>