tools: add build path support on host_info tool#18919
Merged
linguini1 merged 1 commit intoMay 20, 2026
Merged
Conversation
Adds a build_path argument for when CMake builds are used. This solves a problem when building the nxdiag tool with CMake. Signed-off-by: Filipe Cavalcanti <filipe.cavalcanti@espressif.com>
eren-terzioglu
approved these changes
May 20, 2026
xiaoxiang781216
approved these changes
May 20, 2026
linguini1
approved these changes
May 20, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds a build_path argument for when CMake builds are used.
This solves a problem when building the nxdiag tool with CMake.
This is related to this PR on nuttx-apps.
Impact
Impact on user: No.
Impact on build: If using CMake, especially with Espressif devices, this will fix a problem related to the script path. Does not affect Make builds.
Impact on hardware: No.
Impact on documentation: No.
Impact on security: No.
Impact on compatibility: No.
Testing
Build with Make works fine, with CMake it would fail since build and source directory differs.
Building
Make example:
CONFIG_SYSTEM_NXDIAGandCONFIG_SYSTEM_NXDIAG_ESPRESSIFCMake example:
CONFIG_SYSTEM_NXDIAGandCONFIG_SYSTEM_NXDIAG_ESPRESSIFRunning
Make:
python3 -B tools/host_info_dump.py /home/fdcavalcanti/nuttxspace5/nuttx --target_infoCMake:
python3 -B tools/host_info_dump.py /home/fdcavalcanti/nuttxspace5/nuttx -b build --target_infoOn both cases output works fine.