Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make rebar3 work with dialyzer internally
We got funny interactions since PR erlang#1656: - the last `debug_info`-related option seen in a list of options after profile merge is kept, allowing later profiles from overtaking earlier ones - if you go `rebar3 as a,b,c compile`, the options from profile A come before B, which come before C, so C's options win - overrides are applied in order of profile as well, giving a priority to a later profile than an earlier one - The values in overrides are prepended rather than suffixed to the existing list - this means if we have to overrides adding options, such as `default` adding `no_debug_info', and `dialyze` adding `debug_info`, the results are `[debug_info]` as `dialyze` is applied first, and then `[no_debug_info, debug_info]` as `default` overrides are applied - the final result is `no_debug_info` always winning when erl_opts are overriden specifically. only `debug_info` options are going to suffer this, and in the context of overrides. Other `erl_opts` should be fine. I'm not sure how that can be fixed at all. In the meanwhile, we can add support back while leaving the default to not having debug information. This is done by: - moving all `no_debug_info` options to the `prod` profile - forcing `prod` to be called by `./bootstrap` so that most people keep getting no debug info - anyone calling `rebar3 clean -a` and then rebuilding with `rebar3 escriptize` (i.e. rebar3 devs) get debug info going This is up for review and discussion.
- Loading branch information