Become a leader in the IoT community!
New DevHeads get a 320-point leaderboard boost when joining the DevHeads IoT Integration Community. In addition to learning and advising, active community leaders are rewarded with community recognition and free tech stuff. Start your Legendary Collaboration now!
we would like to make an operating system for it and store it for reproducability
How does one keep this information, so that we dont have to lug around Yocto layers everywhere we go,.
Not sure if I totally understand…
I have a build server. That has all the layers, configuration and resulting build images. The build server just stays in my office.
For a bespoke system, I will create my project with both third-party layers (Poky, OpenEmbedded, Raspberry Pi, etc) and my personal software layer(s) that contains the recipes for any software I have created. All of that gets stored in a repo as it is not very big. My `.gitignore` contains by build directory as that is huge and is reproducible.
To develop for the board, I would create the SDK to give me my development toolchain, and then update and commit my personal recipes as I go along.
So, the layers never leave my build server.
Ah I what artefact do you keep in that repo?
I’m assuming its some sort of build script that knows where to fetch layers from and if need be you can build from that. I think we are wanting to know what artefact to keep
like I guess how you can keep a docker file of an environment so you can share it.
With a Yocto Project, the build script is `bitbake` but it needs **all** the layers being used and the configuration files (`local.conf`, `bblayers.conf` the image BB files, etc).
The repo will contain all of the layers (I use git submodules for the third-party layers) and then I will create a templates dir that contains copies of my `local.conf` and `bblayers.conf` as `local.conf.sample` and `bblayers.conf.sample`
There is a diagram at https://siliconbladeconsultants.com/2024/05/16/structure-of-a-yocto-project/
So `New Project` is my repo. the `layers/third-party/XXX` are submodules and the `layers/project` I often just include in the main repo. Add a templates dir under `New Project` with the samples and include that in your repo tool.
**Exclude** the build directory, as that is reproducible
@superbike_z so I have found https://github.com/renesas-rz/meta-renesas which includes a layer for rzg2l
I guess we just have a build script that pulls from that.
I will demonstrate how I found it and would make use of it in the TechTips on Thursday 😄
that would be highly helpful
CONTRIBUTE TO THIS THREAD