-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
twister: problem with build specific samples on Windows OS #41929
Labels
area: Twister
Twister
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Comments
gopiotr
added a commit
to gopiotr/zephyr
that referenced
this issue
Feb 7, 2022
Add possibility to create shorter build paths when --short-build-path option is enabled. This can help during run Twister on Windows OS and building programs by CMake which has a problem when paths with building files are too long. The solution based on symbolic links which help to connect "traditional" long paths with shorther one like: "twister_links/test_0". Fixes zephyrproject-rtos#41929 Signed-off-by: Piotr Golyzniak <piotr.golyzniak@nordicsemi.no>
gopiotr
added a commit
to gopiotr/zephyr
that referenced
this issue
Feb 17, 2022
Add possibility to create shorter build paths when --short-build-path option is enabled. This can help during run Twister on Windows OS and building programs by CMake which has a problem when paths with building files are too long. The solution based on symbolic links which help to connect "traditional" long paths with shorter one like: "twister_links/test_0". Fixes zephyrproject-rtos#41929 Signed-off-by: Piotr Golyzniak <piotr.golyzniak@nordicsemi.no>
nashif
pushed a commit
that referenced
this issue
Feb 22, 2022
Add possibility to create shorter build paths when --short-build-path option is enabled. This can help during run Twister on Windows OS and building programs by CMake which has a problem when paths with building files are too long. The solution based on symbolic links which help to connect "traditional" long paths with shorter one like: "twister_links/test_0". Fixes #41929 Signed-off-by: Piotr Golyzniak <piotr.golyzniak@nordicsemi.no>
andrea-pallini
pushed a commit
to andrea-pallini/zephyr
that referenced
this issue
Feb 23, 2022
Add possibility to create shorter build paths when --short-build-path option is enabled. This can help during run Twister on Windows OS and building programs by CMake which has a problem when paths with building files are too long. The solution based on symbolic links which help to connect "traditional" long paths with shorter one like: "twister_links/test_0". Fixes zephyrproject-rtos#41929 Signed-off-by: Piotr Golyzniak <piotr.golyzniak@nordicsemi.no>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: Twister
Twister
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Describe the bug
During building samples or tests by Twister on Windows OS some of them cannot be build due to the fact, that path of directories created for build place is too long. This problem is connected with path limit on Windows OS, which can be remove (since Windows 10) but it seems that still some programs like CMake has problem with such limit. This problem do not occur, when those samples and tests are built by west tool (path of build directory is shorter).
To Reproduce
Steps to reproduce the behavior:
C:\tb\nrf5340dk_nrf5340_cpuapp\samples\subsys\portability\cmsis_rtos_v1\timer_synchronization\sample.portability.cmsis_rtos_v1.timer_synchronization
build directory).x.y.z
. This cause, that path of build directory is shorter:C:\tb\nrf5340dk_nrf5340_cpuapp\samples\subsys\portability\cmsis_rtos_v1\timer_synchronization\x.y.z
.C:\zephyrproject\zephyr\build
)nrf5340dk_nrf5340_cpuapp_ns
,nrf5340dk_nrf5340_cpuapp
ornrf5340dk_nrf5340_cpunet
:Expected behavior
The path length of sample or test or testscenario name should not impact on build result.
Impact
Twister cannot be used to build all samples or tests on Windows OS
Environment (please complete the following information):
Additional context
I already have proposition for fix this bug and I will create PR soon
The text was updated successfully, but these errors were encountered: