Hi Alex,
Thank you for your response.
I’m working with the Marvell Armada 7040 board and haven't reached out to
Marvell for support yet.
While integrating the meta-marvell layer from the krogoth branch into the
scarthgap Yocto workspace, I encountered several syntax errors, which I’ve
since r
Yes. You can build many images with the same bitbake invocation, they’re
defined with recipes, and the application recipe is built only once for all
of them. Any image specific variable including the image name is visible
only from the tasks of the image recipe.
Alex
On Tue 10. Sep 2024 at 14.55,
Hi Alex,
So, am I understand correctly, it is impossible to import destination image
name inside particular application recipe?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63813): https://lists.yoctoproject.org/g/yocto/message/63813
Mute This To
You need to make two slightly different recipes (put common bits into
an .inc), and then install one or the other to the respective images.
Alex
On Tue, 10 Sept 2024 at 13:16, Gennady Abramov via
lists.yoctoproject.org
wrote:
>
> Dear community,
>
> I'm trying to build A+B+Data distro + update
Dear community,
I'm trying to build A+B+Data distro + update distros using RAUC and populate
Data partition with default configuration files.
Thus, I want a particular recipe, if "full" image build, install particular
default configuration files, and if "update" image build, not to do that,
On Mon, 9 Sept 2024 at 16:24, Radoslav Pesek via
lists.yoctoproject.org
wrote:
> thanks for the explanation. I checked the slides, watched the video and tried
> this workflow (partially - didn't try deploy-target and finish), and it seems
> to work, but still have some questions:
> * Alex, you w
