| Summary: | [Managed Build] Please enable C/C++ Build Properties page to copy settings | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Markus Karg <Markus.Karg> |
| Component: | cdt-core | Assignee: | Oleg Krasilnikov <oleg.krasilnikov> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | leo.treggiari, mikhail.sennikovskiy, oleg.krasilnikov |
| Version: | 2.0 | ||
| Target Milestone: | 5.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 182450 | ||
| Bug Blocks: | |||
|
Description
Markus Karg
Reassign to sean. This is managedBuilder related. Left side list-box of projects should be tree with all targets (Debug, Release, ...) under project node. Also, user should be able to multi-select these nodes and edit them en masse. That's not a bad suggestion in terms of managing the various configurations. Doing a multi-config edit is a little more complicated than it sounds due to the design of the build model. At the moment, since there is no way to change configruation without selecting one from the combo list box in that property page, this suggestion will be a bit hard to pull off, but when we do have a betterway to chnage configs, I will seriously consider doing this. Thanks. PR was not targeted to any particular release. Changing target milestone to 2.1 I think this issue is covered by new buid model, so the bug can be closed? Has it actually been fixed? We coudl certainly transfer ownership ofthe defect to the developers who will be working on that area in the MBS, but until there is a fix, we shouldn't close it. Setting target to future. Future means you commit to fix it in the Future. Inboxes can't make committments. Moving to '--'. Now, there are 2 ways to do required thing: - multi-configuration properies edit, mostly implemented. - checkbox "add to all configurations" when adding new environment variable, build macro, include path, symbol, etc. Closing as duplicate. *** This bug has been marked as a duplicate of bug 182450 *** |