mruby-cli is a platform to build native command line applications for Linux, Windows, and OS X. It p...
A utility for setting up a CLI with mruby that compiles binaries to Linux, OS X, and Windows.
You'll need the following installed and in your
On Mac OS X and Windows, Docker Toolbox is the recommended way to install Docker and docker-compose (does not work on windows).
To generate a new mruby CLI, there's a
$ mruby-cli --setup
This will generate a foldercontaining a basic skeleton for getting started. Once you're in the folder, you can build all the binaries:
$ docker-compose run compile
You'll be able to find the binaries in the following directories:
You should be able to run the respective binary that's native on your platform. There's a
shellservice that can be used as well. In the example below,
mruby-cli --setup hello_worldwas run.
$ docker-compose run shell [email protected]:/home/mruby/code# mruby/build/host/bin/hello_world Hello World
When running on a windows system
docker-compose run, you need to add the flag
-d. For instance,
docker-compose run -d compile. If you don't add it, you will got the following error:
[31mERROR Please pass the -d flag when using `docker-compose run`.
Each app will be generated with a Dockerfile that inherits a base image.
You can pull the image from docker hub here: https://registry.hub.docker.com/u/hone/mruby-cli/
The Dockerfile for the base image is available on github: https://github.com/hone/mruby-cli-docker
Building the canonical hello world example in mruby-cli is quite simple. The two files of note from the generate skeleton are
mrbgem.rake. The CLI hooks into the
__main__method defined here and passes all the arguments as
ruby def __main__(argv) puts "Hello World" end
The rubygems equivalent is mrbgems. mgem-list contains a list of mgems you can pull from. By default mruby does not include everything in the kitchen sink like MRI. This means to even get
puts, we need to include the
mruby-print. The list of core gems can be found here. Adding dependencies is simple, you just need to add a line near the bottom of your
mrbgem.rakewith the two arguments: name and where it comes from.
mrbgem.rake: ```ruby MRuby::Gem::Specification.new('helloworld') do |spec| spec.license = 'MIT' spec.author = 'Terence Lee' spec.summary = 'Hello World' spec.bins = ['helloworld']
spec.adddependency 'mruby-print', :core => 'mruby-print' spec.adddependency 'mruby-mtest', :mgem => 'mruby-test' end ```
The app is built from two parts a C wrapper in
tools/and a mruby part in
mrblib/. The C wrapper is fairly minimal and executes the
__main__method in mruby and instantiates
ARGVand passes it to the mruby code. You won't need to touch the C wrapper. The rest of the CLI is written in mruby. You can't have subfolders in
mrblib/but you can have as many files in
mrblib/. All these files are precompiled into mruby bytecode The build tool for mruby is written in CRuby (MRI).
mruby-cligenerates two kinds of tests: mtest and bintest.
These tests are unit tests, are written in mruby, and go in the
test/directory. It uses the mrbgem
mruby-mtest. The available methods to be used can be found here. To run the tests, just execute:
$ docker-compose run mtest
These are integration tests, are written in CRuby (MRI), and go in the
bintest/directory. It tests the status and output of the host binary inside a docker container. To run them just execute:
$ docker-compose run bintest
mruby-cliitself is an app generated by
mruby-cli, so you can explore this repo on how to build one.
This app is built as a
mruby-cliapp. To compile the binaries, you must type
docker-compose run compile
and find the binaries in the appropriate directories (
The docker container contains the necessary cross toolchain to compile a binary for each supported target. That's why it is checked before running a rake task if it is run inside a container.
Indeed, just using
rake compilewill not work out of the box because the main build is designed to compile on a 64-bit Linux host. It could work if you are on a 64-Linux host and you have an cross toolchain equivalent to the one we provide into the docker container.
This means that if you want to add a new rake task
my_task, you need to add it to the
docker-compose.ymlto make it available through
docker-compose run my_task.
docker-compose run release
After this command finishes, you'll see the releases for each target in the
We can package the ad hoc release as deb, rpm, msi, or dmg for the following Linux.
To create all the package, just type
docker-compose run package