Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Re: Make Target View

On 6/30/08, Elmenthaler, Jens <jens.elmenthaler@xxxxxxxxxx> wrote:

Hi Andrew,


Work on the make targets is highly appreciated. We can only use makefile projects because the makefiles are managed by other tools. The projects are not small and running even an incremental compile on the entire projects leads to long edit/debug cycles.

Thanks for the encouragement, it definitely helps fuel enthuthiasm ;)

Normally you only have to run the make in the folder that you edited files for, and sometimes compile an additional folder. The make targets actually address this problem nicely (once is fixed;-(.

 I can certainly feel your pain. I'll keep it in mind and hopefully will be able to propose a solution once it is understood how make targets should fit into MBS architecture. I think configurations is the key to it. Make targets could be tied to environment variables, scanner discovery, error parsers etc. via configurations. All the MBS niceties - we users of Standard Build want them too. 

I wonder about another question: Should I be required to manually define make targets for full, incremental, and clean for the source folders at all? Isn't that a standard setup when people write their make files that they can be run per source folder if they know which files were toched?

 I don't think that this fits well with Eclipse project concept. But yes, I think this is very common and CDT should have a better solution than creating a separate project for each folder - it is not practical.

If so, running the incremental build for the currently active configuration when a file is saved for its source folder would be a nice feature, too (assuming that only the compile errors for the recompiled folder would be updated).


Implicitly created make targets on source folders for each configuration would save a lot of work to my users.

That is an interesting idea, I like the idea. Maybe you can file an enhancement request in Bugzilla? Perhaps it could evolve into some good solution. My patch does not create targets per a folder but per a configuration. But maybe it makes sense, for example, have a Targets tab in configuration setup and to define targets which would appear in each folder automatically, or something?

Additionally, they could be the required targets to be build when a source file is saved.


Just thinking. Jens.

 Good. Thank you!


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Gvozdev
Sent: Monday, June 30, 2008 00:43
To: CDT General developers list.
Subject: [cdt-dev] Re: Make Target View



I've modified Make Target View to allow to display and run such actions as Full Build, Incremental Build, Clean Build for each configuration. If you work with multiple configurations, it could be handy to manipulate these targets. For one, it lets to run a build for a different configuration not switching to it. See attached picture and a patch in bug 238919. Is there any interest in such functionality?

As a next step, I want to tie regular make targets from the view to a configuration. Any idea is much appreciated.





On 6/15/08, Andrew Gvozdev <> wrote:


There is a number of bugs related to Standard Build and Make Target View in particular in Bugzilla. We are using CDT for the most part with Stadard Build and interested in some improvements in this area. I took a look at these bugs to analyse what are the improvements people are interested in. I came up with enhanced dialog, could you take a look and share your thoughts about it? The most significant part is a relation of a Build Target to Configuration and Project Builders. How does it fit to overall concept and does it connect well to Managed Build?

I'd like to know if there is *any* interest in that area, and would appreciate any response. It does not look like there were any developments for quite a bit of time but I am pretty sure that many use Standard Build at large.

Here is the list of bugs:






Jens Elmenthaler
Platform & Components Lab

Architecture Development Team


Verigy Germany GmbH, Herrenberger Str. 130, 71034
Sitz der Gesellschaft: Böblingen - Amtsgericht Böblingen HRB 6167

WEEE-Reg.-Nr. DE 16968742
Geschäftsführer: Hans-Jürgen Wagner, Dietmar Höller

Tel: +49 7031 4357-119


Back to the top