Skip to content
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.

Sign up for GitHub

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

Jump to bottom

subst is not a solution for the long path names on Windows #125

Merged
merged 2 commits into from
Oct 30, 2023
Merged

subst is not a solution for the long path names on Windows #125

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
08367f5
subst is not a solution for the long path names on Windows
ivmarkov Oct 28, 2023
9caa887
Update src/misc/troubleshooting.md
ivmarkov Oct 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions src/misc/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,11 +66,17 @@ For more information on toolchain overriding, see the [Overrides chapter][overri

### Long Path Names

When using Windows, you may encounter issues building a new project if using long path names. Follow these steps to substitute the path of your project:
```powershell
subst r: <pathToYourProject>
cd r:\
```
When using Windows, you may encounter issues building a new project if using long path names.
Moreover - and if you are trying to build a `std` application - the build will fail with a hard error if your project path
is longer than ~ 10 characters.

To workaround the problem, you need to shorten your project name, and move it to the drive root, as in e.g. `C:\myproj`.
Note also that while using the Windows `subst` utility (as in e.g. `subst r: <pathToYourProject>`) might look like an easy
solution for using short paths during build while still keeping your project location intact,
it simply *does not work*, as the short, substituted paths are expanded to their actual (long) locations by the Windows APIs.

Another alternative is to install Windows Subsystem for Linux (WSL), move your project(s) inside the native Linux file partition,
build inside WSL and only flash the compiled MCU ELF file from outside of WSL.

### Missing ABI

Expand Down