-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: "Variable ZEPHYR_TOOLCHAIN_VARIANT is not defined" #30713
Comments
I was just searching for the same issue. But current documentation does not mention it. Probably at some point all the build tools detected Zephyr SDK automatically, so they removed the mention about setting that variable. |
The getting started guide doesn't currently document that the ZEPHYR_TOOLCHAIN_VARIANT env var needs to be set even in the case of using the Zephyr SDK. Add mentions to it in both the short and long guides. Fixes zephyrproject-rtos#30713. Signed-off-by: Carles Cufi <[email protected]>
Correct. CMake handles this automatically when using newer Zephyr SDK's. (from 0.11.3 and beyond). This issue is related to running twister, which seems to also test for the Toolchain variable, so i'm looking into aligning code so this can be done in a single place. |
if trying to build using west or CMake / Ninja, then you should not see this issue. |
west+CMake+Ninja works OK, as expected. |
Fixes: zephyrproject-rtos#30713 Now using the common script `verify-toolchain.cmake` for verifying toolchain settings. Signed-off-by: Torsten Rasmussen <[email protected]>
Fixes: #30713 Now using the common script `verify-toolchain.cmake` for verifying toolchain settings. Signed-off-by: Torsten Rasmussen <[email protected]>
Describe the bug
Imaged a new Ubuntu machine and followed all the directions on https://docs.zephyrproject.org/latest/getting_started/index.html
I used the default location for the SDK.
Unfortunately, this page doesn't mention that ZEPHYR_TOOLCHAIN_VARIANT has to be set for
twister
to work.To Reproduce
Expected behavior
Doc page would mention this detail.
Impact
Minor
The text was updated successfully, but these errors were encountered: