<?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: Rules with Multiple Outputs in GNU Make</title>
	<atom:link href="http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/</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: Jean</title>
		<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/#comment-56</link>
		<dc:creator>Jean</dc:creator>
		<pubDate>Thu, 22 Oct 2009 09:22:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=449#comment-56</guid>
		<description>Just noticed: PVM Gmake uses &quot;+&quot;
http://pvmgmake.sourceforge.net/</description>
		<content:encoded><![CDATA[<p>Just noticed: PVM Gmake uses &#8220;+&#8221;<br />
<a href="http://pvmgmake.sourceforge.net/" rel="nofollow">http://pvmgmake.sourceforge.net/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean</title>
		<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/#comment-55</link>
		<dc:creator>Jean</dc:creator>
		<pubDate>Sun, 23 Aug 2009 18:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=449#comment-55</guid>
		<description>I&#039;ve know too little about emake so I didn&#039;t even think that there are other &quot;#pragma&quot;ta. I don&#039;t think you have to be paranoid about new syntactic features in GNU make: once they&#039;re there, they ensure wide acceptance; emake should win by doing a better job with dependencies (thanks to electric fs), shouldn&#039;t it?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve know too little about emake so I didn&#8217;t even think that there are other &#8220;#pragma&#8221;ta. I don&#8217;t think you have to be paranoid about new syntactic features in GNU make: once they&#8217;re there, they ensure wide acceptance; emake should win by doing a better job with dependencies (thanks to electric fs), shouldn&#8217;t it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Melski</title>
		<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/#comment-54</link>
		<dc:creator>Eric Melski</dc:creator>
		<pubDate>Thu, 06 Aug 2009 17:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=449#comment-54</guid>
		<description>@Dave: Thanks for the feedback.  The nice thing about pragmas in emake is that they are interpreted as comments by vanilla GNU make, so they are simply ignored -- there&#039;s no real risk of &quot;lock in&quot;.  You could imagine using something like &quot;#pragma multi&quot; in conjunction with one of the solutions in the CM Crossroads article, so that with emake you get the fully correct behavior, and with gmake you get as close as possible within the constraints of the tool.</description>
		<content:encoded><![CDATA[<p>@Dave: Thanks for the feedback.  The nice thing about pragmas in emake is that they are interpreted as comments by vanilla GNU make, so they are simply ignored &#8212; there&#8217;s no real risk of &#8220;lock in&#8221;.  You could imagine using something like &#8220;#pragma multi&#8221; in conjunction with one of the solutions in the CM Crossroads article, so that with emake you get the fully correct behavior, and with gmake you get as close as possible within the constraints of the tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Melski</title>
		<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/#comment-53</link>
		<dc:creator>Eric Melski</dc:creator>
		<pubDate>Thu, 06 Aug 2009 17:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=449#comment-53</guid>
		<description>@Jean: That&#039;s interesting.  I didn&#039;t know that Sun make had that feature.  Unfortunately I don&#039;t think that syntax would be a good choice for emake.  With &quot;#pragma multi&quot;, the makefile would remain &quot;parse compatible&quot; with vanilla GNU make (because the pragma is just a special comment), but with target group syntax, the plus signs would cause trouble for vanilla GNU make.</description>
		<content:encoded><![CDATA[<p>@Jean: That&#8217;s interesting.  I didn&#8217;t know that Sun make had that feature.  Unfortunately I don&#8217;t think that syntax would be a good choice for emake.  With &#8220;#pragma multi&#8221;, the makefile would remain &#8220;parse compatible&#8221; with vanilla GNU make (because the pragma is just a special comment), but with target group syntax, the plus signs would cause trouble for vanilla GNU make.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Melski</title>
		<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/#comment-52</link>
		<dc:creator>Eric Melski</dc:creator>
		<pubDate>Thu, 06 Aug 2009 17:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=449#comment-52</guid>
		<description>@Jean:  I&#039;m not really interested in improving the functionality of GNU make, because my livelihood is based on selling an alternative to it.  I&#039;m looking for new ways to make my offering more compelling in comparison to GNU make.</description>
		<content:encoded><![CDATA[<p>@Jean:  I&#8217;m not really interested in improving the functionality of GNU make, because my livelihood is based on selling an alternative to it.  I&#8217;m looking for new ways to make my offering more compelling in comparison to GNU make.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean</title>
		<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/#comment-51</link>
		<dc:creator>Jean</dc:creator>
		<pubDate>Wed, 05 Aug 2009 12:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=449#comment-51</guid>
		<description>Oh, and Sun make has &quot;target groups&quot;

target [+ target. . . ] :

http://docs.sun.com/app/docs/doc/816-5165/make-1s</description>
		<content:encoded><![CDATA[<p>Oh, and Sun make has &#8220;target groups&#8221;</p>
<p>target [+ target. . . ] :</p>
<p><a href="http://docs.sun.com/app/docs/doc/816-5165/make-1s" rel="nofollow">http://docs.sun.com/app/docs/doc/816-5165/make-1s</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean</title>
		<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/#comment-50</link>
		<dc:creator>Jean</dc:creator>
		<pubDate>Wed, 05 Aug 2009 12:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=449#comment-50</guid>
		<description>Why not proposing $(pragma ) for GNU make?</description>
		<content:encoded><![CDATA[<p>Why not proposing $(pragma ) for GNU make?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.electric-cloud.com/blog/2009/08/04/rules-with-multiple-outputs-in-gnu-make/#comment-49</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 05 Aug 2009 03:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.electric-cloud.com/?p=449#comment-49</guid>
		<description>We&#039;ve been avoiding the use of pragmas to preserve our ability to use other makes, although we have yet to use one.

We would certainly consider it.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve been avoiding the use of pragmas to preserve our ability to use other makes, although we have yet to use one.</p>
<p>We would certainly consider it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

