Forum Replies Created
-
Posts
-
I confirm the issue is fixed in VisualGDB-5.5.8.3747. Thank you very much for your great support!
Udo
Just tried it and it works as expected. The options you added in project properties make sense to me. Great job!
I really appreciate your support. Unbelievable how fast you react on a feature suggestion. This is the second time I experienced this. First time I suggested separate Additional Options for C and C++. Will think about more feature ideas 😉
Thanks again.
Udo
Hi,
Thanks for your comments. To implement your first suggestion, I roughly followed these instructions and redefined the BuildDependsOn property. This works. I can access %(ClCompile.AdditionalIncludeDirectories) and %(ClCompile.PreprocessorDefinitions) and use them in my custom prebuild target. There are still a couple of details to solve, e.g. transforming the semicolon-separated list of path items into a sequence of -I options for gcc.
What I really want to achieve is preprocessing my linker script. I’m wondering if this wouldn’t be a nice feature for VGDB to support out of the box. I will open a separate topic to discuss this.
Udo
Hi,
I do have the same problem and found this thread. I want to use gcc option -fno-use-cxa-atexit which is a very useful one for embedded C++ projects. I added -fno-use-cxa-atexit in project properties under C/C++ – Command Line. The project contains C++ and C files. For C files this option causes a gcc warning:
gcc command line option ‘-fno-use-cxa-atexit’ is valid for c++/objc++ but not for c
which cannot be suppressed with another option.
Is there any chance that you will add this option to the prop page, or filter it out automatically for C files?
My suggestion is to enhance the C/C++ – Command Line dialog to offer separate options for C and C++. Alternatively, you could support some proprietary syntax to support filtering of options specified under Additional Options, for example: $CPPFLAG(-fno-use-cxa-atexit) $CFLAG(-some-useful-option).
Udo
Thanks for your reply. I understand that the Intellisense engine requires a different set of options. However, in my case I had to manually adjust basic editor settings such as tab size manually. I do not remember exactly what I had to tweak but I’m sure about the following observations:
I installed VisualGDB over an existing VS2015 installation with the following settings under
Tools->Options->Text Editor->C/C++->Tabs: Indenting = Block, Tab Size = 4, Insert Spaces.After that under Tools->Options->Text Editor->C/C++ (VisualGDB)->Tabs I had:
Indenting = Smart, Tab Size = 4, Keep Tabs.Also settings from the General section were not imported by VisualGDB. I have “Line numbers” checked which I had to redo in the (VisualGDB)->General section.
Also Text Editor->C/C++->Formatting->General->”When I past: Do nothing” was not converted to
Text Editor->C/C++ (VisualGDB)->Formatting->Auto-format when pasting text.I think it’s okay to offer a different set of Intellisense options. But VisualGDB should not duplicate editor and auto-formatting settings. The editor settings reflect my personal preferences which should be in effect when I work on any C++ code. Whether the target is embedded or PC does not make a difference here. In other words, such settings are language-specific but not target-specific.
Udo
