<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Subbuilds: build avoidance done right</title>
	<atom:link href="http://www.electric-cloud.com/blog/2009/10/21/subbuilds-build-avoidance-done-right/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.electric-cloud.com/blog/2009/10/21/subbuilds-build-avoidance-done-right/</link>
	<description>This is your source for private development cloud best practices and technical tips and tricks for Electric Cloud solutions</description>
	<lastBuildDate>Thu, 03 May 2012 01:47:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Chris Leishman</title>
		<link>http://www.electric-cloud.com/blog/2009/10/21/subbuilds-build-avoidance-done-right/#comment-95</link>
		<dc:creator>Chris Leishman</dc:creator>
		<pubDate>Mon, 14 Dec 2009 15:14:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=552#comment-95</guid>
		<description>I have to echo Jean&#039;s comment - this whole &quot;subbuild&quot; approach is _exactly_ what make normally does anyway, except that there&#039;s an extra DB layer built in to work around the fact that the original makefiles were poorly constructed using recursive make, rather than non-recursive.</description>
		<content:encoded><![CDATA[<p>I have to echo Jean&#8217;s comment &#8211; this whole &#8220;subbuild&#8221; approach is _exactly_ what make normally does anyway, except that there&#8217;s an extra DB layer built in to work around the fact that the original makefiles were poorly constructed using recursive make, rather than non-recursive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean</title>
		<link>http://www.electric-cloud.com/blog/2009/10/21/subbuilds-build-avoidance-done-right/#comment-94</link>
		<dc:creator>Jean</dc:creator>
		<pubDate>Sun, 15 Nov 2009 22:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=552#comment-94</guid>
		<description>Pity the discussion at uberVU is not available here... To sum it up, &quot;build avoidance&quot; vs &quot;object reuse&quot; muddles the water: the problem is broken makefiles. &quot;Build avoidance&quot; in emake tries to work around the brokenness instead of helping to do the right thing: non-recursive make. The examples above are broken themselves, see http://make.paulandlesley.org/rules.html, rule 3: &quot;Life is simplest if the targets are built in the current working directory.&quot;</description>
		<content:encoded><![CDATA[<p>Pity the discussion at uberVU is not available here&#8230; To sum it up, &#8220;build avoidance&#8221; vs &#8220;object reuse&#8221; muddles the water: the problem is broken makefiles. &#8220;Build avoidance&#8221; in emake tries to work around the brokenness instead of helping to do the right thing: non-recursive make. The examples above are broken themselves, see <a href="http://make.paulandlesley.org/rules.html" rel="nofollow">http://make.paulandlesley.org/rules.html</a>, rule 3: &#8220;Life is simplest if the targets are built in the current working directory.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://www.electric-cloud.com/blog/2009/10/21/subbuilds-build-avoidance-done-right/#comment-93</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Sat, 24 Oct 2009 13:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=552#comment-93</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by ElectricCloud: #Build avoidance done right (even better: it costs you nothing). Read about it here: http://bit.ly/lItZt...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by ElectricCloud: #Build avoidance done right (even better: it costs you nothing). Read about it here: <a href="http://bit.ly/lItZt.." rel="nofollow">http://bit.ly/lItZt..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Trackbacks for Subbuilds: build avoidance done right « The Electric Cloud Blog [electric-cloud.com] on Topsy.com</title>
		<link>http://www.electric-cloud.com/blog/2009/10/21/subbuilds-build-avoidance-done-right/#comment-92</link>
		<dc:creator>Twitter Trackbacks for Subbuilds: build avoidance done right « The Electric Cloud Blog [electric-cloud.com] on Topsy.com</dc:creator>
		<pubDate>Thu, 22 Oct 2009 21:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=552#comment-92</guid>
		<description>[...] Subbuilds: build avoidance done right « The Electric Cloud Blog  blog.electric-cloud.com/2009/10/21/subbuilds-build-avoidance-done-right &#8211; view page &#8211; cached  I’ve heard it said that the best programmer is a lazy programmer. I’ve always taken that to mean that the best programmers avoid unnecessary work, by working smarter and not harder; and that they... (Read more)I’ve heard it said that the best programmer is a lazy programmer. I’ve always taken that to mean that the best programmers avoid unnecessary work, by working smarter and not harder; and that they focus on building only those features that are really required now, not allowing speculative work to distract them. (Read less) &#8212; From the page [...]</description>
		<content:encoded><![CDATA[<p>[...] Subbuilds: build avoidance done right « The Electric Cloud Blog  blog.electric-cloud.com/2009/10/21/subbuilds-build-avoidance-done-right &ndash; view page &ndash; cached  I’ve heard it said that the best programmer is a lazy programmer. I’ve always taken that to mean that the best programmers avoid unnecessary work, by working smarter and not harder; and that they&#8230; (Read more)I’ve heard it said that the best programmer is a lazy programmer. I’ve always taken that to mean that the best programmers avoid unnecessary work, by working smarter and not harder; and that they focus on building only those features that are really required now, not allowing speculative work to distract them. (Read less) &mdash; From the page [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

