Lightweight Ruby
C Ruby Yacc C++ Batchfile Shell
Latest commit a9f7b41 Feb 16, 2017 @matz matz committed on GitHub Merge pull request #3460 from AltimitSystems/android.rake-ndk-clang
Additional options for Android build script.
Failed to load latest commit information.
benchmark Remove benchmarks not in mruby Apr 24, 2015
bin add mruby sources Apr 20, 2012
doc Removed trailing spaces Sep 28, 2016
examples Added example build script for Android armeabi-v7a NEON hardware FPU Feb 16, 2017
include Build fix for 32-bit clang 3.8/3.9 with MRB_INT64 Feb 16, 2017
lib/mruby Change to to make Ruby 1.9 Happy Sep 7, 2015
mrbgems Configure callinfo target_class as CRuby; ref #3429 Feb 16, 2017
mrblib Integral#step without arg should loop forever as CRuby does. Jan 20, 2017
src Move #__id__ to BasicObject; ref #3417 Feb 15, 2017
tasks Android toolchain separated target architecture compile flags (ctarge… Feb 16, 2017
test Move BasicObject#method_missing to Kernel#method_missing; ref #3417 Feb 15, 2017
.gitignore Move guides location Oct 8, 2015
.travis.yml Remove webhook notification for Travis CI Nov 17, 2016
.yardopts Improved mrb_args_format table Oct 20, 2015
AUTHORS Update AUTHORS Nov 24, 2016 Fix typos in documentation and error messages [skip ci] Jun 19, 2015
LEGAL Change mruby-random License to MIT Apr 8, 2013
MITL Update Copyright to 2017 Jan 6, 2017
Makefile remove trailing spaces Apr 30, 2014
NEWS add document Apr 20, 2012 Small grammar fix Jan 20, 2016
Rakefile fix `rake doc` error Oct 9, 2015
TODO update TODO entries; close #2831 Nov 16, 2015
appveyor.yml Add appveyor.yml for Visual Studio 2015/2013 Mar 15, 2016
appveyor_config.rb Create appveyor_config.rb Mar 15, 2016
build_config.rb Update example lines of mrbgems in build_config.rb; ref #3414 Jan 25, 2017
minirake Fix build error when trace mode Feb 10, 2017
mruby-source.gemspec Switch gem API to constants only Sep 6, 2015
travis_config.rb Enable full-debug build on travis using `MRB_ENABLE_DEBUG_HOOK` Nov 17, 2015

Build Status

What is mruby

mruby is the lightweight implementation of the Ruby language complying to (part of) the ISO standard. Its syntax is Ruby 1.9 compatible.

mruby can be linked and embedded within your application. We provide the interpreter program "mruby" and the interactive mruby shell "mirb" as examples. You can also compile Ruby programs into compiled byte code using the mruby compiler "mrbc". All those tools reside in the "bin" directory. "mrbc" is also able to generate compiled byte code in a C source file, see the "mrbtest" program under the "test" directory for an example.

This achievement was sponsored by the Regional Innovation Creation R&D Programs of the Ministry of Economy, Trade and Industry of Japan.

How to get mruby

The stable version 1.2.0 of mruby can be downloaded via the following URL:

The latest development version of mruby can be downloaded via the following URL:

The trunk of the mruby source tree can be checked out with the following command:

$ git clone

You can also install and compile mruby using ruby-install, ruby-build or rvm.

mruby home-page

The URL of the mruby home-page is:

Mailing list

We don't have a mailing list, but you can use GitHub issues.

How to compile and install (mruby and gems)

See the doc/guides/ file.

Running Tests

To run the tests, execute the following from the project's root directory.

$ make test


$ ruby ./minirake test

How to customize mruby (mrbgems)

mruby contains a package manager called mrbgems. To create extensions in C and/or Ruby you should create a GEM. For a documentation of how to use mrbgems consult the file doc/guides/ For example code of how to use mrbgems look into the folder examples/mrbgems/.


mruby is released under the MIT License.

Note for License

mruby has chosen a MIT License due to its permissive license allowing developers to target various environments such as embedded systems. However, the license requires the display of the copyright notice and license information in manuals for instance. Doing so for big projects can be complicated or troublesome. This is why mruby has decided to display "mruby developers" as the copyright name to make it simple conventionally. In the future, mruby might ask you to distribute your new code (that you will commit,) under the MIT License as a member of "mruby developers" but contributors will keep their copyright. (We did not intend for contributors to transfer or waive their copyrights, Actual copyright holder name (contributors) will be listed in the AUTHORS file.)

Please ask us if you want to distribute your code under another license.

How to Contribute

See the contribution guidelines, and then send a pull request to We consider you have granted non-exclusive right to your contributed code under MIT license. If you want to be named as one of mruby developers, please include an update to the AUTHORS file in your pull request.