Remove "C/C++ Include Paths and Symbols" and "CMake" property pages in Core Build projects

[jonahgraham]

I think the whole page "C/C++ Include Paths and Symbols" can be removed from the CBS Makefile project properties. I don't see the use of any of the items that can be used there. See also my comments above.

I also think that in the CMake project properties the the page "CMake" can be removed. It only has a button to launch cmake-gui. I find it weird to launch this from project properties.

Originally posted by @ewaterlander in #999

See #999 for some discussion on how this conclusion was arrived at.

[jsmif]

Is the "C/C++ Include Paths and Symbol" functionality going to remain in other project types other than Makefile projects? (I don't actually care what type my projects are, because I'm never actually compiling the code, I'm just auditing it. And I just picked Makefile-based in the past because it seemed to pick up configuration clues from other files in any random project.)

I ask, because literally the only reason I use Eclipse is because I found its "C/C++ Include Paths and Symbol" functionality to be superior to using things like emacs + gtags, which doesn't show which preprocessor defines are currently assumed to be defined or undefined. The capability to manually set what's #defined is my whole reason for using Eclipse.

[jonahgraham]

The functionality you are looking for will not be removed as we're only going to remove these pages for project types where it doesn't work (i.e. doesn't have an effect). I really appreciate you bringing your use case to our attention to make sure we don't break this flow as I think it represents a common use case.

[ewaterlander]

I ask, because literally the only reason I use Eclipse is because I found its "C/C++ Include Paths and Symbol" functionality to be superior to using things like emacs + gtags, which doesn't show which preprocessor defines are currently assumed to be defined or undefined. The capability to manually set what's #defined is my whole reason for using Eclipse.

Hi @jsmif ,

What you are looking for is the legacy Managed Build System Makefile projects, because these projects generate a Makefile based on build configurations defined in the project properties. A change in the project properties will immediately update the code view. You need to take care that you edit the build configuration that is active to see the immediate effect.

Creating a new project:

Importing existing code is done via menu File >> Import... and then select Existing Code as Makefile project

Changing preprocessor symbols: