-
Notifications
You must be signed in to change notification settings - Fork 175
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
compile - files with CreateProcess error (windows) - path max length limitation #6
Comments
It would be great if you could help find the workaround yotta used! :) |
@screamerbg : use the Unicode process creation API in python (32k path limit versus 260 characters path limit). |
yotta workaround has been applied, yet compiling Thread and everything else generates 38000 symbols link command. This will be addressed with response files. |
Please provide commit/PR reference, or might be better to reference this via commit message, we can track/review changes done for this issue. |
Hitting this now too. I'd be happy to help review the commit/PR when its ready |
I am hitting the error even with a folder C:/5 for morpheus code example. It used to be fine before we merge few more modules in, now I can't link a program :( This is a blocker for me now.
|
Unless someone objects, I'll try to fix this today, at least for GCC, since it's clearly a blocker for some people. |
Workaround until this is fixed: try running in a Linux VM. |
@bogdanm https://msdn.microsoft.com/en-us/commandline/wsl/about (run native Ubuntu on Windows - no VM needed any more) |
@meriac, I think that only works in Windows 10 though :( |
A partial fix for the command line problem is in ARMmbed/mbed-os#43. It's partial because it only covers linking. That seems to work for now, but in the future it might have to be extended for compilation too. In any case, I'm closing this for now, since this particular issue is solved by that commit. |
Working now, the example which failed previously. Thanks |
It seems like I am hitting windows path limit. This was a problem with yotta, which I recall added unicode paths support, to overcome this?
vs
The text was updated successfully, but these errors were encountered: