- This topic has 1 reply, 2 voices, and was last updated 1 hour, 31 minutes ago by
.
-
Posts
-
I have a new pristine laptop. I want to develop for ESP32, among other MCUs. On my previous laptop, I could not do that because the path to the ESP32 SDK/libraries was greater than 255 characters and I could not seem to change it, for some reason. So, now I want to install correctly. Should I just let VGDB install the ESP32 when I set up the project? Or should I install the ESP32 libraries and make sure it is a short path?
thanks!
Hi,
The absolutely safest way to go would be to install the Espressif’s VS Code extension, let it install all the necessary tools, and then use VisualGDB’s consolidated toolchain mode where it reuses the Espressif’s own tool layout.
So, if it works with the Espressif’s own VS Code extension, it will work with VisualGDB as well.
Also a heads up that we just finished porting a big chunk of the debugger-related functionality to CodeVROOM, and are expecting to release v0.6 with ESP32 debugging support in about a month. This way, you’ll be able to use a lot of VisualGDB’s debugging, navigation and settings editing GUI for the VS Code projects, without having to import them into the “Big” Visual Studio. It will also work directly on Linux and Mac where the 255-character path limitation does not exist.
- You must be logged in to reply to this topic.