Devtool debug build support and update dependencies #370
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
deribaucourt
force-pushed
the
devtool-debug-build
branch
2 times, most recently
from
e381169 to
3fdc528
Compare
deribaucourt
requested review from
WilsonZiweiWang and
idillon-sfl
and removed request for
idillon-sfl
deribaucourt
force-pushed
the
devtool-debug-build
branch
2 times, most recently
from
cbbb429 to
e62d734
Compare
semver will be used to check the Yocto version.
This will allow other tests to use a real bitbake folder when needed.
We'll use the bitbake version to make some features available or not based on their support in the bitbake version. The necessary ajustments were made to keep compiling. The unknown version is '', making it easy to check if it was found or not. For the tests, rather than defining an empty version everywhere, I used `as BitbakeScanResult` to mock only the attributes needed for each test. This means less hassle next time we change the scan result structure again.
This is the easiest way to get the bitbake version that we have access to from the settings. It is super fast since it doesn't need to start bitbake. Bitbake versions can be correlated to poky versions using the Yocto Wiki Release page: - https://wiki.yoctoproject.org/wiki/Releases
We now have access to the bitbake version through the project scan. This allows us to check if the devtool ide-sdk command is available without running devtool which is a lot faster.
The devtool ide-sdk tests need to get access to a bitbake version that was throwing an exception if not defined.
By default, we'll turn on the new devtool debug build feature. This allows accessing the debug symbols. Because this is a new default behavior, we'll add a new setting to disable this feature. The necessary adjustments are made to compile the code by including a boolean to the build settings.
This new devtool feature allows to add the debug symbols when building the devtool recipe. It is enabled by default in the previous commit.
In eSDK mode, we don't have access to the bitbake version. Revert to the previous behavior of checking the availability of devtool ide-sdk and devtool debug-build based on the help message.
deribaucourt
force-pushed
the
devtool-debug-build
branch
from
e62d734 to
e48a6c4
Compare
WilsonZiweiWang
approved these changes
Jan 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #361