rake-compiler 0.7.1 → 0.7.5

data/History.txt

@@ -1,3 +1,24 @@
+=== 0.7.5 / 2010-11-25
+
+* Enhancements:
+  * Promoted stable version for cross-compilation to 1.8.6-p398. Closes GH-19
+
+* Bugfixes:
+  * Generate a fake.rb compatible with Ruby 1.9.2. Closes GH-25
+  * fake.rb will not try to mimic Ruby's own fake to the letter. Closes GH-28
+  * Expand symlinks for tmp_dir. Closes GH-24
+  * Silence make output during rake-compiler invocation.
+  * Usage of Gem.ruby instead of RbConfig ruby_install_name
+    This solve issues with ruby vs. ruby.exe and jruby.exe
+
+* Experimental:
+  * Allow setting of HOST during cross-compilation. This enable usage
+    of mingw-w64 compiler and not the first one found in the PATH.
+
+      rake-compiler cross-ruby VERSION=1.9.2-p0 HOST=i686-w64-mingw32
+      rake-compiler cross-ruby HOST=i386-mingw32 (OSX mingw32 port)
+      rake-compiler cross-ruby HOST=i586-pc-mingw32 (Debian/Ubuntu mingw32)
+
 === 0.7.1 / 2010-08-07
 
 * Bugfixes:

data/Isolate

@@ -0,0 +1,9 @@
+options :path => 'isolated'
+
+gem 'rake'
+gem 'rspec', '~> 1.3.1'
+gem 'cucumber', '~> 0.9.4'
+
+unless RUBY_PLATFORM =~ /java/
+  gem 'rcov', '~> 0.9.9'
+end

data/README.rdoc

@@ -1,301 +1,320 @@
-= rake-compiler
-
-rake-compiler aims to help Gem developers deal with Ruby extensions, simplifying
-code and reducing duplication.
-
-It followss *convention over configuration* and sets a standardized structure to
-build and package both C and Java extensions in your gems.
-
-This is the result of experiences dealing with several Gems that required native
-extensions across platforms and different user configurations where details like
-portability and clarity of code were lacking.
-
-== An Overview
-
-Let's summarize what rake-compiler provides:
-
-* No custom rake tasks required. Less code duplication and errors.
-
-* Painlessly build extensions on different platforms (Linux, OSX and Windows).
-
-* Painlessly build extensions for different Ruby implementations (JRuby,
-  Rubinius and MRI).
-
-* Allow multiple extensions be compiled inside the same gem.
-
-* Mimics RubyGems installation process, so helps as a test environment.
-
-* Simplify cross platform compilation of extensions (target Windows from Linux).
-
-== I'm sold! show me how to use it! (Installation)
-
-Usage of rake-compiler is pretty much straight forward.
-
-First, you need to install the gem:
-
-  $ gem install rake-compiler
-
-== Now what? (Usage)
-
-Now that you have the gem installed, let's give your project some structure.
-
-=== Structure
-
-Let's say we want to compile an extension called 'hello_world', so we should
-organize the code and folders that will help rake-compiler do its job:
-
-    |-- ext
-    |   `-- hello_world
-    |       |-- extconf.rb
-    |       |-- HelloWorldService.java
-    |       `-- hello_world.c
-    |-- lib
-    `-- Rakefile
-
-TIP: Having a consistent folder structure will help developers and newcomers
-to find code and also contribute back to your project more easily.
-
-=== Adding the code
-
-So now it's time to introduce the code to compile our extension:
-
-    # File: Rakefile
-
-    require 'rake/extensiontask'
-
-    Rake::ExtensionTask.new('hello_world')
-
-Ok, that's it. No other line of code.
-
-If we wanted to do the same for a JRuby extension (written in Java):
-
-    # File: Rakefile
-
-    require 'rake/javaextensiontask'
-
-    Rake::JavaExtensionTask.new('hello_world')
-
-=== Compile process
-
-Those *two* lines of code automatically added the needed rake tasks to build
-the hello_world extension. Running Rake on 1.8.x/1.9 (MRI):
-
-  $ rake -T
-  (in /home/user/my_extension)
-  rake compile                # Compile the extension(s)
-  rake compile:hello_world    # Compile just the hello_world extension
-
-Simply calling <tt>compile</tt>:
-
-  $ rake compile
-
-Will do all the compile process for us, putting the result extension inside
-<tt>lib</tt> directory.
-
-NOTE: Please be aware that building C extensions requires the proper
-development environment for your Platform, which includes libraries, headers
-and build tools. Check your distro / vendor documentation on how to install it.
-
-NOTE: Building Java extensions requires the <tt>javac</tt>, part of the Java
-Development Kit (JDK). This should be included by default on Mac OS X, and
-downloadable from http://java.sun.com for other operating systems.
-
-=== Generate native gems
-
-A common usage scenario of rake-compiler is generate native gems that bundles
-your extensions.
-
-This got over-simplified with <tt>Rake::ExtensionTask</tt>:
-
-    # somewhere in your Rakefile, define your gem spec
-    spec = Gem::Specification.new do |s|
-      s.name = "my_gem"
-      s.platform = Gem::Platform::RUBY
-      s.extensions = FileList["ext/**/extconf.rb"]
-    end
-
-    # add your default gem packing task
-    Rake::GemPackageTask.new(spec) do |pkg|
-    end
-
-    # feed your ExtensionTask with your spec
-    Rake::ExtensionTask.new('hello_world', spec)
-
-Now, as usual, you can build your pure-ruby gem (standard output):
-
-  $ rake gem
-  (in /projects/oss/my_gem.git)
-  mkdir -p pkg
-    Successfully built RubyGem
-    Name: my_gem
-    Version: 0.1.0
-    File: my_gem-0.1.0.gem
-  mv my_gem-0.1.0.gem pkg/my_gem-0.1.0.gem
-
-Plus, you have the functionality to build native versions of the gem:
-
-  # rake native gem
-  (... compilation output ...)
-  mkdir -p pkg
-    Successfully built RubyGem
-    Name: my_gem
-    Version: 0.1.0
-    File: my_gem-0.1.0.gem
-  mv my_gem-0.1.0.gem pkg/my_gem-0.1.0.gem
-    Successfully built RubyGem
-    Name: my_gem
-    Version: 0.1.0
-    File: my_gem-0.1.0-x86-mingw32.gem
-  mv my_gem-0.1.0-x86-mingw32.gem pkg/my_gem-0.1.0-x86-mingw32.gem
-
-You get two gems for the price of one.
-
-And the same for JRuby extensions:
-
-  # rake java gem
-  (... compilation output ...)
-  mkdir -p pkg
-    Successfully built RubyGem
-    Name: my_gem
-    Version: 0.1.0
-    File: my_gem-0.1.0.gem
-  mv my_gem-0.1.0.gem pkg/my_gem-0.1.0.gem
-    Successfully built RubyGem
-    Name: my_gem
-    Version: 0.1.0
-    File: my_gem-0.1.0-java.gem
-  mv my_gem-0.1.0-java.gem pkg/my_gem-0.1.0-java.gem
-
-
-=== What about breaking the standards? (Customization)
-
-In case you want to bend the convention established, rake-compiler let you
-personalize several settings for <tt>Rake::ExtensionTask</tt>:
-
-    Rake::ExtensionTask.new do |ext|
-      ext.name = 'hello_world'                # indicate the name of the extension.
-      ext.ext_dir = 'ext/weird_world'         # search for 'hello_world' inside it.
-      ext.lib_dir = 'lib/my_lib'              # put binaries into this folder.
-      ext.config_script = 'custom_extconf.rb' # use instead of 'extconf.rb' default
-      ext.tmp_dir = 'tmp'                     # temporary folder used during compilation.
-      ext.source_pattern = "*.{c,cpp}"        # monitor file changes to allow simple rebuild.
-      ext.config_options << '--with-foo'      # supply additional configure options to config script.
-      ext.gem_spec = spec                     # optional indicate which gem specification
-                                              # will be used to based on.
-    end
-
-== Future is now: Cross compilation
-
-rake-compiler provides now an standardized way to generate, from Linux or OSX
-both extensions and gem binaries for Windows!
-
-It takes advantages from GCC host/target to build binaries (for target) on
-different OS (hosts).
-
-=== How I enjoy this?
-
-Besides having the development tool chain installed (GCC), you should install
-also <tt>mingw32</tt> cross compilation package.
-
-Installation depends will depend on your operating system/distribution. On
-Ubuntu and Debian machines, a simple <tt>apt-get install mingw32</tt> will be
-enough.
-
-On OSX, mingw32 is available via MacPorts: <tt>port install i386-mingw32-gcc</tt>
-(ensure you update your ports tree before hand as <tt>mingw32</tt> has been
-been broken).
-
-=== I have my tool-chain, now what?
-
-You need to build Ruby for Windows.
-
-Relax, no need to freak out! Let rake-compiler do it for you:
-
-  rake-compiler cross-ruby
-
-And you're done. It will automatically download, configure and compile latest
-stable version of Ruby for Windows, and place it into <tt>~/.rake-compiler</tt>
-
-If, instead, you want to build another version than the default one, please
-supply a <tt>VERSION</tt>:
-
-  rake-compiler cross-ruby VERSION=1.8.6-p114
-
-=== Let's build some gems!
-
-Now, you only need to use additional options in your extension definition:
-
-    Rake::ExtensionTask.new('my_extension', gem_spec) do |ext|
-      ext.cross_compile = true                # enable cross compilation (requires cross compile toolchain)
-      ext.cross_platform = 'i386-mswin32'     # forces the Windows platform instead of the default one
-                                              # configure options only for cross compile
-      ext.cross_config_options << '--with-something'
-
-      # perform alterations on the gemspec when cross compiling
-      ext.cross_compiling do |gem_spec|
-        gem_spec.post_install_message = "You installed the binary version of this gem!"
-      end
-    end
-
-By default, cross compilation targets 'i386-mingw32' which is default GCC platform
-for Ruby.
-
-To target gems for current Ruby official distribution, please force the platform
-to the one shown before.
-
-=== Magician doing some tricks, don't blink!
-
-Compiles keeps being simple:
-
-  rake cross compile
-
-And now, build your gems for Windows is just 5 more letters:
-
-  rake cross native gem
-
-And you're done, yeah.
-
-=== Take it even further
-
-You can specify against with version of Ruby you want to build the extension:
-
-  rake cross compile RUBY_CC_VERSION=1.8.6
-
-If you installed <tt>1.9.1</tt>, you can do:
-
-  rake cross compile RUBY_CC_VERSION=1.9.1
-
-Even more, you can target multiple versions (ie. 1.8.6 and 1.9.1):
-
-  rake cross compile RUBY_CC_VERSION=1.8.6:1.9.1
-
-And more exiting, bundle both binaries in one "fat" Gem:
-
-  rake cross native gem RUBY_CC_VERSION=1.8.6:1.9.1
-
-That will place binaries for 1.8 and 1.9 versions of ruby inside <tt>lib_dir</tt>
-
-  lib/1.8/my_extension.so
-  lib/1.9/my_extension.so
-
-Now is up to you to make your gem load the proper one ;-)
-
-== Future
-
-rake-compiler is a work in progress and we will appreciate feedback during the
-development of it! (and contributions too!)
-
-You can find more information about rake-compiler:
-
-Blog:      http://blog.mmediasys.com
-RubyForge: http://rubyforge.org/projects/rake-compiler
-GitHub:    http://github.com/luislavena/rake-compiler
-
-== Disclaimer
-
-If you have any trouble, don't hesitate to contact the author. As always,
-I'm not going to say "Use at your own risk" because I don't want this library
-to be risky.
-
-If you trip on something, I'll share the liability by repairing things
-as quickly as I can. Your responsibility is to report the inadequacies.
+= rake-compiler
+
+rake-compiler aims to help Gem developers deal with Ruby extensions, simplifying
+code and reducing duplication.
+
+It followss *convention over configuration* and sets a standardized structure to
+build and package both C and Java extensions in your gems.
+
+This is the result of experiences dealing with several Gems that required native
+extensions across platforms and different user configurations where details like
+portability and clarity of code were lacking.
+
+== An Overview
+
+Let's summarize what rake-compiler provides:
+
+* No custom rake tasks required. Less code duplication and errors.
+
+* Painlessly build extensions on different platforms (Linux, OSX and Windows).
+
+* Painlessly build extensions for different Ruby implementations (JRuby,
+  Rubinius and MRI).
+
+* Allow multiple extensions be compiled inside the same gem.
+
+* Mimics RubyGems installation process, so helps as a test environment.
+
+* Simplify cross platform compilation of extensions (target Windows from Linux).
+
+== I'm sold! show me how to use it! (Installation)
+
+Usage of rake-compiler is pretty much straight forward.
+
+First, you need to install the gem:
+
+  $ gem install rake-compiler
+
+== Now what? (Usage)
+
+Now that you have the gem installed, let's give your project some structure.
+
+=== Structure
+
+Let's say we want to compile an extension called 'hello_world', so we should
+organize the code and folders that will help rake-compiler do its job:
+
+    |-- ext
+    |   `-- hello_world
+    |       |-- extconf.rb
+    |       |-- HelloWorldService.java
+    |       `-- hello_world.c
+    |-- lib
+    `-- Rakefile
+
+TIP: Having a consistent folder structure will help developers and newcomers
+to find code and also contribute back to your project more easily.
+
+=== Adding the code
+
+So now it's time to introduce the code to compile our extension:
+
+    # File: Rakefile
+
+    require 'rake/extensiontask'
+
+    Rake::ExtensionTask.new('hello_world')
+
+Ok, that's it. No other line of code.
+
+If we wanted to do the same for a JRuby extension (written in Java):
+
+    # File: Rakefile
+
+    require 'rake/javaextensiontask'
+
+    Rake::JavaExtensionTask.new('hello_world')
+
+=== Compile process
+
+Those *two* lines of code automatically added the needed rake tasks to build
+the hello_world extension. Running Rake on 1.8.x/1.9 (MRI):
+
+  $ rake -T
+  (in /home/user/my_extension)
+  rake compile                # Compile the extension(s)
+  rake compile:hello_world    # Compile just the hello_world extension
+
+Simply calling <tt>compile</tt>:
+
+  $ rake compile
+
+Will do all the compile process for us, putting the result extension inside
+<tt>lib</tt> directory.
+
+NOTE: Please be aware that building C extensions requires the proper
+development environment for your Platform, which includes libraries, headers
+and build tools. Check your distro / vendor documentation on how to install it.
+
+NOTE: Building Java extensions requires the <tt>javac</tt>, part of the Java
+Development Kit (JDK). This should be included by default on Mac OS X, and
+downloadable from http://java.sun.com for other operating systems.
+
+=== Generate native gems
+
+A common usage scenario of rake-compiler is generate native gems that bundles
+your extensions.
+
+This got over-simplified with <tt>Rake::ExtensionTask</tt>:
+
+    # somewhere in your Rakefile, define your gem spec
+    spec = Gem::Specification.new do |s|
+      s.name = "my_gem"
+      s.platform = Gem::Platform::RUBY
+      s.extensions = FileList["ext/**/extconf.rb"]
+    end
+
+    # add your default gem packing task
+    Rake::GemPackageTask.new(spec) do |pkg|
+    end
+
+    # feed your ExtensionTask with your spec
+    Rake::ExtensionTask.new('hello_world', spec)
+
+Now, as usual, you can build your pure-ruby gem (standard output):
+
+  $ rake gem
+  (in /projects/oss/my_gem.git)
+  mkdir -p pkg
+    Successfully built RubyGem
+    Name: my_gem
+    Version: 0.1.0
+    File: my_gem-0.1.0.gem
+  mv my_gem-0.1.0.gem pkg/my_gem-0.1.0.gem
+
+Plus, you have the functionality to build native versions of the gem:
+
+  # rake native gem
+  (... compilation output ...)
+  mkdir -p pkg
+    Successfully built RubyGem
+    Name: my_gem
+    Version: 0.1.0
+    File: my_gem-0.1.0.gem
+  mv my_gem-0.1.0.gem pkg/my_gem-0.1.0.gem
+    Successfully built RubyGem
+    Name: my_gem
+    Version: 0.1.0
+    File: my_gem-0.1.0-x86-mingw32.gem
+  mv my_gem-0.1.0-x86-mingw32.gem pkg/my_gem-0.1.0-x86-mingw32.gem
+
+You get two gems for the price of one.
+
+And the same for JRuby extensions:
+
+  # rake java gem
+  (... compilation output ...)
+  mkdir -p pkg
+    Successfully built RubyGem
+    Name: my_gem
+    Version: 0.1.0
+    File: my_gem-0.1.0.gem
+  mv my_gem-0.1.0.gem pkg/my_gem-0.1.0.gem
+    Successfully built RubyGem
+    Name: my_gem
+    Version: 0.1.0
+    File: my_gem-0.1.0-java.gem
+  mv my_gem-0.1.0-java.gem pkg/my_gem-0.1.0-java.gem
+
+
+=== What about breaking the standards? (Customization)
+
+In case you want to bend the convention established, rake-compiler let you
+personalize several settings for <tt>Rake::ExtensionTask</tt>:
+
+    Rake::ExtensionTask.new do |ext|
+      ext.name = 'hello_world'                # indicate the name of the extension.
+      ext.ext_dir = 'ext/weird_world'         # search for 'hello_world' inside it.
+      ext.lib_dir = 'lib/my_lib'              # put binaries into this folder.
+      ext.config_script = 'custom_extconf.rb' # use instead of 'extconf.rb' default
+      ext.tmp_dir = 'tmp'                     # temporary folder used during compilation.
+      ext.source_pattern = "*.{c,cpp}"        # monitor file changes to allow simple rebuild.
+      ext.config_options << '--with-foo'      # supply additional configure options to config script.
+      ext.gem_spec = spec                     # optional indicate which gem specification
+                                              # will be used to based on.
+    end
+
+== Future is now: Cross compilation
+
+rake-compiler provides now an standardized way to generate, from Linux or OSX
+both extensions and gem binaries for Windows!
+
+It takes advantages from GCC host/target to build binaries (for target) on
+different OS (hosts).
+
+=== How I enjoy this?
+
+Besides having the development tool chain installed (GCC), you should install
+also <tt>mingw32</tt> cross compilation package.
+
+Installation depends will depend on your operating system/distribution. On
+Ubuntu and Debian machines, a simple <tt>apt-get install mingw32</tt> will be
+enough.
+
+On OSX, mingw32 is available via MacPorts: <tt>port install i386-mingw32-gcc</tt>
+(ensure you update your ports tree before hand as <tt>mingw32</tt> has been
+been broken).
+
+=== I have my tool-chain, now what?
+
+You need to build Ruby for Windows.
+
+Relax, no need to freak out! Let rake-compiler do it for you:
+
+  rake-compiler cross-ruby
+
+And you're done. It will automatically download, configure and compile latest
+stable version of Ruby for Windows, and place it into <tt>~/.rake-compiler</tt>
+
+If, instead, you want to build another version than the default one, please
+supply a <tt>VERSION</tt>:
+
+  rake-compiler cross-ruby VERSION=1.8.6-p114
+
+If you, like me, have multiple versions of MinGW packages, you can specify the
+HOST that will be used to cross compile ruby:
+
+  rake-compiler cross-ruby HOST=i386-mingw32 # (OSX mingw32 port)
+
+The host will vary depending on provider (mingw32 versus mingw-w64 projects).
+Consult the documentation and website of the MinGW package provider before
+reporting any issue.
+
+=== Let's build some gems!
+
+Now, you only need to use additional options in your extension definition:
+
+    Rake::ExtensionTask.new('my_extension', gem_spec) do |ext|
+      ext.cross_compile = true                # enable cross compilation (requires cross compile toolchain)
+      ext.cross_platform = 'i386-mswin32'     # forces the Windows platform instead of the default one
+                                              # configure options only for cross compile
+      ext.cross_config_options << '--with-something'
+
+      # perform alterations on the gemspec when cross compiling
+      ext.cross_compiling do |gem_spec|
+        gem_spec.post_install_message = "You installed the binary version of this gem!"
+      end
+    end
+
+By default, cross compilation targets 'i386-mingw32' which is default GCC platform
+for Ruby.
+
+To target gems for current Ruby official distribution, please force the platform
+to the one shown before.
+
+=== Magician doing some tricks, don't blink!
+
+Compiles keeps being simple:
+
+  rake cross compile
+
+And now, build your gems for Windows is just 5 more letters:
+
+  rake cross native gem
+
+And you're done, yeah.
+
+=== Take it even further
+
+You can specify against with version of Ruby you want to build the extension:
+
+  rake cross compile RUBY_CC_VERSION=1.8.6
+
+If you installed <tt>1.9.1</tt>, you can do:
+
+  rake cross compile RUBY_CC_VERSION=1.9.1
+
+Even more, you can target multiple versions (ie. 1.8.6 and 1.9.1):
+
+  rake cross compile RUBY_CC_VERSION=1.8.6:1.9.1
+
+And more exiting, bundle both binaries in one "fat" Gem:
+
+  rake cross native gem RUBY_CC_VERSION=1.8.6:1.9.1
+
+That will place binaries for 1.8 and 1.9 versions of ruby inside <tt>lib_dir</tt>
+
+  lib/1.8/my_extension.so
+  lib/1.9/my_extension.so
+
+Now is up to you to make your gem load the proper one ;-)
+
+=== What are you talking about? (Give me examples)
+
+I know all the above sounds like a complete foreign language (it does even for me!). So, what if I show you some examples?
+
+Check our wiki with links to the proper rake files used by many developers and projects and how they use rake-compiler.
+
+http://github.com/luislavena/rake-compiler/wiki/projects-using-rake-compiler
+
+== Future
+
+rake-compiler is a work in progress and we will appreciate feedback during the
+development of it! (and contributions too!)
+
+You can find more information about rake-compiler:
+
+* GitHub:    https://github.com/luislavena/rake-compiler
+* Issues:    https://github.com/luislavena/rake-compiler/issues
+* Blog:      http://blog.mmediasys.com
+* Docs:      http://rubydoc.info/gems/rake-compiler
+* Wiki:      https://github.com/luislavena/rake-compiler/wiki
+
+== Disclaimer
+
+If you have any trouble, don't hesitate to contact the author. As always,
+I'm not going to say "Use at your own risk" because I don't want this library
+to be risky.
+
+If you trip on something, I'll share the liability by repairing things
+as quickly as I can. Your responsibility is to report the inadequacies.

data/Rakefile

@@ -12,11 +12,9 @@
 #
 
 begin
-  require 'rake'
-rescue LoadError
-  require 'rubygems'
-  gem 'rake', '~> 0.8.3.1'
-  require 'rake'
+  require 'isolate/now'
+rescue LoadError => e
+  fail "This project uses Isolate to manage development dependencies. Please `gem install isolate` first and try again."
 end
 
 # load rakefile extensions (tasks)

data/features/step_definitions/gem.rb

@@ -17,7 +17,11 @@ Then /^a gem for '(.*)' version '(.*)' platform '(.*)' do exist in '(.*)'$/ do |
   `gem unpack #{gem_file_platform(folder, name, version, platform)} --target tmp`
   unpacked_gem_dir = unpacked_gem_dir_platform('tmp', name, version, platform)
   File.exist?(unpacked_gem_dir).should be_true
-  Dir.glob(unpacked_gem_dir << "/lib/*.#{binary_extension(platform)}").should_not be_empty
+
+  files = Dir.glob("#{unpacked_gem_dir}/lib/*.#{binary_extension(platform)}")
+  files << Dir.glob("#{unpacked_gem_dir}/lib/*/*.#{binary_extension(platform)}")
+
+  files.flatten.uniq.should_not be_empty
 end
 
 Then /^gem for platform '(.*)' get generated$/ do |platform|

data/features/support/file_template_helpers.rb

@@ -70,7 +70,7 @@ EOF
 require 'rake/extensiontask'
 Rake::ExtensionTask.new("#{extension_name}", SPEC) do |ext|
   ext.cross_compile = true
-  ext.cross_platform = ['i386-mswin32', 'i386-mingw32']
+  ext.cross_platform = ['x86-mswin32', 'x86-mingw32']
 end
 EOF
   end

data/lib/rake/extensiontask.rb

@@ -109,7 +109,7 @@ Rerun `rake` under MRI Ruby 1.8.x/1.9.x to cross/native compile.
         options = @config_options.dup
 
         # include current directory
-        cmd = ['-I.']
+        cmd = [Gem.ruby, '-I.']
 
         # if fake.rb is present, add to the command line
         if t.prerequisites.include?("#{tmp_path}/fake.rb") then
@@ -117,8 +117,8 @@ Rerun `rake` under MRI Ruby 1.8.x/1.9.x to cross/native compile.
         end
 
         # build a relative path to extconf script
-        abs_tmp_path = Pathname.new(Dir.pwd) + tmp_path
-        abs_extconf = Pathname.new(Dir.pwd) + extconf
+        abs_tmp_path = (Pathname.new(Dir.pwd) + tmp_path).realpath
+        abs_extconf = (Pathname.new(Dir.pwd) + extconf).realpath
 
         # now add the extconf script
         cmd << abs_extconf.relative_path_from(abs_tmp_path)
@@ -135,7 +135,7 @@ Rerun `rake` under MRI Ruby 1.8.x/1.9.x to cross/native compile.
           # FIXME: Rake is broken for multiple arguments system() calls.
           # Add current directory to the search path of Ruby
           # Also, include additional parameters supplied.
-          ruby cmd.join(' ')
+          sh cmd.join(' ')
         end
       end
 
@@ -378,11 +378,24 @@ Rerun `rake` under MRI Ruby 1.8.x/1.9.x to cross/native compile.
         class Object
           remove_const :RUBY_PLATFORM
           remove_const :RUBY_VERSION
+          remove_const :RUBY_DESCRIPTION if defined?(RUBY_DESCRIPTION)
           RUBY_PLATFORM = "i386-mingw32"
           RUBY_VERSION = "#{version}"
+          RUBY_DESCRIPTION = "ruby \#{RUBY_VERSION} (\#{RUBY_RELEASE_DATE}) [\#{RUBY_PLATFORM}]"
         end
+        if RUBY_PLATFORM =~ /mswin|bccwin|mingw/
+          class File
+            remove_const :ALT_SEPARATOR
+            ALT_SEPARATOR = "\\\\"
+          end
+        end
+
+        posthook = proc do
+          $ruby = "#{Gem.ruby}"
+          untrace_var(:$ruby, posthook)
+        end
+        trace_var(:$ruby, posthook)
 FAKE_RB
     end
-
   end
 end

data/spec/lib/rake/extensiontask_spec.rb

@@ -441,6 +441,8 @@ describe Rake::ExtensionTask do
       'rbconfig-1.8.6' => '/some/path/version/1.8/to/rbconfig.rb',
       'rbconfig-1.8.7' => '/some/path/version/1.8/to/rbconfig.rb',
       'rbconfig-1.9.1' => '/some/path/version/1.9.1/to/rbconfig.rb',
+      'rbconfig-1.9.2' => '/some/path/version/1.9.1/to/rbconfig.rb',
+      'rbconfig-1.9.3' => '/some/path/version/1.9.1/to/rbconfig.rb',
       'rbconfig-3.0.0' => '/some/fake/version/3.0.0/to/rbconfig.rb'
     }
   end

data/tasks/bin/cross-ruby.rake

@@ -33,16 +33,17 @@ end
 
 require 'rake/extensioncompiler'
 
-MAKE = ENV['MAKE'] || %w[gmake make].find { |c| system(c, '-v') }
+MAKE = ENV['MAKE'] || %w[gmake make].find { |c| system("#{c} -v > /dev/null 2>&1") }
 USER_HOME = File.expand_path("~/.rake-compiler")
-RUBY_CC_VERSION = "ruby-#{ENV['VERSION'] || '1.8.6-p287'}"
+RUBY_CC_VERSION = "ruby-#{ENV['VERSION'] || '1.8.6-p398'}"
 RUBY_SOURCE = ENV['SOURCE']
 
 # grab the major "1.8" or "1.9" part of the version number
 MAJOR = RUBY_CC_VERSION.match(/.*-(\d.\d).\d/)[1]
 
 # Use Rake::ExtensionCompiler helpers to find the proper host
-MINGW_HOST = Rake::ExtensionCompiler.mingw_host
+MINGW_HOST = ENV['HOST'] || Rake::ExtensionCompiler.mingw_host
+MINGW_TARGET = MINGW_HOST.gsub('msvc', '')
 
 # define a location where sources will be stored
 directory "#{USER_HOME}/sources/#{RUBY_CC_VERSION}"
@@ -59,7 +60,7 @@ CLOBBER.include("#{USER_HOME}/ruby/#{RUBY_CC_VERSION}")
 CLOBBER.include("#{USER_HOME}/config.yml")
 
 # ruby source file should be stored there
-file "#{USER_HOME}/sources/#{RUBY_CC_VERSION}.tar.gz" => ["#{USER_HOME}/sources"] do |t|
+file "#{USER_HOME}/sources/#{RUBY_CC_VERSION}.tar.bz2" => ["#{USER_HOME}/sources"] do |t|
   # download the source file using wget or curl
   chdir File.dirname(t.name) do
     if RUBY_SOURCE
@@ -72,10 +73,10 @@ file "#{USER_HOME}/sources/#{RUBY_CC_VERSION}.tar.gz" => ["#{USER_HOME}/sources"
 end
 
 # Extract the sources
-source_file = RUBY_SOURCE ? RUBY_SOURCE.split('/').last : "#{RUBY_CC_VERSION}.tar.gz"
+source_file = RUBY_SOURCE ? RUBY_SOURCE.split('/').last : "#{RUBY_CC_VERSION}.tar.bz2"
 file "#{USER_HOME}/sources/#{RUBY_CC_VERSION}" => ["#{USER_HOME}/sources/#{source_file}"] do |t|
   chdir File.dirname(t.name) do
-    t.prerequisites.each { |f| sh "tar xfz #{File.basename(f)}" }
+    t.prerequisites.each { |f| sh "tar xf #{File.basename(f)}" }
   end
 end
 
@@ -111,22 +112,13 @@ task :mingw32 do
   end
 end
 
-task :environment do
-  ENV['ac_cv_func_getpgrp_void'] =  'no'
-  ENV['ac_cv_func_setpgrp_void'] = 'yes'
-  ENV['rb_cv_negative_time_t'] = 'no'
-  ENV['ac_cv_func_memcmp_working'] = 'yes'
-  ENV['rb_cv_binary_elf' ] = 'no'
-end
-
 # generate the makefile in a clean build location
 file "#{USER_HOME}/builds/#{RUBY_CC_VERSION}/Makefile" => ["#{USER_HOME}/builds/#{RUBY_CC_VERSION}",
                                   "#{USER_HOME}/sources/#{RUBY_CC_VERSION}/Makefile.in"] do |t|
 
   options = [
-    '--target=i386-mingw32',
     "--host=#{MINGW_HOST}",
-    '--build=i686-linux',
+    "--target=#{MINGW_TARGET}",
     '--enable-shared',
     '--disable-install-doc',
     '--without-tk',
@@ -188,4 +180,5 @@ task :default do
 end
 
 desc "Build #{RUBY_CC_VERSION} suitable for cross-platform development."
-task 'cross-ruby' => [:mingw32, :environment, :install, 'update-config']
+task 'cross-ruby' => [:mingw32, :install, 'update-config']
+

data/tasks/bootstrap.rake

@@ -0,0 +1,11 @@
+desc 'Ensure all the cross compiled versions are installed'
+task :bootstrap do
+  fail "Sorry, this only works on OSX and Linux" if RUBY_PLATFORM =~ /mswin|mingw/
+
+  versions = %w(1.8.6-p398 1.9.1-p243 1.9.2-p0)
+
+  versions.each do |version|
+    puts "[INFO] Attempt to cross-compile Ruby #{version}"
+    ruby "-Ilib bin/rake-compiler cross-ruby VERSION=#{version}"
+  end
+end

data/tasks/common.rake

@@ -8,6 +8,3 @@ task :default => [:spec, :features]
 
 # make packing depend on success of running specs and features
 task :package => [:spec, :features]
-
-# publish documentation when doing a release
-task :release => [:publish]

data/tasks/gem.rake

@@ -3,7 +3,7 @@ require 'rubygems/package_task'
 GEM_SPEC = Gem::Specification.new do |s|
   # basic information
   s.name        = "rake-compiler"
-  s.version     = "0.7.1"
+  s.version     = "0.7.5"
   s.platform    = Gem::Platform::RUBY
 
   # description and details
@@ -15,7 +15,7 @@ GEM_SPEC = Gem::Specification.new do |s|
   s.required_rubygems_version = ">= 1.3.5"
 
   # dependencies
-  s.add_dependency  'rake', '>= 0.8.3', '< 0.9'
+  s.add_dependency  'rake'
 
   # development dependencies
   s.add_development_dependency 'rspec', '~> 1.2.9'
@@ -25,7 +25,8 @@ GEM_SPEC = Gem::Specification.new do |s|
   # components, files and paths
   s.files = FileList["features/**/*.{feature,rb}", "bin/rake-compiler",
                       "lib/**/*.rb", "spec/spec.opts", "spec/**/*.rb",
-                      "tasks/**/*.rake", "Rakefile", "*.{rdoc,txt,yml}"]
+                      "tasks/**/*.rake", "Rakefile", "Isolate",
+                      "*.{rdoc,txt,yml}"]
 
   s.bindir      = 'bin'
   s.executables = ['rake-compiler']

data/tasks/news.rake

@@ -1,79 +1,39 @@
-begin
-  require 'rubyforge'
-rescue LoadError
-  warn "rubyforge gem is required to generate announces, please install it (gem install rubyforge)."
-end
-
-CLEAN.include('email.txt')
-
-if defined?(RubyForge) then
-  if defined?(GEM_SPEC) then
-    desc 'Create news email file and post to RubyForge.'
-    task :announce do |t|
-      ver = ENV['VERSION'] or fail "Must supply VERSION (rake announce VERSION=x.y.z)."
-
-      # compare versions to avoid mistakes
-      unless ver == GEM_SPEC.version.to_s then
-        fail "Version mismatch (supplied and specification versions differ)."
-      end
-
-      # no homepage? why announce it then?!
-      if GEM_SPEC.homepage == 'TODO' or GEM_SPEC.homepage.nil? then
-        fail "Must define homepage in your gem specification."
-      end
-
-      # no rubyforge project? no release for you!
-      if GEM_SPEC.rubyforge_project == 'TODO' or GEM_SPEC.rubyforge_project.nil? then
-        fail "Must define rubyforge_project in your gem specification."
-      end
-
-      # instantiate a RubyForge object
-      rf = RubyForge.new.configure
-
-      # read project info and overview
-      notes = begin
-                r = File.read("README.rdoc")
-                r.split(/^(=+ .*)/)[1..4].join.strip
-              rescue
-                warn "Missing README.rdoc"
-                ''
-              end
-
-      # read changes
-      changes = begin
-                  h = File.read("History.txt")
-                  h.split(/^(===+ .*)/)[1..2].join.strip
-                rescue
-                  warn "Missing History.txt"
-                  ''
-                end
-
-      # standard fields
-      subject = "#{GEM_SPEC.name} #{GEM_SPEC.version} Released"
-      title   = "#{GEM_SPEC.name} version #{GEM_SPEC.version} has been released!"
-      body    = "#{notes}\n\nChanges:\n\n#{changes}"
-      urls    = [GEM_SPEC.homepage, "http://rubyforge.org/projects/#{GEM_SPEC.rubyforge_project}"].map { |u| "* <#{u.strip}>" }.join("\n")
-
-      puts "Logging in RubyForge..."
-      rf.login
-
-      puts "Generating email.txt..."
-      File.open("email.txt", "w") do |mail|
-        mail.puts "Subject: [ANN] #{subject}"
-        mail.puts
-        mail.puts title
-        mail.puts 
-        mail.puts urls
-        mail.puts
-        mail.puts body
-      end
-      puts "Created email.txt"
-
-      puts "Posting news for #{GEM_SPEC.name} version #{GEM_SPEC.version}..."
-      rf.post_news GEM_SPEC.rubyforge_project, subject, "#{title}\n\n#{body}"
-      puts "Done."
-    end
-  else
-    warn "no GEM_SPEC is found or defined. 'announce' task cannot work without it."
-  end
+desc 'Generate email template to standard output'
+task :announce do
+  fail "no GEM_SPEC is found or defined. 'announce' task cannot work without it." unless defined?(GEM_SPEC)
+
+  # read project info and overview
+  notes = begin
+            r = File.read("README.rdoc")
+            r.split(/^(=+ .*)/)[1..4].join.strip
+          rescue
+            warn "Missing README.rdoc"
+            ''
+          end
+
+  # read changes
+  changes = begin
+              h = File.read("History.txt")
+              h.split(/^(===+ .*)/)[1..2].join.strip
+            rescue
+              warn "Missing History.txt"
+              ''
+            end
+
+  # standard fields
+  subject = "#{GEM_SPEC.name} #{GEM_SPEC.version} Released"
+  title   = "#{GEM_SPEC.name} version #{GEM_SPEC.version} has been released!"
+  body    = "#{notes}\n\nChanges:\n\n#{changes}"
+  urls    = [GEM_SPEC.homepage].map { |u| "* <#{u.strip}>" }.join("\n")
+
+  puts "=" * 80, ""
+  puts "Subject: [ANN] #{subject}"
+  puts
+  puts title
+  puts
+  puts urls
+  puts
+  puts body
+  puts
+  puts "=" * 80, ""
 end

data/tasks/release.rake

@@ -1,71 +1,26 @@
-begin
-  require 'rubyforge'
-rescue LoadError
-  warn "rubyforge gem is required to generate releases, please install it (gem install rubyforge)."
-end
-
-if defined?(RubyForge) then
-  if defined?(GEM_SPEC) then
-    desc 'Package and upload to RubyForge'
-    task :release => [:clobber, :package] do |t|
-      ver = ENV['VERSION'] or fail "Must supply VERSION (rake release VERSION=x.y.z)."
-
-      # compare versions to avoid mistakes
-      unless ver == GEM_SPEC.version.to_s then
-        fail "Version mismatch (supplied and specification versions differ)."
-      end
-
-      # no rubyforge project? no release for you!
-      if GEM_SPEC.rubyforge_project == 'TODO' or GEM_SPEC.rubyforge_project.nil? then
-        fail "Must define rubyforge_project in your gem specification."
-      end
-
-      # instantiate a RubyForge object
-      rf = RubyForge.new
+desc 'Package gems and upload to RubyGems'
+task :release, :version, :needs => [:package] do |t, args|
+  args.with_defaults(:version => "")
+  ver = args.version
 
-      # read project info and overview
-      notes = begin
-                r = File.read("README.rdoc")
-                r.split(/^(=+ .*)/)[1..4].join.strip
-              rescue
-                warn "Missing README.rdoc"
-                ''
-              end
+  fail "no GEM_SPEC is found or defined. 'release' task cannot work without it." unless defined?(GEM_SPEC)
 
-      # read changes
-      changes = begin
-                  h = File.read("History.txt")
-                  h.split(/^(===+ .*)/)[1..2].join.strip
-                rescue
-                  warn "Missing History.txt"
-                  ''
-                end
-
-      # build the configuration for the release
-      config = Hash.new
-      config["release_notes"] = notes
-      config["release_changes"] = changes
-      config["preformatted"] = true
-
-      # prepare configuration
-      rf.configure config
-
-      files = FileList["pkg/#{GEM_SPEC.name}-#{GEM_SPEC.version}*.*"].to_a
-      fail "No files found for the release." if files.empty?
+  # compare versions to avoid mistakes
+  unless ver == GEM_SPEC.version.to_s then
+    fail "Version mismatch (supplied and specification versions differ)."
+  end
 
-      puts "Logging in RubyForge..."
-      rf.login
+  files = FileList["pkg/#{GEM_SPEC.name}-#{GEM_SPEC.version}*.*"].to_a
+  fail "No files found for the release." if files.empty?
 
-      puts "Files to upload:"
-      files.each do |f|
-        puts "  * #{f}"
-      end
+  puts "Files to release:"
+  files.each do |f|
+    puts "  * #{f}"
+  end
 
-      puts "Releasing #{GEM_SPEC.name} version #{GEM_SPEC.version}..."
-      rf.add_release GEM_SPEC.rubyforge_project, GEM_SPEC.name, GEM_SPEC.version, *files
-      puts "Done."
-    end
-  else
-    warn "no GEM_SPEC is found or defined. 'release' task cannot work without it."
+  puts "Releasing #{GEM_SPEC.name} version #{GEM_SPEC.version}..."
+  files.each do |f|
+    system "gem push #{f}"
   end
+  puts "Done."
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: rake-compiler
 version: !ruby/object:Gem::Version 
-  hash: 1
+  hash: 9
   prerelease: false
   segments: 
   - 0
   - 7
-  - 1
-  version: 0.7.1
+  - 5
+  version: 0.7.5
 platform: ruby
 authors: 
 - Luis Lavena
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-08-07 00:00:00 -03:00
+date: 2010-11-25 00:00:00 -03:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -26,19 +26,10 @@ dependencies:
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
-        hash: 57
+        hash: 3
         segments: 
         - 0
-        - 8
-        - 3
-        version: 0.8.3
-    - - <
-      - !ruby/object:Gem::Version 
-        hash: 25
-        segments: 
-        - 0
-        - 9
-        version: "0.9"
+        version: "0"
   type: :runtime
   version_requirements: *id001
 - !ruby/object:Gem::Dependency 
@@ -115,15 +106,15 @@ files:
 - spec/spec_helper.rb
 - spec/support/capture_output_helper.rb
 - tasks/bin/cross-ruby.rake
+- tasks/bootstrap.rake
 - tasks/common.rake
 - tasks/cucumber.rake
 - tasks/gem.rake
 - tasks/news.rake
-- tasks/rdoc.rake
-- tasks/rdoc_publish.rake
 - tasks/release.rake
 - tasks/rspec.rake
 - Rakefile
+- Isolate
 - README.rdoc
 - History.txt
 - LICENSE.txt

data/tasks/rdoc.rake

@@ -1,15 +0,0 @@
-begin
-  require 'rdoc/task'
-rescue LoadError
-  warn "RDoc 2.4.3+ gem is required, please install it (gem install rdoc)."
-end
-
-if defined?(RDoc) then
-  DOC = RDoc::Task.new(:rdoc) do |rd|
-    rd.title    = 'rake-compiler -- Documentation'
-    rd.main     = 'README.rdoc'
-    rd.rdoc_dir = 'doc/api'
-    rd.options << '--line-numbers' << '--main'  << 'README.rdoc' << '--title' << 'rake-compiler -- Documentation'
-    rd.rdoc_files.include %w(README.rdoc LICENSE.txt History.txt lib/**/*.rb)
-  end
-end

data/tasks/rdoc_publish.rake

@@ -1,41 +0,0 @@
-begin
-  require 'rubyforge'
-rescue LoadError
-  warn "rubyforge gem is required to generate releases, please install it (gem install rubyforge)."
-end
-
-if defined?(RubyForge) then
-  if defined?(DOC) && defined?(GEM_SPEC) then
-    desc "Publish RDoc to RubyForge"
-    task :publish => [:clobber_rdoc, :rdoc] do
-      config_file = File.expand_path('~/.rubyforge/user-config.yml')
-      fail "You need rubyforge properly configured." unless File.exist?(config_file)
-
-      # no rubyforge project? no release for you!
-      if GEM_SPEC.rubyforge_project == 'TODO' or GEM_SPEC.rubyforge_project.nil? then
-        fail "Must define rubyforge_project in your gem specification."
-      end
-
-      # use YAML to load configuration file
-      config = YAML.load_file(config_file)
-
-      host = "#{config['username']}@rubyforge.org"
-      remote_dir = "/var/www/gforge-projects/#{GEM_SPEC.rubyforge_project}/"
-      local_dir = DOC.rdoc_dir
-
-      # use PuTTY pscp or scp on other platforms
-      ssh_exe = RUBY_PLATFORM =~ /mswin|mingw/ ? 'pscp' : 'scp'
-
-      # construct the command
-      cmd = [ssh_exe]
-      cmd << '-r' << '-q'  # recursive and quiet options
-      cmd << "#{local_dir}/*"
-      cmd << "#{host}:#{remote_dir}"
-
-      puts "Publishing RDocs to RubyForge..."
-      sh cmd.join(' ')
-    end
-  else
-    warn "You need a GEM_SPEC and DOC rdoc definitions present. task publish not defined."
-  end
-end