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

Alexander Kanavin <[email protected]>
Newsgroups org.yoctoproject.lists.poky
Message-ID <CANNYZj_i=Wg_S2dXNRMUVZ0v0AzkWRwrNASBSxHMoe9SqDv4zQ@mail.gmail.com>
If SRC_URI is the same in multiple recipes then it will be cloned just once
and then reused from the download folder. Not sure what’s exactly happening
on your side, you need to demonstrate how that is not working, and where
mutiple clones are happening.

Alex

On Tue 5. Nov 2024 at 11.51, Steve via lists.yoctoproject.org <star=
[email protected]> wrote:

> Hello,
>
> Do have a bigger repo with submodules. Before each submodule gets its
> tag - so I did have mutliple recipes and need to fetch only parts.
>
> Now there is just one(!) tag for the main repo. Anyhow it was a pain to
> clone that repo and submodules multiple times.
> So I think about one recipe for just fetching data and multiple recipes
> that (depend on download-recipe)  work on the fetched data to compile
> parts?
>
> Problem is, that I have a huge git repo (with submodules / gitsm) and
> the download is via gitsm with branch and tag. Than the download folder
> is some recipe-name/<tag>+gitAUTOINC+<git-hash> and other recipes can't
> know that hash to access this folder.
>
> What is a solution for this? I think about creating a link to the level
> below - but that doesn't sound save or clever. What would your approach
>
> Thanks,
> Arno
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#13473):
> https://lists.yoctoproject.org/g/poky/message/13473
> Mute This Topic: https://lists.yoctoproject.org/mt/109403571/1686489
> Group Owner: [email protected]
> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [
> [email protected]]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.