Please read History entry about usage of RUBY_CC_VERSION.
This change automatically append MAJOR.MINOR Ruby version of the compiled extension in the target directory. A better picture: rake cross compile RUBY_CC_VERSION=1.8.6:1.9.1 Will generate the following files: lib/1.8/extension_name.so lib/1.9/extension_name.so
This is in preparation for fat-binaries work. rake cross compile RUBY_CC_VERSION=1.8.6:1.9.1 Will generate binaries for both 1.8.6 and 1.9.1 compilers.
Be warned: works from 1.8 to 1.9, but not if your default ruby is 1.9. There are some issues inside mkmf.rb that limits this, needs further investigation.
Signed-off-by: Luis Lavena <firstname.lastname@example.org>
* predicate_matchers is deprecated. * please use the new Matcher DSL instead. http://rspec.rubyforge.org/rspec/1.2.4/classes/Spec/Matchers.html Spec::Matchers.create But that generated: * Spec::Matchers.create is deprecated. * please use Spec::Matchers.define instead. So, what should I follow, documentation or code? Hmn...
- This allows build gems for both VC6 and MinGW builts of Ruby. Rake::ExtensionTask.new('my_extension', GEM_SPEC) do |ext| ext.cross_compile = true ext.cross_platform = ['i386-mswin32', 'i386-mingw32'] end This is highly experimental and exposed the need to refactor ExtensionTask internals. Right now it fires the compilation process twice, which is suboptimal.
- It no longer raises an error, but instead a warning. - Uses captured console output.
I know, I keep messing with that file, but I like the new format with Darkfish.