Fujimoto Hisa
hisa****@fobj*****
Sat Jun 2 07:50:42 JST 2007
Hi The issue may be from that the rubygem installer always make the 1st line of the gem command: #!/usr/bin/env ruby So script which call the gem command using `system' method, may excute another ruby command. For example the early stage of gen_bridge_doc tool had this sortof issue, so i've fixed it. the rake is optional in Tiger , so the install.rb should be primary way to make rubycocoa. hisa On 2007/06/02, at 6:04, Laurent Sansonetti wrote: > Hi, > > Justin reported on the IRC channel a problem about building RubyCocoa > using a manually-installed version of Ruby, and using rake. It seems > that RubyGems cannot be found then. > > But when using install.rb, the problem disappears. > > I don't know much about rake, so I just read both Rakefile and the > source code of rake, and found that normally the `ruby' method should > spawn the right Ruby interpreter (in his case, /usr/local/bin/ruby). > > Any thoughts on this problem? > > Also, why was Rakefile created? Having 2 different ways of building > RubyCocoa is a bit confusing. I think that we should either keep > install.rb, or move everything in Rakefile. > > Laurent > > _______________________________________________ > Rubycocoa-devel mailing list > Rubyc****@lists***** > http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel
