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

On 8 Nov 2024, at 06:33, Arno Steffens <[email protected]> wrote:
> 
> On 11/7/24 22:41, Ross Burton wrote:
>> On 6 Nov 2024, at 17:42, Steve via lists.yoctoproject.org <[email protected]> wrote:
>>> 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.
>> 
>> Where are you picking the files from in the other recipes?
>> 
>> Ross
> 
> Not sure I understood your question.
> RecipeA fetches data of repo and uses few files out of it to become part
> of the final image (lets assume a lib)
> Also it save a filename with location of this fetched git repo folder in
> tmp/work (my_common_git_repo_location.txt)
> RecipeB,C,D ... depend on RecipeA and read that file and can use data
> from that. Each recipe uses other files out of this repo above.
> That works so far.

You’ll need to be careful with your task dependencies and how work dir behaves on clean builds with sstate involved.  

Ross