summaryrefslogtreecommitdiffhomepage
path: root/include/mruby.h
diff options
context:
space:
mode:
authorKOBAYASHI Shuji <[email protected]>2021-02-04 21:17:58 +0900
committerKOBAYASHI Shuji <[email protected]>2021-02-04 21:17:58 +0900
commit67a28b56ab1bc8960a8302b2af273fcd8cd2a7bc (patch)
treeacf2d37f7b6fd2d173d9706da88770a893c691f9 /include/mruby.h
parent6f354322a8c77f07466aacd12d57674ead6726c9 (diff)
downloadmruby-67a28b56ab1bc8960a8302b2af273fcd8cd2a7bc.tar.gz
mruby-67a28b56ab1bc8960a8302b2af273fcd8cd2a7bc.zip
Check if `.pi` build rules are defined
`.pi` files are created for `.o` files that `build.products` depends on, but an error will occur if the build rule is unknown, so add a check. I don't think this situation would normally arise. However, in `mattn/mruby-onig-regexp`, when using bundled onigmo, onigmo's `.o` files are added to dependency of `libmruby.a` in the second and subsequent builds, and mruby does not know the build rule, so the following error had occured. ```console rake aborted! Don't know how to build task '/mruby/build/host/mrbgems/mruby-onig-regexp/onigmo-6.2.0/libonig_objs/ascii.pi' (See the list of available tasks with `rake --tasks`) ```
Diffstat (limited to 'include/mruby.h')
0 files changed, 0 insertions, 0 deletions