[oe] [PATCH] gphoto2_2.4.8.bb: Stop configure from looking in /usr/local/include

[Khem Raj]

On Wed, Nov 3, 2010 at 1:21 PM, Frans Meulenbroeks
<fransmeulenbroeks at gmail.com> wrote:
> 2010/11/3 Khem Raj <raj.khem at gmail.com>:
>> On Wed, Nov 3, 2010 at 12:04 PM, Frans Meulenbroeks
>> <fransmeulenbroeks at gmail.com> wrote:
>>> 2010/11/3 Khem Raj <raj.khem at gmail.com>:
>>>
>>>>
>>>> yes a more detailed solution is better. you have to go through the
>>>> configure of every
>>>> package and understand the behavior then act upon. As I said before
>>>> its a tedious task
>>>>
>>> I'm well aware of this. That is also why in the infrastructure thread
>>> I suggested using automated testing to find misbehaving packages.
>>>
>>> Btw there are 355 .inc files that contain the word autotools and 1899 .bb files.
>>> Of course there are lots of dups in there.
>>> And maybe for the base recipes we can convince the yocto people that
>>> this is a serious QA issue (and they have some people employed to work
>>> on this if I understood properly).
>>>
>>
>> numbers means not so much when it comes down to this. I don't know if
>> any distribution that even does that
>> so I take comfort in everyone being wrong.
>>
>
> I agree that numbers don't mean that much. Just wanted to give an
> indication of the possible effort needed.
> Also no idea how debian does this.

Does it do it in first place ?

> One way to get a minimal package is to have everything in packaged
> staging then bake the recipe.
> that'll only drag in stuff from depends.

It depends also on the sequence of staging. So there are multiple
factors and no two stagings will look same


>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>