Here's some code which does that:
http://github.com/alloy/rucola/tree/master/lib/rucola/tasks/deploy.rake
- Eloy
On Nov 11, 2008, at 1:38 PM, Richard Kilmer wrote:
As always, Laurent did all the hard work!
I also wonder whether it makes sense to add 'package' or something
as a rake task tha
Ouch, if you removed /usr/bin/ruby then yes it's going to fail :)
Either you manually edit the Rakefile and change the paths, or you re-
install your OS. Removing the default Ruby install is a very very bad
idea (as removing anything bundled with the OS), because some OS
functionality relies
So I didn't really "remove" Ruby, I simply renamed the files/folders to
avoid conflict between macports Ruby and OSX Ruby. I believe this is
something very common and it might create issues for other people.
However, even after I changed the rake file, the build failed because of
miniruby:
https:/
#159: "%d" with large integer argument gives conversion error
-+--
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major
#142: Infinite loop creating new Monitor object
---+
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major
booh I re added Ruby and Gem (I just had renamed them ruby.orig and
gem.orig) but I still can't build:
$ rake --trace
(in /Users/mattetti/src/MacRuby/trunk)
** Invoke default (first_time)
** Invoke all (first_time)
** Invoke macruby (first_time)
** Invoke macruby:build (first_time)
** Invoke macru
#157: MacRuby/miniruby segfaults while building
-+--
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: blocker |
As always, Laurent did all the hard work!
I also wonder whether it makes sense to add 'package' or something as
a rake task that takes the deployed .app and creates a dmg and places
it inside of it for redistribution. Make sense?
Best,
Rich
On Nov 11, 2008, at 1:03 AM, Matt Aimonetti wro
A packaging rake task would be nice. I personally have no clue about
creating a dmg file, so having a task that does for me would be super
helpful.
- Matt
On Tue, Nov 11, 2008 at 7:38 AM, Richard Kilmer <[EMAIL PROTECTED]> wrote:
> As always, Laurent did all the hard work!
> I also wonder whethe
Didn't work.
I believe the problem is that I removed MacOSX default Ruby install in favor
of the macports version (maybe not a wise move) and the rake task seems to
have a hard coded path to /usr/bin/ruby
Command failed with status (127): [/usr/bin/ruby tool/compile_prelude.rb
prel...]
Line 269
#142: Infinite loop creating new Monitor object
---+
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major
#142: Infinite loop creating new Monitor object
---+
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major
On Nov 11, 2008, at 1:28 PM, Matt Aimonetti wrote:
booh I re added Ruby and Gem (I just had renamed them ruby.orig and
gem.orig) but I still can't build:
$ rake --trace
macrake
___
MacRuby-devel mailing list
[email protected]
ht
to use macrake I would need to be able to build MacRuby first ;)
-Matt
On Tue, Nov 11, 2008 at 7:11 PM, Jordan K. Hubbard <[EMAIL PROTECTED]> wrote:
>
> On Nov 11, 2008, at 1:28 PM, Matt Aimonetti wrote:
>
> booh I re added Ruby and Gem (I just had renamed them ruby.orig and
>> gem.orig) but I
Erm. I must have missed something. Are you saying that rake build
and rake install don't work for you either? I assumed you'd already
used those two commands to bootstrap yourself and then would use
macrake to do more esoteric stuff. You'll need macrake, for example,
to build the HotCoc
The problem is that I can't build MacRuby itself :(
$ rake in the repo fails :(
-Matt
On Tue, Nov 11, 2008 at 7:50 PM, Jordan K. Hubbard <[EMAIL PROTECTED]> wrote:
> Erm. I must have missed something. Are you saying that rake build and
> rake install don't work for you either? I assumed y
#160: Opening a TCPSocket causes GC exception
-+--
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major| Mil
#160: Opening a TCPSocket causes GC exception
-+--
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major|
#160: Opening a TCPSocket causes GC exception
-+--
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: closed
Priority: major|
#159: "%d" with large integer argument gives conversion error
-+--
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major
The result we're looking for (IMHO) is a way to write Cocoa apps
that "look right" to Ruby programmers. The number of Objective-C
programmers who don't work on OSX apps is vanishingly small.
By opening up OSX programming to MacBook-carrying Rubyists, Apple
can grow its developer base in relativel
yay! I finally got it to build. Turns out that I still had the old miniruby
which wasn't built properly. After cleaning up everything, restored MacOsX
ruby and re tried, everything works fine :)
Time to have fun and learn Cocoa via ruby.
Thanks,
-Matt
On Tue, Nov 11, 2008 at 8:06 PM, Matt Aimon
I wanted to debug Rich's new tasks and by reflect I added the following code
to my Rakefile:
require "ruby-debug"
debugger
macrake died on the require telling me that the lib couldn't be required. I
tried to do
macgem install ruby-debug but it segfaulted big time:
/Library/Frameworks/MacRuby.f
IMHO, MacRuby and Merb are two of the most interesting current
developments in the Ruby arena. Because I've been looking at
both of them, I started noticing some similarities, including:
* Focus on design and engineering
In an age of "cowboy programming", I find it refreshing to
see that
Merb <3 MacRuby
During RubyConf, Laurent, Yehuda, Rich and myself were talking about how to
work closer.
We were thinking about maybe running Merb on MacRuby so we could introspect
a dev app and see what's going on. A bit like the iPhone dev tools.
We are also looking at simpler MacRuby apps suc
25 matches
Mail list logo
