summaryrefslogtreecommitdiffhomepage
path: root/mrbgems/mruby-test
diff options
context:
space:
mode:
authorZachary Scott <[email protected]>2015-09-02 23:11:18 -0400
committerZachary Scott <[email protected]>2015-09-03 01:02:53 -0400
commitbacb8268682e8d931a00e7894ed7904bc789d8c4 (patch)
tree9b34d3025d195741cc5c028fad9dd7962beec04a /mrbgems/mruby-test
parentcc0b28373a304541308b6386f4be15aedf30ce43 (diff)
downloadmruby-bacb8268682e8d931a00e7894ed7904bc789d8c4.tar.gz
mruby-bacb8268682e8d931a00e7894ed7904bc789d8c4.zip
Add build_mrbtest after config block is evaluated
This allows us to add `enable_test` anywhere in a build target, without having to worry about the order in which they are included. Previously, there was a bug that occured when adding 'mruby-test' gem to dependencies before additional gems. Instead of adding the 'mruby-test' gem dependency manually to a test build, we now only need to call `enable_test` in the target. This also allows us to call `test_enabled?` downstream when running mruby tests ourselves. /cc #2924
Diffstat (limited to 'mrbgems/mruby-test')
-rw-r--r--mrbgems/mruby-test/mrbgem.rake2
1 files changed, 1 insertions, 1 deletions
diff --git a/mrbgems/mruby-test/mrbgem.rake b/mrbgems/mruby-test/mrbgem.rake
index 8370f4713..b6b247ff6 100644
--- a/mrbgems/mruby-test/mrbgem.rake
+++ b/mrbgems/mruby-test/mrbgem.rake
@@ -32,7 +32,7 @@ MRuby::Gem::Specification.new('mruby-test') do |spec|
end
end
- gem_table = build.gems.generate_gem_table self
+ gem_table = build.gems.generate_gem_table build
build.gems.each do |g|
test_rbobj = g.test_rbireps.ext(exts.object)