Symbolic links of the binary files generated under build/bin are being created. However, these symbolic links are created with absolute paths, which can sometimes result in incorrect links. For instance, in my project, I am using Docker for the builds. When building on a Docker image, the binary is created at /src/build/host/mruby, but it appears at a different path when viewed from the host.
$ rake build
-- snip --
$ pwd
/home/buty4649/src/github.com/buty4649/rf
# The actual mruby binary is located under build/host/bin
$ ls -lah ./build/host/bin/mruby
-rwxr-xr-x 1 buty4649 buty4649 12M Oct 21 12:22 ./build/host/bin/mruby
# The path of mruby under build/bin is incorrect
$ ls -lah ./build/bin/mruby
lrwxrwxrwx 1 buty4649 buty4649 25 Oct 21 12:22 ./build/bin/mruby -> /src/build/host/bin/mruby
$ ls -lah /src/build/host/bin/mruby
/bin/ls: cannot access '/src/build/host/bin/mruby': No such file or directory
I suspect that the issue is caused by calling File.expand_path when creating the symbolic links, as seen here: https://github.com/mruby/mruby/blob/master/lib/mruby/build.rb#L400