Hey all,
I'm currently working on the beginnings of of RubyCocoa Bundle, and trying to do something similar to the "Build and Run" script from the XCode Bundle:
#!/bin/sh echo "<html><body>" cd $TM_PROJECT_DIRECTORY && rake MyApp.app/Contents/MacOS/MyApp echo "</body></html>"
I've gotten to the point where I can run MyApp.app/Contents/MacOS/ MyApp and get the output, but only after the program has terminated. I know there's some way to get my traces to output while I'm running the program, but not sure how. Any pointers? Thanks,
Ben
On 5/30/07, Benjamin Jackson ben@incomumdesign.com wrote:
Hey all,
I'm currently working on the beginnings of of RubyCocoa Bundle, and trying to do something similar to the "Build and Run" script from the XCode Bundle:
#!/bin/sh echo "<html><body>" cd $TM_PROJECT_DIRECTORY && rake MyApp.app/Contents/MacOS/MyApp echo "</body></html>"
I've gotten to the point where I can run MyApp.app/Contents/MacOS/ MyApp and get the output, but only after the program has terminated. I know there's some way to get my traces to output while I'm running the program, but not sure how. Any pointers? Thanks,
are you trying to launch rubycocoa applications and display output or are you trying to run a rubycocoa application within the textmate process?
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.
if the latter, i think you'll need to initialize rubycocoa from within textmate and also load/run rubycocoa scripts inside textmate (otherwise you won't be able to interact with the window server). i wrote a plugin to do this (i wanted to write a bundle which could offer commands that made use of rubycocoa) but stalled at the point of creating a RubyCocoaMate or tweaked RubyMate to handle and present output.
cheers, jean-pierre
are you trying to launch rubycocoa applications and display output or are you trying to run a rubycocoa application within the textmate process?
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.
if the latter, i think you'll need to initialize rubycocoa from within textmate and also load/run rubycocoa scripts inside textmate (otherwise you won't be able to interact with the window server). i wrote a plugin to do this (i wanted to write a bundle which could offer commands that made use of rubycocoa) but stalled at the point of creating a RubyCocoaMate or tweaked RubyMate to handle and present output.
cheers, jean-pierre
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,
Ben
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