Skip to content

Conversation

@fabiobaltieri
Copy link
Member

The Zephyr SDK install has a step where it tweaks the library paths of the host utilities so match the full install path and have them run without having to set LD_LIBRARY_PATH. In the current setup that path includes the repository name, which means that if the repository is renamed the cached SDK is going to end up having a non working path leading to a confusing error, typically dtc not found.

Move the SDK install to the home directory, so that the path does not depend on the repository name. The SDK is found using a CMake package so it can really be installed anywhere.

@fabiobaltieri fabiobaltieri force-pushed the sdk-path branch 3 times, most recently from 2d13ef3 to 89aa8fe Compare September 9, 2025 15:16
The Zephyr SDK install has a step where it tweaks the library paths of
the host utilities so match the full install path and have them run
without having to set LD_LIBRARY_PATH. In the current setup that path
includes the repository name, which means that if the repository is
renamed the cached SDK is going to end up having a non working path
leading to a confusing error, typically dtc not found.

Move the SDK install to the home directory, so that the path does not
depend on the repository name. The SDK is found using a CMake package so
it can really be installed anywhere.

Signed-off-by: Fabio Baltieri <[email protected]>
@fabiobaltieri
Copy link
Member Author

whatever

@fabiobaltieri fabiobaltieri deleted the sdk-path branch September 9, 2025 15:33
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.

1 participant