Re: [poky] One recipe for fetch a bigger repo, multiple recipes to build parts of it

On 11/6/24 11:57, Richard Purdie via lists.yoctoproject.org wrote:
> On Wed, 2024-11-06 at 11:49 +0100, Steve via lists.yoctoproject.org
> wrote:
>> Well, the idea with work-shared sounds good. But I didn't figure out
>> what param makes fetcher to checkout into work-shared?
>> Just modify $S doesn't help, it is checked out still to tmp/work/<my-
>> arch>/my-fw/${TAG}+git${SRCPV}/git
>> To workaround that for the moment I create a link, but that doesn't
>> work reliable.
>
> The way gcc handles it is a single recipe responsible for the source
> (gcc-source) which the other recipes all then depend upon.
>
> The kernel works a bit differently as the kernel creates the shared
> source and then the other recipes depend on virtual/kernel.
>
> Both approaches have complications and end up needing to be special
> cased in various places (archiver.bbclass for example) so they're
> definitely advanced usage.
>
> Cheers,
>
> Richard

Follow the path of recipes of kernel or gcc is rather frustrating for a
newbee. Having a recipe just for download seems not a good idea,
dependencies of recipes seem not to work, as download recipe creates no
real output.
What I did now, I created one standard recipeA that checks all out and
really does something that is needed
The other recipesB,C,... depend on recipeA and in their do_install (I
just want to pick some files out of repo that is checked out in recipeA)
I figure out the folder name by just ignoring the (for B, C, D...)
unknown git hash.
That seem to work.
Best regards