Rakudo

This is Rakudo, a Raku Programming Language compiler for the MoarVM, JVM and Javascript virtual machines. This directory contains only the Rakudo compiler itself; it does not contain any of the modules, documentation, or other items that would normally come with a full Raku distribution. If you're after more than just the bare compiler, please download the latest Rakudo Star package. Rakudo is currently the primary implementation of the Raku language. The Rakudo compiler has moar , jvm and js backends. Note that each backend has a different set of features. Recent changes and feature additions are documented in the docs/ChangeLog text file. See the INSTALL.md file for detailed prerequisites and build and installation instructions. Check CAVEATS.md for platform specific notes. The general process for building is running perl Configure.pl with the desired configuration options (common options listed below), and then running make or make install . Optionally, you may run make spectest to test your build on Roast, the Official Raku test suite. To update the test suite, run make spectest update . Installation of Rakudo simply requires building and running make install . Note that this step is necessary for running Rakudo from outside the build directory. But don't worry, it installs locally by default, so you don't need any administrator privileges for carrying out this step. Please be aware, that this will install MoarVM and NQP into your given --prefix before Configure.pl exits. Alternatively, feel free to git clone and manually and install them individually. Configuration flags can be passed to MoarVM's Configure.pl using the --moar-option flag. For example, if you wish to use Clang when GCC is the default compiler selected for your OS, use the --compiler flag: For more information on how MoarVM can be configured, view MoarVM's Configure.pl. If you get a java.lang.OutOfMemoryError: Java heap space error building rakudo on the JVM, you may need to modify your NQP runner to limit memory use. e.g. edit the nqp-j / nqp-j.bat executable (found wherever you installed to, or in the install/bin directory) to include -Xms500m -Xmx3g as options passed to java. Alternatively, you can set JAVA OPTS env var; e.g. export JAVA OPTS="-Xmx51200000000" Please be aware, that this will install NQP into your given --prefix before Configure.pl exits. By supplying combinations of backends to the --backends flag, you can get two or three backends built in the same prefix. The first backend you supply in the list is the one that gets the rakudo name as a symlink, and all backends are installed separately as rakudo-m or rakudo-j for Rakudo on MoarVM, or JVM respectively. $ perl Configure.pl --backends=moar,jvm --gen-moar --relocatable $ perl Configure.pl --backends=ALL --gen-moar --relocatable The roast test suite is installed as the t/spec directory under your rakudo directory. If your installed rakudo source directory doesn't have t/spec installed, then you can clone it like this: Note the rakudo code includes an entry in its .gitignore file so git will ignore any content under t/spec . To run a single test, one must use make because of the tooling required to run the spectests. For example: There are several mailing lists, IRC channels, and wikis available with help for the Raku Programming Language and Rakudo. Figuring out the right one to use is often the biggest battle. Here are some rough guidelines: The central hub for Raku information is raku.org. This is always a good starting point. If you have a question about Raku syntax or the right way to approach a problem using Raku, you probably want the “[email protected]” mailing list or the irc.libera.chat/ raku IRC channel. The mailing list is primarily for the people who want to use Raku to write programs, so newbie questions are welcomed there. Newbie questions are also welcome on the raku channel; the Rakudo development teams tend to hang out there and are generally glad to