-
Notifications
You must be signed in to change notification settings - Fork 12
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
Can't building the TF-M Regression Test suite #117
Comments
Hi @jeromecoutant, I can't reproduce this issue locally. Could you please try a clean fetch & build:
and see if the issue persists? |
Here is what I have done:
Maybe it is the famous long path windows issue..... |
Sounds likely. Have you tried putting mbed-os-tf-m-regression-tests in a shallower directory on your PC? |
OK, I can try, but it is not the solution... :-) |
No, I couldn't make it work at /c/ level |
The CMake build paths of trusted-firmware-m (TF-M) are rather deep. When I built trusted-firmware-m manually on Windows, the path was borderline too long and moving the repository by one directory or so changed the result... Sometime CMake warns you about paths lengths being too long on Windows, earlier in the log. Unfortunately there's not much we can do on the Mbed OS side, as we're just letting the trusted-firmware-m repo build itself. I'll raise a suggestion to shorten paths to the TF-M team. Meantime, could you please try removing the path restriction as per the Windows 10 documentation from Microsoft? Please let us know if it works for you, thanks.
Was it the same failure? |
Patch for path restrictions doesn't work....
Could you check |
@jeromecoutant Thanks for the suggestion, I'll try to see what's the best we can do. The main thing is, CMake generates Ninja files and ninja does the actual build. But Ninja doesn't support long paths yet, someone has a PR open for that: ninja-build/ninja#1939 Even if the system-wide path restriction is remove, that seems not enough - applications also need to be adjusted to take advantage of the long path support. (Apparently "make" doesn't support it either, so switching from ninja back to make doesn't help either.) |
Hi @jeromecoutant, for now if you both rename mbed-os-tf-m-regression-tests to a shorter name (e.g. mbed-tf-m) and put it in a short path (e.g. /c/work/), it'll likely let you proceed with the work at least. Before ninja properly supports long paths on Windows. |
This workaround is OK:
Maybe it could be documented or included in the python script ? |
Following https://github.com/ARMmbed/mbed-os-tf-m-regression-tests#building-the-tf-m-regression-test-suite
I tried
python3 build_tfm.py -m ARM_MUSCA_B1 -t GNUARM -c RegressionIPC
But it is failing:
The text was updated successfully, but these errors were encountered: