Hotcocoa also don't came with macruby dmg anymore?
On 23/04/2010, at 01:23, Matt Aimonetti wrote:
The project was moved outside of the MacRuby core and it's currently
maintained by Rich Kilmer. It was moved to GitHub with the hope that
the community will be more involved and take ownership
Thanks Laurent, I will update the site with this links.
Sent from my iPhone
On 22/04/2010, at 17:25, Laurent Sansonetti
wrote:
Hi Daniel,
This is a recurrent question. Our opensource projects are hosted on
macosforge. If we want to switch to new tools they must be installed
there, and
My apps are working too!
Unfortunately compiling to static code is broken:
$ cat a.rb
puts 42
$ macrubyc --static a.rb
Undefined symbols:
"llvm::ExecutionEngine::createJIT(llvm::ModuleProvider*,
std::basic_string, std::allocator >*,
llvm::JITMemoryManager*, llvm::CodeGenOpt::Level, bool,
l
Could you also take a look at https://www.macruby.org/trac/ticket/663?
Jordan
On Apr 23, 2010, at 00:31, Laurent Sansonetti wrote:
> Now:
>
> http://www.macruby.org/trac/ticket/628 CTFramesetterCreateFrame doesn't like
> the CFRange type
> http://www.macruby.org/trac/ticket/662 macruby 0.6 bre
Just to clarify, should I direct any questions or comments about HotCocoa
here, or privately to Rich (since there doesn't seem to be a HotCocoa
mailing list that I can find)?
Thanks,
-Matt
On Thu, Apr 22, 2010 at 9:23 PM, Matt Aimonetti wrote:
> The project was moved outside of the MacRuby core
Hi,
Looks like the version of LLVM that you installed in your system is too old.
Are you using MacRuby from the nightly builds? It could explain the problem
then (and if you manually built MacRuby in the past).
--static only works if you installed LLVM manually. This is a problem that we
shoul
This one does not seem critical for 0.6, does it?
We are looking for bugs that could seriously impact Cocoa development.
Laurent
On Apr 23, 2010, at 4:29 AM, Jordan Breeding wrote:
> Could you also take a look at https://www.macruby.org/trac/ticket/663?
>
> Jordan
>
> On Apr 23, 2010, at 00:3
Probably not, the only way it could affect Cocoa development is if someone was
doing something like:
NSTextFieldInstance.text = "%6.2" % [5.fdiv(3)]
I haven't tried to see if -[NSString stringWithFormat:] would work instead, but
hopefully it would.
On Apr 23, 2010, at 14:31, Laurent Sansonetti
