1. 30 Oct, 2013 8 commits
  2. 26 Oct, 2013 4 commits
  3. 25 Oct, 2013 1 commit
  4. 24 Oct, 2013 3 commits
  5. 23 Oct, 2013 2 commits
  6. 22 Oct, 2013 2 commits
  7. 20 Oct, 2013 1 commit
  8. 19 Oct, 2013 1 commit
  9. 15 Oct, 2013 5 commits
  10. 10 Oct, 2013 3 commits
  11. 09 Oct, 2013 1 commit
  12. 08 Oct, 2013 1 commit
  13. 05 Oct, 2013 2 commits
  14. 04 Oct, 2013 2 commits
  15. 02 Oct, 2013 1 commit
  16. 01 Oct, 2013 3 commits
    • Yukihiro "Matz" Matsumoto's avatar
      Merge pull request #1523 from wrl/relative-gembox-nokeyword · 34cdc21c
      Yukihiro "Matz" Matsumoto authored
      Implement gembox-relative gemdir paths
      34cdc21c
    • William Light's avatar
      Fix for caller_dir relative gems · 72d6db8b
      William Light authored
      72d6db8b
    • William Light's avatar
      Implement gembox-relative gemdir paths · 7c3f06dd
      William Light authored
      In the case where a relative path is specified to a gembox from
      build_config.rb, it was previously tricky to specify relative gem paths
      from inside that gembox.
      
      For example, consider a project in which mruby is checked out as a
      submodule in the project root:
      
      	+- project_root
      	   |
      	   +- mruby/
      	   |  |
      	   |  +- build_config.rb
      	   |  |
      	   |  +- ...
      	   |
      	   +- my_gembox/
      	      |
      	      +- my_gembox.gembox
      	      |
      	      +- my_gem/
      	         |
      	         +- mrbgem.rake
      	         |
      	         +- ...
      
      If build_config.rb refers to my_gembox with a relative path, it's
      difficult for my_gembox to then refer to my_gem. With this proposed
      change, my_gembox.gembox can look like this:
      
      	MRuby::GemBox.new do |conf|
      	  conf.gem "my_gem"
      	end
      7c3f06dd