On 22/01/2020 17.59, Richard Purdie wrote:
> On Wed, 2020-01-22 at 16:39 +0000, Rasmus Villemoes wrote:
>> On 22/01/2020 16.50, Richard Purdie wrote:
>>> On Wed, 2020-01-22 at 15:46 +0000, Rasmus Villemoes wrote:
>>>> On 22/01/2020 15.35, Richard Purdie wrote:
>>
>> I can't be the first one to want to substitute bitbake variables in
>> various source files, without necessarily knowing upfront which
>> variables might appear.
>>
>> So thinking out loud (and apologies if this is very silly): Would it
>> be
>> possible to implement some auto-deps class 
> 
> Why not do what I already suggested?

Sorry, I'm probably a bit slow. Do you mean this part

  Well, if you have the expansion, just put it in a variable the
  function references...

? That was in response to something that I since discovered wouldn't
work [because d.getVar(line) doesn't magically feed back the deps info
as my naive experiment led me to believe], so I must admit I didn't
think too hard about it. But, I don't see how slurping in the file(s),
doing the expansion, and putting the result in some variable that I then
do a (dummy?) reference to would help teach bitbake which variables were
used during the expansion.

> I suspect rather than a class you're looking for a helper function in
> lib/oe to call into? Just move my suggested function somewhere there?

Well, yes, I'm certainly looking for or asking for a library function
that will do what I want. But I'm not really seeing how to implement
that. I do now see how the variable dependencies must be known at parse
time.

Rasmus
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48089): https://lists.yoctoproject.org/g/yocto/message/48089
Mute This Topic: https://lists.yoctoproject.org/mt/69979676/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to