Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Language Settings (was: CDT survey)

Includes, Symbols, Libraries and Library Paths tabs in Paths and Symbols page contain no useful information when MBS language settings provider is disabled. To reduce UI clutter and to avoid user confusion, it makes sense to hide these tabs when MBS LSP is disabled. I've created for that.


On Mon, Jul 29, 2013 at 6:44 AM, Andrew Gvozdev <> wrote:
Hi Christian,
Both "C/C++ Build" > "Settings" and "Paths and Symbols" represent settings from MBS. If you add/edit entries in either one they end up in the toolchain definition supplied by cdt.managedbuild plugin. "Paths and Symbols" also would show read-only entries captured by older scanner discovery ("C/C++ Build" > "Discovery Options").

The "C/C++ General" > "Preprocessor Include Paths, Macros etc." is cdt.core. It combines those from MBS, new scanner discovery and also UI for adding user entries. It does not need managedbuild plugin and so can be used with CDT builder which does not use MBS.

I agree that it is confusing. What about moving  "Paths and Symbols" under "C/C++ Build" and renaming it to "MBS Paths and Symbols"? Would it at least alleviate the confusion?


On Mon, Jul 29, 2013 at 2:21 AM, Christian Walther <walther@xxxxxxxx> wrote:
kesselhaus wrote:
> I just found something else strange:
> If I add something in C/C++ General -> PreProcessor Include Paths, Macros, etc. page like a lib or include path, why they are not also taken into account for compiling? I have to add them again in the C/C++ Build pages for the compiler/linker, but is this really intended?

I have been confused by this as well. Let's see if I got this straight: The "C/C++ General" > "Preprocessor Include Paths, Macros etc." page is for getting settings *from the compiler to CDT*. It's the sucessor of "scanner discovery". You should only make manual entries there for things that the compiler already knows about by some other way (but CDT doesn't). What you want is "C/C++ General" > "Paths and Symbols", which is for getting settings *from CDT to the compiler*, and should mirror what you see in "C/C++ Build" > "Settings". Once you have your setting in "Paths and Symbols", CDT knows about it and there should be no need to also add it in "Preprocessor Include Paths, Macros etc.".

Experts, is that correct? Is there a way to make this less confusing? I think at least the naming of the "Preprocessor Include Paths, Macros etc." page is unfortunate, as it doesn't give any hint that it's for discovering, not for specifying settings.


cdt-dev mailing list

cdt-dev mailing list

Back to the top