[OE-core] [RFC PATCH 0/7] Developer workflow improvements

[Trevor Woerner]

I think *this* thread (and question) got lost in the shuffle...

On 12/09/14 10:47, Trevor Woerner wrote:
> On 12/02/14 09:01, Paul Eggleton wrote:
>> On Monday 01 December 2014 23:54:03 Trevor Woerner wrote:
>>> On 11/25/14 12:28, Paul Eggleton wrote:
>>>> I've then added a new recipe auto-creation script, recipetool, which can
>>>> take a source tree or URL and create a skeleton recipe to build it.
>>> ...
>>>
>>>>  * "recipetool create" ideally needs to become smarter and fill in
>>>>  
>>>>    more details of the recipe. At some point we'll probably have to
>>>>    make the process interactive and possibly have it automate parts of
>>>>    the build process and examine the output; some things just can't be
>>>>    practically detected from the source tree without building.
>>> There is a tool "autoscan" which might be of some use here. If nothing
>>> else, the resulting configure.scan file could be parsed for DEPENDS
>>> information and perhaps PACKAGECONFIG items too.
>> Interesting - I was not aware of this tool. I've added support for running it 
>> as well as picking converting AC_CHECK_LIB lines over to DEPENDS (with a note 
>> about some of them possibly being optional). Thanks!
>>
> Finding "AC_PATH_X" in "configure.scan" is probably a good indication
> there's an RDEPENDS on "libx11". Maybe "recipetool" could check for that?

*ping*!!

Oddly enough, the default recipe even says:

    # NOTE: the following library dependencies are unknown, ignoring: X11


Why is it ignoring x11? Coincidentally the code I'm testing this with
has a dependency on X11 and when I try building, bitbake throws out an
RDEPENDS warning.