[support]

Hi,

It looks like you have upgraded to CMake that does not support the server mode. Are you using the CMake that is shipped with Cygwin?

If yes, please try building it from sources as described here: http://visualgdb.com/documentation/cmake/annotations/

Additionally to enabling the advanced CMake mode, using our CMake fork will let you step through the CMakeLists.txt files, so you will be able to diagnose CMake-related issues faster.

[support]

Just wanted to share an update: we have added a CMake script debugger to VisualGDB 5.4 Preview 7, so you can easily step through ESP-IDF’s CMakeLists to quickly understand what is going on (see the announcement). In our experiments, the project() command is actually redefined by the IDF itself, in a way that does not use the VERSION argument. If it worked under the regular Visual Studio, you might have used a different ESP-IDF build that did not redefine it, or have patched it yourself.

[support]

Hi,

Sorry, this isn’t supported. VisualGDB projects refer to toolchains by unique IDs that are automatically resolved by VisualGDB when you open the project.

The path (neither relative nor absolute) is never hardcoded in the project itself. This allows opening the same project on multiple machines with different toolchain installation directories without modifying anything.

If you want to avoid installing the toolchain on each machine manually, you can simply create a .reg file that will register the toolchain location from your repository on each machine (see HKEY_CURRENT_USER\Software\Sysprogs\GNUToolchains) or rely on the VisualGDB Team Settings mechanism to deploy the toolchain automatically.

[support]

Hi,

If you are using MSBuild, you can override the object file directory for each file using the regular VS properties. Alternatively, please consider switching your project to CMake with the Advanced CMake Project Subsystem. It automatically handles such cases and also builds the projects much faster.

[support]

Hi,

Good to know you have found the download link. Let us know if you need any further help with this.

The build errors might be caused by the Project Properties -> Path Mapping -> GDB Path Style setting. It should be set to “Use toolchain default” in order to automatically switch between Cygwin-based toolchains (R12 and earlier) and MSYS2-based toolchains (R13).

[support]

Hi,

No problem, we will help you get it to work. The problem could be caused by 2 issues: a corrupt toolchain, or incompatible settings cached in the projects.

Please try installing the R12 toolchain and VisualGDB 5.4 Preview 6. Then try creating a new project. If it builds works, please open one of the old projects and check the VisualGDB Project Properties -> Path Mapping -> GDB Path Style setting. It should be set to “Use toolchain default”.

If the old projects still don’t work, please try comparing the .vgdbproj files in a diffing tool (e.g. KDiff3) or simply import the old projects via the ESP32 project wizard to regenerate the settings file.

[support]

Hi,

Please try cleaning the project via Build->Clean All. If it doesn’t help, please remove the toolchain completely and install it again via VisualGDB Package Manager.

It should get rid of any conflicting files and get the project to build again.

[support]

Hi,

Most likely the same source file got included in the project twice (or multiple source files with the same name got included, causing obj file conflicts). The exact steps to fix this depend on your project type, but normally searching for the file name shown in the error message in Solution Explorer should help you narrow it down (ensure that only 1 instance is included in the project).

[support]

Hi,

Thanks for sharing the details. The Wi-Fi driver is included in the ESP-IDF itself (the ESP32 SDK provided by Espressif, the chip vendor) and does not come from us. Hence please consider creating a topic on the ESP32 forum, or simply downgrade to an ESP-IDF version (and/or toolchain) that works.

[support]

Hi,

Thanks for clarifying this. For MSBuild projects you can use the regular Visual Studio property pages to configure various compiler/linker options. The easiest way to transfer them to the Release configuration would be as follows:

1. Open VS project properties for the Debug Configuration.
2. Locate the relevant setting and copy it to Clipboard.
3. Switch the “Configuration” view in the Properties window to “Release”.
4. Paste the setting value from the Clipboard.

BTW, you can switch the VS property window to “All Configurations” mode to simultaneously edit properties for both Debug and Release configurations.

[support]

Hi,

Sorry, we are not affiliated with Espressif and are only able to help with issues specific to our products. For general ESP32-related inquiries, please consider creating a post on the ESP32 forum. It is maintained by Espressif and they should be able to answer questions regarding the release schedules, plans and compatibility between SDKs.

[support]

Hi,

Sorry, looks like there is still some misunderstanding going on. We will try to clarify:

• VisualGDB builds the ESP32 projects using the ESP-IDF (official SDK from Espressif, the ESP32 chip vendor).
• The latest stable release of ESP-IDF is v3.1. It works out-of-the-box, but does not include the http_server example.
• The experimental ESP-IDF 3.2 (the master branch) includes http_server, but is currently broken (if try building it via command-line using the official toolchain from Espressif, you will run into the same problems).

 

Hope this explains. Let us know if you have further questions.

You should be able to copy the contents of the Output window by pressing Ctrl-A, Ctrl-C. If you want to share a long log, please consider attaching it as a text file instead of inserting it into the post.

[support]

Hi,

Sorry, it’s hard to give any advice without seeing the exact error messages. The easiest way to get it to work would be to:

1. Install VisualGDB 5.4 Preview 6.
2. Completely remove your ESP32 toolchain and install it from scratch via VisualGDB Package Manager.
3. Create a new project using the v3.1 checkout that is included in the toolchain.

This is the scenario that we test as a part of our pre-release tests, so it should work out-of-the-box.

[support]

Hi,

Sorry, we don’t have any current plans for overriding the Visual Studio popup mechanism to support popups on the ‘(‘ symbol.

It also looks like your trial period has expired. Please feel free to get back to us once you purchase a license and we will be happy to discuss possible workarounds to display the information you would normally see with this popup.

[support]

Hi,

Nope, sorry. The CMake projects have a fundamentally different structure from the regular VC++ projects, so the regular VC++ IntelliSense won’t recognize them. Please consider filing a feature request with JetBrains. On our side we will be more than happy to provide a public interface for them to query the include paths and other compiler settings, but we need someone from them to modify Resharper to actually use this interface.

[Author]

Posts