8000 Yocto populate sdk by svlad-90 · Pull Request #161 · xen-troops/moulin · GitHub
[go: up one dir, main page]

Skip to content

Yocto populate sdk - #161

Merged
lorc merged 2 commits into
xen-troops:mainfrom
svlad-90:yocto-populate-sdk
Jul 21, 2026
Merged

lorc merged 2 commits into
xen-troops:mainfrom
svlad-90:yocto-populate-sdk

Conversation

@svlad-90
Copy link
Copy Markdown

yocto: add populate_sdk builder option

Allow Yocto components to request BitBake SDK generation by setting
populate_sdk to true. The default build path still invokes the
configured build_target directly.

When populate_sdk is enabled, pass -c populate_sdk together with the
build target through the generated Ninja rule. Keep target_images as the
declared outputs so callers can point Moulin at the expected SDK
installer path.

Document the new option and cover the generated bitbake arguments in the
Yocto builder unit tests.


version: bump version to 0.32

Taking into account added Yocto populate_sdk builder option and other
changes, bump the version up.

ghost left a comment
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are more pythonic ways to operate with lists ;)

With that fixed:

Reviewed-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>

Comment thread moulin/builders/yocto.py Resolved
Comment thread moulin/builders/yocto.py Resolved
@ghost
ghost force-pushed the yocto-populate-sdk branch 3 times, most recently from 7852bfd to b3820ba Compare July 21, 2026 11:48
ghost commented Jul 21, 2026
Copy link
Copy Markdown

boolean flag that runs BitBake's SDK population task instead of the default build task
can we run not instead, but as an additional task?

ghost commented Jul 21, 2026
Copy link
Copy Markdown

IIRC, the resulting behavior will be the same

@ghost
ghost force-pushed the yocto-populate-sdk branch from b3820ba to d96ed6b Compare July 21, 2026 13:26
ghost commented Jul 21, 2026
Copy link
Copy Markdown
Author

Hi @lorc, @andr2000, done.

No-SDK ninja graph:
domd-no-sdk-ninja-graph

Populate SDK ninja graph:
domd-with-sdk-ninja-graph

ghost commented Jul 21, 2026
Copy link
Copy Markdown

LGTM WRT logic implemented

ghost left a comment
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove unnecessary changes

Comment thread moulin/builders/yocto.py Resolved
Comment thread moulin/builders/yocto.py Resolved
Vladyslav Goncharuk added 2 commits July 21, 2026 18:10
Keep the normal Yocto image build as the producer for configured
target_images. When populate_sdk is enabled, add a separate Ninja step
that runs BitBake populate_sdk after those image outputs are up to date.

Record the SDK step with its own stamp so component targets depend on
both the image artifacts and SDK generation without treating SDK output
as a replacement for the image build.

Update the user reference and unit coverage for the generated two-step
build.

Reviewed-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
Signed-off-by: Vladyslav Goncharuk <vladyslav_goncharuk@epam.com>
Taking into account added Yocto populate_sdk builder option and other
changes, bump the version up.

Signed-off-by: Vladyslav Goncharuk <vladyslav_goncharuk@epam.com>
Reviewed-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
@ghost
ghost force-pushed the yocto-populate-sdk branch from d96ed6b to 726d348 Compare July 21, 2026 15:14
@ghost
ghost merged commit b9228f7 into xen-troops:main Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

0