You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing east with new sysbuild configuration showed, that east doesn't correctly create artefacts when sysbuild is enabled. This is probably due to difference in path inside build folder.
I noticed there is some handling of sysbuild path (using domains file) inside helper functions used when handling runners and debug configuration, same should be done for release command
Firmware/Software Version
Using NCS 2.7.0 with east 0.22.0
Hardware Version
N/A
To Reproduce
Enable sysbuild in your repository, you can do that by running west config --local build.sysbuild True
Run east release
Release will run normally, but it will only produce empty release folders and sub-folders (no artefacts inside).
Additional context
Folder structure change inside build folder is - build files are located one extra level of subfolders, what was before build/ is now build/<project_name>/
The text was updated successfully, but these errors were encountered:
Describe the bug
Testing east with new sysbuild configuration showed, that east doesn't correctly create artefacts when sysbuild is enabled. This is probably due to difference in path inside build folder.
I noticed there is some handling of sysbuild path (using domains file) inside helper functions used when handling runners and debug configuration, same should be done for release command
Firmware/Software Version
Using NCS 2.7.0 with east 0.22.0
Hardware Version
N/A
To Reproduce
west config --local build.sysbuild True
east release
Additional context
Folder structure change inside build folder is - build files are located one extra level of subfolders, what was before
build/
is nowbuild/<project_name>/
The text was updated successfully, but these errors were encountered: