Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367586

Summary:	Require explicit user action to make changes only to a single build configuration
Product:	[Tools] CDT	Reporter:	Eugene Ostroukhov <eostroukhov>
Component:	cdt-build-managed	Assignee:	Project Inbox <cdt-build-managed-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	normal
Priority:	P3	CC:	cdtdoug
Version:	8.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Eugene Ostroukhov

2011-12-27 14:17:39 EST

I know this may be a matter of taste, but I would argue that most CDT project property pages (pretty much all save for tool settings) are expected to work on all build configuration at once.

For instance, when the user adds a library to "Path and Symbols" property page he would expect this library is added to both debug and release configuration. This results in broken build and requires the user to redo settings for other configurations. This may become quite tedious if the user made substantial changes (i.e. added several paths, specified many MACROs, etc.)

I would like to suggest making per-configuration setup an opt-in feature on most tabs.

One of the ideas I plan to try in our product is hiding the configuration combo and showing "Apply to all build configurations" checkbox that is checked by default. The combo will only be shown when user unchecks the box.

Comment 1 Andrew Gvozdev

2011-12-27 15:29:29 EST

(In reply to comment #0)
> I know this may be a matter of taste, but I would argue that most CDT project
> property pages (pretty much all save for tool settings) are expected to work on
> all build configuration at once.
I don't agree that the users expect that as a starting point. The configurations always differ, not exact duplicates. Besides, some of the project pages are not capable of working in multi-configuration mode. Maybe we just need easier way to propagate the settings to the other configurations.