[oe] [meta-oe][PATCH] libconfig: add support for libconfig-native

[Andre McCurdy]

On Mon, Dec 19, 2016 at 6:13 AM, Andreas Müller
<schnitzeltony at googlemail.com> wrote:
> On Mon, Dec 19, 2016 at 3:11 PM, Andre McCurdy <armccurdy at gmail.com> wrote:
>> On Mon, Dec 19, 2016 at 5:27 AM, Andreas Müller
>> <schnitzeltony at googlemail.com> wrote:
>>> On Mon, Dec 19, 2016 at 2:09 PM, Andre McCurdy <armccurdy at gmail.com> wrote:
>>>> Signed-off-by: Andre McCurdy <armccurdy at gmail.com>
>>>> ---
>>>>  meta-oe/recipes-extended/libconfig/libconfig_1.5.bb | 2 ++
>>>>  1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/meta-oe/recipes-extended/libconfig/libconfig_1.5.bb b/meta-oe/recipes-extended/libconfig/libconfig_1.5.bb
>>>> index fb6e50e..94daa88 100644
>>>> --- a/meta-oe/recipes-extended/libconfig/libconfig_1.5.bb
>>>> +++ b/meta-oe/recipes-extended/libconfig/libconfig_1.5.bb
>>>> @@ -12,3 +12,5 @@ inherit autotools-brokensep pkgconfig
>>>>
>>>>  SRC_URI[md5sum] = "a939c4990d74e6fc1ee62be05716f633"
>>>>  SRC_URI[sha256sum] = "e31daa390d8e4461c8830512fe2e13ba1a3d6a02a2305a02429eec61e68703f6"
>>>> +
>>>> +BBCLASSEXTEND = "native"
>>>> --
>>>> 1.9.1
>>>>
>>> Please tell us why libconfig needs native biuld in commit message.
>>
>> A private recipe in a private meta layer - the names of which are
>> probably not very useful or interesting in a meta-oe commit message.
>
> So why not just an append in that layer?

Because recipe enhancements which may be useful to others should be
merged upstream.

> Andreas
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel