rake-compiler-dock

Easy to use and reliable cross compiler environment for building Windows, Linux, Mac and JRuby binary gems.

It provides cross compilers and Ruby environments for 2.4 and newer versions of the RubyInstaller and Linux runtime environments. They are prepared for use with rake-compiler. It is used by many gems with C or JRuby extentions.

This is kind of successor of rake-compiler-dev-box. It is wrapped as a gem for easier setup, usage and integration and is based on lightweight Docker containers. It is also more reliable, since the underlying docker images are versioned and immutable.

Installation

Install docker following the instructions on the docker website … or install docker-toolbox for Windows and OSX or boot2docker on Windows or OS X .

Install rake-compiler-dock as a gem. The docker image is downloaded later on demand:

$ gem install rake-compiler-dock

… or build your own gem and docker image:

$ git clone https://github.com/rake-compiler/rake-compiler-dock
$ rake install

Usage

Rake-compiler-dock provides the necessary tools to build Ruby extensions for Windows and Linux written in C and C++ and JRuby written in Java. It is intended to be used in conjunction with rake-compiler’s cross build capability. Your Rakefile should enable cross compilation like so:

ruby exttask = Rake::ExtensionTask.new('my_extension', my_gem_spec) do |ext| ext.cross_compile = true ext.cross_platform = %w[x86-mingw32 x64-mingw-ucrt x64-mingw32 x86-linux x86_64-linux x86_64-darwin arm64-darwin] end

See below, how to invoke cross builds in your Rakefile.

Additionally it may also be used to build ffi based binary gems like libusb, but currently doesn’t provide any additional build helpers for this use case, beyond docker invocation and cross compilers.

Interactive Usage

Rake-compiler-dock offers the shell command rake-compiler-dock and a ruby API for issuing commands within the docker image, described below. There are dedicated images for x86-mingw32, x64-mingw-ucrt, x64-mingw32, x86-linux, x86_64-linux, x86_64-darwin, arm64-darwin and jruby targets. The images contain all supported cross ruby versions, with the exception of x64-mingw32, which has versions before 3.1 only, and x64-mingw-ucrt, which has only ruby-3.1+. This is to match the changed platform of RubyInstaller-3.1.

rake-compiler-dock without arguments starts an interactive shell session. This is best suited to try out and debug a build. It mounts the current working directory into the docker environment. All changes below the current working directory are shared with the host. But note, that all other changes to the file system of the container are dropped at the end of the session - the docker image is static for a given version. rake-compiler-dock can also take the build command(s) from STDIN or as command arguments.

All commands are executed with the same user and group of the host. This is done by copying user account data into the container and sudo to it.

To build x86 Windows and x86_64 Linux binary gems interactively, it can be called like this:

user@host:$ cd your-gem-dir/
user@host:$ rake-compiler-dock   # this enters a container with an interactive shell for x86 Windows (default)
user@5b53794ada92:$ bundle
user@5b53794ada92:$ rake cross native gem
user@5b53794ada92:$ exit
user@host:$ ls pkg/*.gem
your-gem-1.0.0.gem  your-gem-1.0.0-x86-mingw32.gem

user@host:$ RCD_PLATFORM=x86_64-linux rake-compiler-dock   # this enters a container for amd64 Linux target
user@adc55b2b92a9:$ bundle
user@adc55b2b92a9:$ rake cross native gem
user@adc55b2b92a9:$ exit
user@host:$ ls pkg/*.gem
your-gem-1.0.0.gem  your-gem-1.0.0-x86_64-linux.gem

Or non-interactive:

user@host:$ rake-compiler-dock bash -c "bundle && rake cross native gem"

The environment variable RUBY_CC_VERSION is predefined as described below.

If necessary, additional software can be installed, prior to the build command. This is local to the running session, only.

For Windows and Mac:

sudo apt-get update && sudo apt-get install your-package

For Linux:

sudo yum install your-package

You can also choose between different executable ruby versions by rvm use <version> . The current default is 3.1.

As a CI System Container

The OCI images provided by rake-compiler-dock can be used without the rake-compiler-dock gem or wrapper. This may be useful if your CI pipeline is building native gems.

For example, a Github Actions job might look like this:

yaml jobs: native-gem: name: "native-gem" runs-on: ubuntu-latest container: image: "larskanis/rake-compiler-dock-mri-x86_64-linux:1.2.0" steps: - uses: actions/checkout@v2 - run: bundle install && bundle exec rake gem:x86_64-linux:rcd - uses: actions/upload-artifact@v2 with: name: native-gem path: gems retention-days: 1

Where the referenced rake task might be defined by:

``` ruby cross_platforms = [“x64-mingw32”, “x86_64-linux”, “x86_64-darwin”, “arm64-darwin”]

namespace “gem” do cross_platforms.each do |platform| namespace platform do task “rcd” do Rake::Task[“native:#platform”].invoke Rake::Task[“pkg/#rcee_precompiled_specrcee_precompiled_spec.full_name-#Gem::Platform.new(platform).gem”].invoke end end end end

```

For an example of rake tasks that support this style of invocation, visit https://github.com/flavorjones/ruby-c-extensions-explained/tree/main/precompiled

JRuby support

Rake-compiler-dock offers a dedicated docker image for JRuby. JRuby doesn’t need a complicated cross build environment like C-ruby, but using Rake-compiler-dock for JRuby makes building binary gems more consistent.

To build java binary gems interactively, it can be called like this:

user@host:$ cd your-gem-dir/
user@host:$ RCD_RUBYVM=jruby rake-compiler-dock   # this enters a container with an interactive shell
user@5b53794ada92:$ ruby -v
jruby 9.2.5.0 (2.5.0) 2018-12-06 6d5a228 OpenJDK 64-Bit Server VM 10.0.2+13-Ubuntu-1ubuntu0.18.04.4 on 10.0.2+13-Ubuntu-1ubuntu0.18.04.4 +jit [linux-x86_64]
user@5b53794ada92:$ bundle
user@5b53794ada92:$ rake java gem
user@5b53794ada92:$ exit
user@host:$ ls pkg/*.gem
your-gem-1.0.0.gem  your-gem-1.0.0-java.gem

Add to your Rakefile

To make the build process reproducible for other parties, it is recommended to add rake-compiler-dock to your Rakefile. This can be done like this:

ruby task 'gem:native' do require 'rake_compiler_dock' sh "bundle package --all" # Avoid repeated downloads of gems by using gem files from the host. %w[ x86-mingw32 x64-mingw-ucrt x64-mingw32 x86-linux x86_64-linux arm-linux aarch64-linux x86_64-darwin arm64-darwin ].each do |plat| RakeCompilerDock.sh "bundle --local && rake native:#{plat} gem", platform: plat end RakeCompilerDock.sh "bundle --local && rake java gem", rubyvm: :jruby end

This runs the bundle and rake commands once for each platform. That is once for the jruby gems and 6 times for the specified MRI platforms.

Run builds in parallel

rake-compiler-dock uses dedicated docker images per build target (since rake-compiler-dock-1.0). Because each target runs in a separate docker container, it is simple to run all targets in parallel. The following example defines rake gem:native as a multitask and separates the preparation which should run only once. It also shows how gem signing can be done with parallel builds. Please note, that parallel builds only work reliable, if the specific platform gem is requested (instead of just “rake gem”).

```ruby namespace “gem” do task ‘prepare’ do require ‘rake_compiler_dock’ require ‘io/console’ sh “bundle package –all” sh “cp ~/.gem/gem-*.pem build/gem/ || true” ENV[“GEM_PRIVATE_KEY_PASSPHRASE”] = STDIN.getpass(“Enter passphrase of gem signature key: “) end

exttask.cross_platform.each do |plat|
  desc "Build all native binary gems in parallel"
  multitask 'native' => plat

  desc "Build the native gem for #{plat}"
  task plat => 'prepare' do
    RakeCompilerDock.sh <<-EOT, platform: plat
      (cp build/gem/gem-*.pem ~/.gem/ || true) &&
      bundle --local &&
      rake native:#{plat} pkg/#{exttask.gem_spec.full_name}-#{plat}.gem
    EOT
  end
end   end ```

Add to your Gemfile

Rake-compiler-dock uses semantic versioning, so you should add it into your Gemfile, to make sure, that future changes will not break your build.

ruby gem 'rake-compiler-dock', '~> 1.2'

See the wiki for projects which make use of rake-compiler-dock.

Environment Variables

Rake-compiler-dock makes use of several environment variables.

The following variables are recognized by rake-compiler-dock:

RCD_RUBYVM - The ruby VM and toolchain to be used. Must be one of mri, jruby.
RCD_PLATFORM - The target rubygems platform. Must be a space separated list out of x86-mingw32, x64-mingw-ucrt, x64-mingw32, x86-linux, x86_64-linux, arm-linux, aarch64-linux, x86_64-darwin and arm64-darwin. It is ignored when rubyvm is set to :jruby.
RCD_IMAGE - The docker image that is downloaded and started. Defaults to “larskanis/rake-compiler-dock:IMAGE_VERSION” with an image version that is determined by the gem version.

The following variables are passed through to the docker container without modification:

http_proxy, https_proxy, ftp_proxy - See Frequently asked questions for more details.
GEM_PRIVATE_KEY_PASSPHRASE - To avoid interactive password prompts in the container.

The following variables are provided to the running docker container:

RCD_IMAGE - The full docker image name the container is running on.
RCD_HOST_RUBY_PLATFORM - The RUBY_PLATFORM of the host ruby.
RCD_HOST_RUBY_VERSION - The RUBY_VERSION of the host ruby.
RUBY_CC_VERSION - The target ruby versions for rake-compiler. The default is defined in the Dockerfile, but can be changed as a parameter to rake.
RCD_MOUNTDIR - The directory which is mounted into the docker container. Defaults to pwd.
RCD_WORKDIR - The working directory within the docker container. Defaults to pwd.

Other environment variables can be set or passed through to the container like this:

ruby RakeCompilerDock.sh "rake cross native gem OPENSSL_VERSION=#{ENV['OPENSSL_VERSION']}"

More information

See Frequently asked questions and

Contributing

Fork it ( https://github.com/rake-compiler/rake-compiler-dock/fork )
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Add some feature')
Push to the branch (git push origin my-new-feature)
Create a new Pull Request