Bug 43917 - Synchronizing Make Build properties and Make Targets view
Summary: Synchronizing Make Build properties and Make Targets view
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-30 11:27 EDT by Brent Nicolle CLA
Modified: 2020-09-04 15:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brent Nicolle CLA 2003-09-30 11:27:30 EDT
Make Targets View is a clever way of simplifying a directory structure
with many Makefiles, with each containing many potentially useful targets.

Project properties > C/C++ Make Project > Make Builder tab
is a clever way of simplifying the interface for incremental and
full rebuilds.

It would be really nice if the two shared the same information:

1. The Make Targets view should be populated with the targets
specified in the Make Builder fields.  So, by default Make Targets view
contains targets "all" and "clean all".

2.  Decorate the target icons in Make Targets view to indicate that they
are the project's Incremental and Full Rebuild targets.

3. Make a change in the Make Build tab and it is reflected by addition (where
necessary) of targets, and re-decoration of the target icons, in Make
Targets view.

4. Similarly, provide a right-click mechanism to specify the Incremental
and Full Rebuild targets from the Make Targets view, and have that information
propagated back to the fields in the Make Build tab.
Comment 1 Alain Magloire CLA 2003-09-30 12:10:15 EDT
nice ideas
ok reassign.
Comment 2 Kleo Hapitas CLA 2004-07-07 16:57:09 EDT
PR was not targeted to any particular release. Changing target milestone to 2.1
Comment 3 Jonah Graham CLA 2019-12-30 18:55:32 EST
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.