I don’t know wheather any of the wxRuby devs has tried to compile
wxRuby on Ruby 1.9 with Psych enabled (Ruby’s new YAML parser
automatically used by RubyGems if available–Psych is available if
libyaml was available when Ruby was compiled. Note this is NOT the
case for most packaged Rubies (Ubuntu/Debian/Arch Linux for sure) for
whatever reason). If you do
WXRUBY_RELEASE : build a release version, stripped of debugging
info
WXRUBY_DEBUG : build a debug version
=============================================
Another question: Will there ever be a precompiled 64-bit version of
wxRuby 2.0.1 for Linux? I can provide one, but I don’t have the rights
to push it to rubygems.org making it available for direct
installation. Tell me where to put it, and you can download it and
push it where it ought to be.
Thanks very much for the report and patch. I’ve been using distro linux
so hadn’t come across it.
Can the change be applied somewhere later, and nearer to the bug it
tickles, instead of at the head of the main rakefile? For example, could
it go at the start of rake/rakepackage.rb, before the requires there,
since it seems to relate to gem tasks?
Also, can it have a one-line comment note of the bug it fixes please,
and the Ruby version affected?
Another question: Will there ever be a precompiled 64-bit version of
wxRuby 2.0.1 for Linux? I can provide one, but I don’t have the rights
to push it to rubygems.org making it available for direct
installation. Tell me where to put it, and you can download it and
push it where it ought to be.
Would be happy to accept and upload a 64-bit version, thank you. Please
drop me a line off-list.
Can the change be applied somewhere later, and nearer to the bug
it tickles, instead of at the head of the main rakefile? For
example, could it go at the start of rake/rakepackage.rb, before
the requires there, since it seems to relate to gem tasks?
I’ll try, but the problem is that it must come before any attempt to
require yaml.rb, because otherwise Syck is already loaded. I’ll post
again when I know more.
Also, can it have a one-line comment note of the bug it fixes
please, and the Ruby version affected?
Of course it can^^. And just for the record, I’ve experienced the
problem with