[oe] Using EXTERNALSRC in practice

[Jérémy Rosen]

On 21/06/2016 00:02, Ulf Samuelsson wrote:
> Den 2016-06-20 kl. 15:58, skrev Jérémy Rosen:
>>
>>
>> On 20/06/2016 15:48, Ulf Samuelsson wrote:
>>> Den 2016-06-20 kl. 14:37, skrev Jérémy Rosen:
>>>>
>>>> On 20/06/2016 14:08, Ulf Samuelsson wrote:
>>>>> We have a meta-layer which builds the kernel.
>>>>>
>>>>> This contains among other things:
>>>>>
>>>>> FILESEXTRAPATHS_prepend_<machine> = "${THIS_DIR}/<machine>"
>>>>>
>>>>> SRC_URI = "git://<server>/<repo.git>;protocol=ssh;branch=<branch>"
>>>>> SRC_URI += "file://defconfig"
>>>>>
>>>>> PV = "...+git${SRCPV}"
>>>>> SRCREV = "<shaid>"
>>>>> ...
>>>>>
>>>>> Would like to have an option to build the kernel with external 
>>>>> source.
>>>>> That option should be easy to enable/disable
>>>>>
>>>> [skip the rest]
>>>>
>>>> What you are describing here is very close to how the devtool 
>>>> works. I think it can deal with kernel packages in its latest 
>>>> iteration
>>>>
>>>> did you have a look at that tool ? does it satisfy your need ? if 
>>>> not, what would it need to do what you want...
>>>
>>> No, where can I find more information?
>>>
>> The yocto manual has quite a section on that tool
>>
>>> The customer does not use the latest version of Yocto right now, so 
>>> that might be a problem,
>>
>> depends on how old "not the latest" is... but if you can do a sandbox 
>> with the latest version, you can probably see how devtool works and 
>> manually do the same thing...
>
> They use Yocto Layers, but not poky, so devtool is not present.
> Anyway, devtool will generate an absolute path, and I am looking for
> a recipe which uses a relative path to allow multiple yocto instances.
>
> projects
>         project1
>                 yocto
>                         kernelsrc + patchset1
>         project2
>                 yocto
>                         kernelsrc + patchset2
>         project3
>                 yocto
>                         kernelsrc + patchset3
>         project4
>                 yocto
>                         kernelsrc + patchset4
>
> Is there any way I can from inside a bbappend file find out the path 
> to that bbappend file?
>
>

${THISDIR} should be what you want, if I understand correctly...

>>>
>>> so It would be good to have an example ".bbappend" to start with.
>>>
>>> BR
>>>
>>> Ulf
>>>
>>>
>>
>