On 5/31/07, Benjamin Jackson ben@incomumdesign.com wrote:
[…] if the former, does the xcode bundle not work? i thought it just used the xcodebuild tool which should works for rubycocoa applications as well. […]
The former. I'd use the xcode bundle but I wanted to use Rake to develop a more generalized build language instead of worrying about binary XCode projects.
any ideas? I'm happy to work with you on this. take care,
well, i'll describe my workflow a bit and maybe we can come up with something.
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'd really rather not try and memorize all those flags/settings adn replicate a lot of the structure it provides. i'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.
i'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.
which part of the development cycle did you want to use rake for? building, launching the build product, testing?
cheers, jean-pierre