- This topic has 3 replies, 3 voices, and was last updated 2 days, 2 hours ago by
.
-
Posts
-
Noticed there was an update to VisualGDB to v6.0R7 (build 5333). I installed that first by itself, then restarted Visual Studio. I thought maybe the install problem of the latest Arduino ESP32 package(v3.1.3) would be fixed, but there’s there’s still a problem with long paths as per enclosed when I tried to install it. Why Arduino has to make such long path names is beyond me~~~.
Hi,
That’s beyond us as well. The latest ESP32 Arduino package indeed includes some rather long paths. They seemingly come from some 3rd-party code that Espressif bundled with their package and don’t seem to be actively used (unless you specifically want to include some connectedhomeip headers).
We looked into it earlier when the same package was causing other issues, and it turned out that Arduino IDE just silently ignores the long paths. So, we updated VisualGDB to show the list of the files it could not install, but otherwise do what the Arduino IDE does. If you don’t need these headers, you can just ignore the warning and go ahead. Otherwise, you can try convincing Espressif to move the affected folders within their package, because they would not work on Windows regardless of the used IDE.
fwiw, still occurring with the latest update today (ESP32 3.3.1) See attached
VisualGDB 6.0R8 (build 5338)
Looks like of the 170+ problems, included is at least the ESP Matter Connected Home stuff. Undesired to just ignore.
Perhaps an alternative install location can be used?
There’s a Windows fix that I personally choose not to use, as I also test my own distributions for other things:
https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry
Hi,
Last time we checked, it could be safely ignored. If you install the same packages with Arduino IDE, it just silently skipped these long paths, and everything still got built just fine. So, we just replicated its behavior, but added a warning just in case.
We would advise against registry hacks, as it could have some weird side effects (e.g. cause some internal errors in gcc). You can also try convincing Espressif to update their package structure, as it might eventually start causing problems for Windows users.
- You must be logged in to reply to this topic.