1

I'm currently working in a Yocto environment with multiple projects, each based on different layers. However, I always work on the same meta layer across these projects, with different recipes used in each project.

Here is the typical structure:

layers
|-- meta-my-layer
|-- meta-external-a
|-- meta-external-b

My code is delivered by meta-my-layer, but it is used in several instances of different Yocto projects. Each project has different external dependencies and supports different recipes. As a result, I am forced to use multiple instances of Yocto projects to work on my code.

Typically, I only need to download source code for one or two repositories, make changes, run tests, and deliver it. For this, I use Yocto's standard SDK.

However, due to the different external dependencies of each recipe/repository, I need multiple instances of Yocto's standard SDK. I am looking for a mechanism to create a single SDK that includes all the necessary tools to compile my code, while allowing me to switch sysroots to work on multiple projects without installing multiple SDKs.

What is the best way to achieve this in Yocto?

Improve this question
1
  • What prevents you from simply building an SDK that has all the dependencies of the other projects included? Also, if you'd build inside Yocto, I assume you already share the downloads and sstate-cache accross projects to speed it up? Commented Nov 3, 2024 at 16:37
Related questions
1
How can I make a yocto layer compatible with different releases that come with incompatible lib versions
1
Yocto recipe to manage Go dependencies with dep tool
0
Yocto Add own Header and Lib file's to sdk
Load 5 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.