Community
Participate
Working Groups
An example: When working with an autotools project, project properties still offer the user access to all settings of the CDT managed builder (MBS). Its settings for compiler switches, include paths and so on. Settings made there will have no effect, of cause, because the build is completely controlled by autotools. Other project models / build systems like CMake and QMake have the same problem. They have to add their own property pages for their settings, but cannot hide other CDT settings they replace. I is very confusing for the user, the GUI gets overloaded with irrelevant entries and its hard to find the wright place to enter a setting. I suggest introducing an easy way for plugins to disable some property pages. Maybe, a new additional project nature for managed builder projects is necessary? Then MBS' settings visibility would depend on this additional nature instead of [c,cc]nature. I guess plugins like autotools cannot remove [c,cc]nature from their projects without loosing the indexer.
