| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-11-23 | Use local variables instead of top level constants in `boxing.rb` [ci skip] | KOBAYASHI Shuji | |
| 2020-11-21 | Fix incorrect build name and simplify `build_config/boxing.rb` [ci skip] | KOBAYASHI Shuji | |
| `boxing-nan-m64` was duplicated. | |||
| 2020-11-21 | Test each combination of boxing, `mrb_int` size, and archtecture. | Yukihiro "Matz" Matsumoto | |
| Boxing: * `MRB_NO_BOXING` (`mrb_value` packed in `struct`) * `MRB_WORD_BOXING` (`mrb_value` packed in `struct`) default * `MRB_NAN_BOXING` (`mrb_value` packed in `double`) `mrb_int` size * `MRB_INT32` (`int32_t` as `mrb_int`) * `MRB_INT64` (`int64` as `mrb_int`) conflict with `MRB_NAN_BOXING' Architecture * `MRB_64BIT` (`sizeof(void*)` is 64 bits) * `MRB_32BIT` (`sizeof(void*)` is 32 bits) | |||
| 2020-11-19 | Allow `bintest` even if build name is not `host` | KOBAYASHI Shuji | |
| 2020-10-19 | Revert `MRUBY_TARGET` mechanism; ref #5096 | KOBAYASHI Shuji | |
| * In explanation of mruby, the expression `build_config.rb` is frequently used including official documents, so I think that it will not make sense if the file is no longer used. * The `MRUBY_TARGET` mechanism seems to have little improvement, so I don't think it should be changed to avoid unnecessary confusion. * `MRUBY_TARGET` and `MRuby.targets` represent somewhat different things, so using the same term "target" is a bit confusing. The mechanism that can be written short when using a file under `build_config` (renamed from `target`) directory remains (`build_config/${MRUBY_CONFIG}.rb` is used if the path specified in `MRUBY_CONFIG` doesn't exist). | |||
