This is the mail archive of the
mailing list for the GCC project.
Re: reduce compilation times?
- From: Tom St Denis <tstdenis at ellipticsemi dot com>
- To: Duft Markus <Markus dot Duft at salomon dot at>
- Cc: Fabian Cenedese <Cenedese at indel dot ch>, gcc-help at gcc dot gnu dot org
- Date: Wed, 28 Nov 2007 09:00:05 -0500
- Subject: Re: reduce compilation times?
- References: <18597F2B47F1394A9B309945EC72411201344D6A@servex01.wamas.com>
Duft Markus wrote:
You didn't get the question: i was asking if a *change* in a header isSounds like a nice feature, but honestly, I'm a bit paranoid, most of
the time when I edit header files I just do a "make clean" first
anyways. In a lot of our smaller SDKs, we often do a clean as part of
the "code/test/verify" cycle. It's just simpler to make sure everything
is fresh then have some lingering files that weren't picked up properly
in a makefile. On the larger projects we only clean if the headers
change for obvious reasons.
recognized to affect a *certain* .cpp file, not how make handles
dependencies and updates targets. Micorosft recognizes that a change in
a certain struct inside a header file may not require a recompilation of
a certain .cpp file if it doesn't use that struct. Thats what i asked
But I can't say honestly that I spend more time editing header files
than source files.