<?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: Windows-Friendly Cygwin Paths</title>
	<atom:link href="http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/</link>
	<description>pursuing well-crafted software</description>
	<lastBuildDate>Wed, 12 Jun 2013 15:15:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Andy</title>
		<link>http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/#comment-32</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sat, 10 Jul 2010 14:44:19 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derekgreer/archive/2010/07/09/windows-friendly-cygwin-paths.aspx#comment-32</guid>
		<description>All fair points.</description>
		<content:encoded><![CDATA[<p>All fair points.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: derekgreer</title>
		<link>http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/#comment-31</link>
		<dc:creator>derekgreer</dc:creator>
		<pubDate>Sat, 10 Jul 2010 13:10:06 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derekgreer/archive/2010/07/09/windows-friendly-cygwin-paths.aspx#comment-31</guid>
		<description>@Andy I stand corrected. This works as long as the paths you&#039;re referencing are on the same drive as the one you&#039;ve installed Cygwin in the root of, but this wouldn&#039;t suffice if expanding relative paths for another drive (e.g. developing in X:/Projects/).  In this case, you&#039;d still need to follow the approach outlined here.  This also isn&#039;t going to be a practical option for people already using Cygwin, as most wouldn&#039;t want to reinstall/copy all there files over for this purpose.

Interesting find, but ultimately my recommendation would still be to set up an explicit mapping in the mount table to avoid the consequences that installing Cygwin in the root would lead to.



</description>
		<content:encoded><![CDATA[<p>@Andy I stand corrected. This works as long as the paths you&#8217;re referencing are on the same drive as the one you&#8217;ve installed Cygwin in the root of, but this wouldn&#8217;t suffice if expanding relative paths for another drive (e.g. developing in X:/Projects/).  In this case, you&#8217;d still need to follow the approach outlined here.  This also isn&#8217;t going to be a practical option for people already using Cygwin, as most wouldn&#8217;t want to reinstall/copy all there files over for this purpose.</p>
<p>Interesting find, but ultimately my recommendation would still be to set up an explicit mapping in the mount table to avoid the consequences that installing Cygwin in the root would lead to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: derekgreer</title>
		<link>http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/#comment-30</link>
		<dc:creator>derekgreer</dc:creator>
		<pubDate>Sat, 10 Jul 2010 11:26:04 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derekgreer/archive/2010/07/09/windows-friendly-cygwin-paths.aspx#comment-30</guid>
		<description>@Eric Yeah, that works if you don&#039;t mind writing Cygwin-specific scripts, but when working on a team where not everyone uses Cygwin or for any open source build scripts this isn&#039;t a viable option.</description>
		<content:encoded><![CDATA[<p>@Eric Yeah, that works if you don&#8217;t mind writing Cygwin-specific scripts, but when working on a team where not everyone uses Cygwin or for any open source build scripts this isn&#8217;t a viable option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/#comment-29</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sat, 10 Jul 2010 08:24:03 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derekgreer/archive/2010/07/09/windows-friendly-cygwin-paths.aspx#comment-29</guid>
		<description>No, it would be at /Projects, alongside /bin, /usr, /Windows, /Users, ... .</description>
		<content:encoded><![CDATA[<p>No, it would be at /Projects, alongside /bin, /usr, /Windows, /Users, &#8230; .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Smith</title>
		<link>http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/#comment-28</link>
		<dc:creator>Eric Smith</dc:creator>
		<pubDate>Sat, 10 Jul 2010 06:27:24 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derekgreer/archive/2010/07/09/windows-friendly-cygwin-paths.aspx#comment-28</guid>
		<description>A neat trick.  I just do a $( cygpath -w &lt;cygwin path&gt; ) when calling out to Windows apps though.</description>
		<content:encoded><![CDATA[<p>A neat trick.  I just do a $( cygpath -w <cygwin path> ) when calling out to Windows apps though.</cygwin></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: derekgreer</title>
		<link>http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/#comment-27</link>
		<dc:creator>derekgreer</dc:creator>
		<pubDate>Sat, 10 Jul 2010 00:55:49 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derekgreer/archive/2010/07/09/windows-friendly-cygwin-paths.aspx#comment-27</guid>
		<description>Where Cygwin gets installed wouldn&#039;t affect the default mount table settings.  If you were to install Cygwin in the root then you&#039;d still find that working in C:/Projects would resolve to /cygdrive/c/projects.</description>
		<content:encoded><![CDATA[<p>Where Cygwin gets installed wouldn&#8217;t affect the default mount table settings.  If you were to install Cygwin in the root then you&#8217;d still find that working in C:/Projects would resolve to /cygdrive/c/projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://lostechies.com/derekgreer/2010/07/09/windows-friendly-cygwin-paths/#comment-26</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 09 Jul 2010 22:08:35 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derekgreer/archive/2010/07/09/windows-friendly-cygwin-paths.aspx#comment-26</guid>
		<description>You could also just install Cygwin into C:\, thereby making / identical to C:\. Advantage: easier mental switching between Cygwin and Windows paths. Disadvantage: Unix and Windows directories get mixed up at the top level (although that&#039;s quite similar to what you&#039;d get on a Mac), and you have to trust the Cygwin package maintainers not to accidentally clobber something in the Windows directories.</description>
		<content:encoded><![CDATA[<p>You could also just install Cygwin into C:\, thereby making / identical to C:\. Advantage: easier mental switching between Cygwin and Windows paths. Disadvantage: Unix and Windows directories get mixed up at the top level (although that&#8217;s quite similar to what you&#8217;d get on a Mac), and you have to trust the Cygwin package maintainers not to accidentally clobber something in the Windows directories.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
