Forum Replies Created
-
Posts
-
Hi,
The main reason why we did not add this feature is because VS is extremely slow when dealing with projects containing lots of source files. Simply opening a project containing the entire Linux kernel can take several minutes, adding the files one-by-one using VS interfaces would take more than 3 hours. The new recursive import feature solves this by closing the solution file, modifying it manually and reopening it, but that would still degrade project opening performance if lots of files are added. Please try using the new recursive import feature and if you don’t notice considerable delays when using it manually, let us know so that we could add an option to run it automatically when new files are detected.
Hi,
VisualGDB stores the list of source files in the Makefile itself that is shared between configurations. Configuration-specific flags are stored in
.mak files that are not affected by adding/removing source files. Hi,
In order to use GDB from a different machine you will need to set the ‘allow choosing build/clean/debug command hosts independently’ checkbox on the Project Settings page.
Note that if you don’t want to use gdbserver, you need to disable the ‘deploy executable’ checkbox on the Project Settings page and deploy it manually by adding a file transfer action to pre-debug steps.Hi,
That’s a bit strange as both tools use the same SSH engine. Are you using different users with different shells?
Hi,
Do you mean the toolchains for building windows applications with MinGW or are you talking about some embedded ones?
Hi,
We’ve added a new command called ‘import folder recursively’ to VisualGDB 4.2 that allows importing an existing folder with subfolders. You can get a quick impression of it by looking at our USB tutorial (http://visualgdb.com/tutorials/arm/stm32/usb/). You can just point it to the main project directory and it will add missing files to the project while keeping all the folder structure. Does that suit your needs or do you want something more sophisticated?
IntelliSense include directories are usually stored in the absolute form. You can see the exact form of them by looking at Visual Studio (not VisualGDB) project properties on the NMake page. If they contain absolute paths, you can change them to using $(ProjectDir) or modify them to point to the new location.
Hi,
IntelliSense directories are stored in Visual Studio Project Properties. The fastest way to copy them is to open the VS properties window, go to the NMake page and copy/paste them there.
Yes, we are working on an independent clang-based C++ IntelliSense engine, but it is not included in VisualGDB 4.2 and will be available at a later point.
VisualGDB automatically updates the list of all sources in Makefile, however it does not support excluding files for separate configurations yet. You won’t need to add all source files manually, you will only need to specify the files you want to exclude.
Hi,
Stdlib uses the space past the ‘end’ symbol to allocate buffers. BTW, we have updated our toolchain to include newlib without the standard syscall implementations. This should make it easier to define your own functions like _write() and control how exactly the IO is performed. Have a look at this tutorial: http://visualgdb.com/tutorials/arm/stm32/uart/ (note that you will need VisualGDB 4.2 beta 1 to use the raw terminal and the memory explorer).
If you want to hack the standard library further, you can get newlib sources, and rebuild it using MinGW and our toolchain:
mkdir newlib-build && cd newlib-build ../newlib-2.0.0/configure --target=arm-eabi --prefix=/c/SysGCC/arm-eabi --disable-newlib-supplied-syscallsNote that the build may take up to a day to complete, as the libraries will be built for each supported core.
Hi,
KGDB does not support debugging over network. The option you are mentioning is provided if you are using a VM that maps a guest COM port to a TCP connection on the host side or want to use a hardware COM-to-TCP bridge. In either way, the final connection to the target machine would still go through a COM port, so there is no performance benefit of mapping it to a TCP/IP port.
Hi,
How do you want to map a physical serial port to a tcp/ip port? Do you mean using a separate Linux machine connected to your target machine via a serial port and the development machine via ethernet?
Hi,
This is a recently added feature that was added to VisualGDB 4.2 that is currently in beta stage. Please install the latest beta to use it.
You can add exclusion lists to Makefile:
ifeq($(CONFIG),DEBUG) EXCLUDED_FILES = file1.cpp file2.cpp endifAnd then add the following code instead of the source_obj1 line:
all_source_files_filtered := $(filter-out $(EXCLUDED_FILES),$(all_source_files_filtered)) source_obj1 := $(all_source_files_filtered:.cpp=.o)
