[viordash]

Thank you, you have solved my problem.
I have added this additional GDB commands to executing after selecting a target
– set print repeats 200
– set print elements 2000
– set print sevenbit-strings off

[viordash]

Many thanks!
The new version solved my problem with CMakeLists formatting.

Regarding the recompilation of ESP-IDF after each commit, the problem is solved by adding the file $(IDF_PATH)/version.txt in which the IDF release version is written.
the solution was found at https://docs.espressif.com/projects/esp-idf/en/v3.3/api-guides/build-system.html

[viordash]

Thanks,
Sorry to be too hasty, I know your rules a little better now.
I will try to figure out the espressif problem on my own.

With regards to CMakeLists, I mean the first line with a list of source files used (idf_component_register (SRCS …), my list of files always goes on one line, and when I try to manually format and make a new line, it fails, when a new file is added into the project, the list of files is automatically changed back to a single line.
Take a look at Screenshot_3.png, I created a project from a template and added some new files
This problem prevents the use of automatic merge in git, it does not know how to merge line-by-line changes

Attachments:

You must be logged in to view attached files.

[viordash]

Should I expect an answer from you here? or make a new ticket?

[viordash]

>>1. The recompilation is managed by the ESP-IDF itself.

I found that full recompilation depends on the commit in git, after each commit, complete rebuild of the project occurs. Is there any way to avoid this?

Is there a setting like “VisualGDB -> Files -> Max. Items per Makefile line” for ESP-IDF project (cmake)? This is necessary for convenient resolution of merge conflicts.

[viordash]

Very sorry,
In Makefile projects I find the most responsive interface.
I’m trying to translate into CMake, but it seems to me that his work is more inconvenient and time-consuming.
MSBuild is not suitable, since the CI/CD build on the machine on Linux.

[viordash]

Hi!

VisualGDB 5.6 (Beta 4, build 4305).
Sometimes, when selecting something from the intellisense dropdown list, no text is inserted after pressing the Enter key. And this time only TAB helps. Unfortunately, I cannot give the exact steps to reproduce this problem, this happens in GNU Make or ESP-IDF projects (cmake)

[viordash]

Thanks, I will wait for updates.

The need to switch the configuration in the VS manager, and not in the VisualGDB Project Properties window is a little inconvenient, since I will need to close the properties window

[viordash]

Thank, but I haven’t had a complete success so far.

$ (ConfigurationName) is not resolved and a file with the verbatim name “sdkconfig-$(ConfigurationName)” is created. I tried to solve this problem by writing “sdkconfig-debug” and “sdkconfig-release” values in the SDKConfig File field. These files have been created.
But I also cannot make full use of the various configurations.
Switching the configuration in VisualGDB Project Properties -> ESP-IDF Project does not visually affect data changes in this window, although the contents of the “sdkconfig-debug” and “sdkconfig-release” files are different.
Building is now done differently for different configurations, but there is no way to edit their settings in the UI

With Custom build steps all norm

[viordash]

Please check the status of the licenses associated with me. They should already be updated.

[viordash]

The “Custom Build Steps” are also independent of the selected Configuration and are always the same.

• This reply was modified 3 years, 3 months ago by viordash.

[viordash]

Hi,

All licenses associated with me will be updated soon

Thanx

[viordash]

Found some dependency on the presence of CustomTargetProviders (TelnetTarget) in the project, even if this provider is not currently used (deploy and debug occurs via ssh on main build machine). If the solution is reopened and the debug test is performed first only for the project with ssh, then debugging works

[viordash]

Hi,

I’ve updated both, VisualGDB 5.6 (Beta 4 build 4305, taken from https://sysprogs.com/w/forums/topic/intellisense-issue-in-visualgdb-5-6-beta4/) + Microsoft Visual Studio Community 2019 Version 16.11.1

But the error is still present

• This reply was modified 3 years, 4 months ago by viordash.

[viordash]

updates!
With msbuild type project the error still exists.
Normal debugging (Start debugging from menu) works fine.

[Author]

Posts