tests: llext-edk: get the Zephyr SDK path from build_info.yml
#83661
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The LLEXT EDK test works by packaging an EDK and then testing its functionality to build the extension in an external CMake build step. That
CMakelists.txt
file currently references the required tools using theZEPHYR_SDK_INSTALL_DIR
environment variable, which must be manually set by the user. This was causing issues in peculiar situations like this one CI run from #82990.This change modifies the test to read the newly added
build_info.yml
file, generated by Zephyr during the first build step. This allows to set theZEPHYR_SDK_INSTALL_DIR
environment variable automatically based on the (possibly auto-discovered) SDK path.