On 5/31/07, <b class="gmail_sendername">Benjamin Jackson</b> &lt;<a href="mailto:ben@incomumdesign.com">ben@incomumdesign.com</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>&gt; […]<br>&gt; if the former, does the xcode bundle not work? i thought it just<br>&gt; used the xcodebuild tool which should works for rubycocoa<br>&gt; applications as well.<br>&gt; […]<br><br>The former. I&#39;d use the xcode bundle but I wanted to use Rake to
<br>develop a more generalized build language instead of worrying about<br>binary XCode projects.<br><br>any ideas? I&#39;m happy to work with you on this. take care,</blockquote><div><br>well, i&#39;ll describe my workflow a bit and maybe we can come up with something.
<br><br>rather than replace the xcode project file, i augment it with a series of rake tasks. the xcode project still provides great organization and i&#39;d really rather not try and memorize all those flags/settings adn replicate a lot of the structure it provides. i&#39;ve just wrapped the xcodebuild tool in some rake tasks which dynamically publish targets and configurations. additionally i have tasks for generating bridge support files and some ruby bits like rspec/mocha/rcov and what not.
<br><br>i&#39;d like to build a base set of rake tasks into rubycocoa and have the project templates provide you with a stub (much like rails does) as well.<br><br><br>which part of the development cycle did you want to use rake for? building, launching the build product, testing?
<br><br>cheers,<br>jean-pierre<br><br></div></div>