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

[Frans Meulenbroeks]

2010/11/2 Khem Raj <raj.khem at gmail.com>:
> On Mon, Nov 1, 2010 at 11:38 PM, Frans Meulenbroeks

>> I have some concerns here.
>> For configure it seems best to explicitly set and reset the flags in
>> it, otherwise you may just pick up whatever happened to be build
>> before.
>>
>
>
> this is the case with any package that uses configure tools. But assumption here
> is that when you are building you are not building stuff thats not
> meant to be in
> the given image.

True. However we should enforce that. If e.g. gphoto has no depends on
exif it autotools will still pick up exif if it happens to be there
because some other package build it.
Funtionally this is not necessarily bad (as your image has exif
anyway), but from a point of reproducability it is undesirable.
E.g. if you build the recipe the first time, you might not get exif
and if you rebuild you do get exif. (because the build system does not
know the dependency is there so it might not have build exif yet).

Actually the results might even differ for between builds of the same
image (especially if you build machines with different speeds etc
and/or use different flags for parallellism.
Therefore I feel it is highly desirable to have all optionals that you
have in configure either explicitly disabled or explicitly added to
depends.

Wrt exif & readline: I agree with koen.

Frans.