And I *REALLY* loved the time it cut down on building large systems
becoz of it's DO subsystem. Now that I'm using PerForce (a
copy-to-local CRM), if someone changes a major header, EVERYBODY has
to rebuild :(
Could you explain this in more detail?
CC keeps track of what it took to build a .o (and subsequent .so/.a's)
This includes header and source files (and their respective revisions,
if under CC) as well as compiler flags.
If someone has already built the .o that you need to build, clearmake
would simply give you the derived-object (DO) instead of rebuilding it
yourself.
Once someone has built the system with the recently touched code,
everyone else got the DO's, and build time was GREATLY reduced for
almost everyone (the first sucker had to spend the most time, of course :)
--
Michael O'Keefe | [EMAIL PROTECTED]
Live on and Ride a 03 BMW F650GSDakar| [EMAIL PROTECTED] / |
I like less more or less less than |Work:+1 858 845 3514 / |
more. UNIX-live it,love it,fork() it |Fax :+1 858 845 2652 /_p_|
My views are MINE ALONE, blah, blah, |Home:+1 760 788 1296 \`O'|
blah, yackety yack - don't come back |Fax :+1 858 _/_\|_,
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
