<?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: Xcode SCM &amp; build directory</title>
	<atom:link href="http://www.artin.org/geekblog/2009/08/xcode-scm-build-directory/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.artin.org/geekblog/2009/08/xcode-scm-build-directory/</link>
	<description>A place to write down the crap from my brain</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:38:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Peter Hornby</title>
		<link>http://www.artin.org/geekblog/2009/08/xcode-scm-build-directory/comment-page-1/#comment-371</link>
		<dc:creator>Peter Hornby</dc:creator>
		<pubDate>Tue, 10 May 2011 21:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.artin.org/geekblog/?p=43#comment-371</guid>
		<description>@AstralBodies : thanks for the tip about XCode 4, by default, maintaining build assets (and other things) in a location other than the project folder.  I&#039;m just starting out on Mac development, and trying to find the executable file that XCode had just built (and run) for me was driving me nuts.  Specifically, I needed, for the purposes of my example, to copy two .bundle files to the folder where my command-line executable lived.  Couldn&#039;t find the .bundle files, nor the command-line executable.  Spotlight didn&#039;t help. The XCode preference &quot;Place build products in locations specified by targets&quot;, in the Locations tab, solved the problem for me.</description>
		<content:encoded><![CDATA[<p>@AstralBodies : thanks for the tip about XCode 4, by default, maintaining build assets (and other things) in a location other than the project folder.  I&#8217;m just starting out on Mac development, and trying to find the executable file that XCode had just built (and run) for me was driving me nuts.  Specifically, I needed, for the purposes of my example, to copy two .bundle files to the folder where my command-line executable lived.  Couldn&#8217;t find the .bundle files, nor the command-line executable.  Spotlight didn&#8217;t help. The XCode preference &#8220;Place build products in locations specified by targets&#8221;, in the Locations tab, solved the problem for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Astralbodies</title>
		<link>http://www.artin.org/geekblog/2009/08/xcode-scm-build-directory/comment-page-1/#comment-366</link>
		<dc:creator>Astralbodies</dc:creator>
		<pubDate>Tue, 26 Apr 2011 11:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.artin.org/geekblog/?p=43#comment-366</guid>
		<description>Chris - later projects I did use the svn:ignore, especially when multiple developers were working on the same project.  Xcode 4 puts build assets in a separate folder by default now - probably to better support SCM on the command line or possibly to just conform to the idea of Application Caches and disposable files being in ~/Library (specifically ~/Library/Developer/Xcode/DerivedData).</description>
		<content:encoded><![CDATA[<p>Chris &#8211; later projects I did use the svn:ignore, especially when multiple developers were working on the same project.  Xcode 4 puts build assets in a separate folder by default now &#8211; probably to better support SCM on the command line or possibly to just conform to the idea of Application Caches and disposable files being in ~/Library (specifically ~/Library/Developer/Xcode/DerivedData).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://www.artin.org/geekblog/2009/08/xcode-scm-build-directory/comment-page-1/#comment-365</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Tue, 26 Apr 2011 10:56:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.artin.org/geekblog/?p=43#comment-365</guid>
		<description>Setting svn:ignore is also possible, and doesn&#039;t require a change of the project structure. I guess having the build files in the designated folder makes it not only easy to debug the build objects, but also keeps things tidy.

Have a look at svn properties for instance. Other SCMs have similar techniques.</description>
		<content:encoded><![CDATA[<p>Setting svn:ignore is also possible, and doesn&#8217;t require a change of the project structure. I guess having the build files in the designated folder makes it not only easy to debug the build objects, but also keeps things tidy.</p>
<p>Have a look at svn properties for instance. Other SCMs have similar techniques.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Version Control for Xcode &#124; macjasp</title>
		<link>http://www.artin.org/geekblog/2009/08/xcode-scm-build-directory/comment-page-1/#comment-80</link>
		<dc:creator>Version Control for Xcode &#124; macjasp</dc:creator>
		<pubDate>Sat, 20 Nov 2010 14:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.artin.org/geekblog/?p=43#comment-80</guid>
		<description>[...] Xcode correctly before getting up and running, the directory in question is nicely documented here, and errors will occur when checking code in or out [...]</description>
		<content:encoded><![CDATA[<p>[...] Xcode correctly before getting up and running, the directory in question is nicely documented here, and errors will occur when checking code in or out [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marco</title>
		<link>http://www.artin.org/geekblog/2009/08/xcode-scm-build-directory/comment-page-1/#comment-76</link>
		<dc:creator>marco</dc:creator>
		<pubDate>Wed, 20 Oct 2010 15:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.artin.org/geekblog/?p=43#comment-76</guid>
		<description>gracias</description>
		<content:encoded><![CDATA[<p>gracias</p>
]]></content:encoded>
	</item>
</channel>
</rss>

