Hi Frank,
I am answering to this mail, as it seems to be the one raising the build
performance issue which may be introduced by full dependencies.
Some points:
- You are certainly free, to build one module only.
- There are techniques, which allow to not necessarily rebuild
everything dependent on a particular file, just because a comment was
added. E.g. http://abisum.sourceforge.net/ may be used, to check if
relinking is needed. Other such approaches may apply to resource or
header files.
- As reported by Kai, at least 66% of the build time is currently spend
in outer tools (dmake, perl, makedepend, ...), so there seems to be
space for improvement.
- AFAIR, the original reason for not using global dependencies was
network build performance, which degenerated because of the many file
stats. Many of these file stats are just done multiple times on the same
files, because of multiple dmake runs. Building everything by one
process basically gets rid of the doublets.
- My impressions is (and you may very well correct me if I am wrong),
that quite many people spend time, effort and code (->impl constructs)
into avoiding or understanding in-compatibility, basically to not
increase development build times. So, deficiencies in build time become
addressed by application _code_! Improved build performance and full
dependencies are the way to solve this.
Kay
Frank Schönheit - Sun Microsystems Germany wrote:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
