| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent builds of LFE have stopped reporting compile errors when compiled with
rebar. Examination of this issue revealed that this was due to recent
changes in default LFE compile options.
The way that LFE handles compile options has slightly changed; ``verbose`` and
``report`` are now provided as defaults only if no other options are passed; if
other options are passed, these do not get set. As a result, we have stopped
seeing compile error info when building with rebar.
This change brings back the previous level of reporting that LFE developers had
when compiling their projects with rebar.
|
|\
| |
| | |
Add erl_first_files in eunit_first_files and qc_first_files
|
| | |
|
|\ \
| | |
| | | |
Fix #536
|
| |/ |
|
| | |
|
|/
|
|
|
|
| |
Move existing documentation from code comment into help string, so that
'rebar help compile' prints complete documentation for
rebar_port_compiler.
|
|
|
|
|
|
| |
Use case: xref'ing a module that defined behavior ranch_protocol was
exiting with
{'EXIT',{undef,[{ranch_protocol,behaviour_info, [callbacks],[]}
|
|
|
|
|
|
|
|
|
|
|
| |
* do not use pdict
* do not enable color support by default. once we have the new
getopt version, we can add a new type of command line flag
for that.
* fix Dialyzer warnings
* use atom instead of boolean
* use better name for internal function
* do not try (and fail) to access rebar's app env in retest test
|
|
|
|
|
|
| |
Fix verbose level in global rebar config
Replace application:set_env on erlang:put
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* fix commit messages
* fix whitespace issues
* move internal helper functions to correct location
* unexport internal cross arch helper functions
* fix 18.0 time API compatibility
* fix Windows temp dir detection
* use correct helper function name
* use sh/2 instead of os:cmd/1
* match file:delete/1 result
* use logging macros
* fix typo
* fix Dialyzer warnings
* add Tony Rogvall to THANKS
* add missing termination clause
* os type must be win32, not windows
* match file:write_file/2 result
* document cross-arch variables
* simplify env_wordsize/1 (Thanks Fred Hebert)
|
|
|
|
|
|
|
|
|
|
| |
New variable names:
* REBAR_TARGET_ARCH
* REBAR_TARGET_ARCH_VSN
* REBAR_TARGET_ARCH_WORDSIZE
|
| |
|
|
|
|
|
|
|
|
|
|
| |
New vars for cross arch support:
* REBAR_ARCH_TARGET
* REBAR_TARGET_WORDSIZE
* REBAR_ARCH_TARGET_VSN
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
ets read_concurrency has been available since R14, but rebar supports
R13B03 (and newer). As a workaround we check that erts/ebin/erts.app
exists as another pre-R14 characteristic to determine whether we can
assume read_concurrency is supported.
|
|
|
|
|
|
|
| |
1. memoize otp release vsn string function call
2. memoize expensive filename:absname/1 call which happens
to be called quite frequently
|
|
|
|
|
| |
Copy memo.erl from https://github.com/tuncer/memo and rename to
rmemo.erl for use in rebar. We rename it to avoid collisions.
|
| |
|
| |
|
|\
| |
| | |
Drop `shared` PLTs support and change PLT name to <OTP-VSN>.plt
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
Add Dialyzer plugin
|
| |
| |
| |
| | |
To match rebar3, change plt_location's default to 'local'.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
{dialyzer,
[
%% Store PLT in ~/.rebar/plt (Default)
{plt_location, shared},
%% Store PLT locally inside the project in .rebar
{plt_location, local},
%% Store PLT in custom directory
{plt_location, "custom_dir"},
%% Extra apps to include in the PLT
{plt_extra_apps, [app1, app2]},
{warnings, [unmatched_returns, error_handling]}
]}.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Build project-specific PLT
$ rebar build-plt
Check the PLT for consistency and rebuild it if it is not up-to-date
$ rebar check-plt
Analyze the code for discrepancies
$ rebar dialyze
Delete project-specific PLT
$ rebar delete-plt
Valid rebar.config options:
%% Store PLT in ~/.rebar/plt (Default)
{dialyzer_plt_location,shared}
%% Store PLT locally inside the project in .rebar
{dialyzer_plt_location,local}
%% Store PLT in custom directory
{dialyzer_plt_location,"custom_path"}
{dialyzer_plt_extra_apps,[app1,app2]}
{dialyzer_warnings,[unmatched_returns,error_handling]}
|
| |
| |
| |
| |
| | |
If one is building Erlang from sources without making a proper release,
there may be an OTP_VERSION file in the root directory.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
into RubberCthulhu-ct-groups-and-cases
Conflicts:
THANKS
|
| |
| |
| |
| |
| |
| |
| | |
Add option 'groups' to 'rebar ct' command. So the command "rebar ct suites=Suite1 groups=Group1,Group2,...,GroupN" is equal to "ct_run -suite Suite1_SUITE -group Group1 Group2 ... GroupN". It allows to run specified test groups in specified test suite with Common Test tool. Besides it is absolutely necessary to specify groups for running test cases which are included in these groups, otherwise init_per_group/2 and end_per_group/1 callbacks are not called by ct_run.
Add option 'cases' to 'rebar ct' command. So the command "rebar ct suites=Suite1 cases=Case1,Case2,...,CaseN" is equal to "ct_run -suite Suite1_SUITE -case Case1 Case2 ... CaseN". It allows to run one or more test cases in specified test suite. Currently rebar has an option 'case' which allows to run only one test case. The option case is remained for backward compability. It's suggested to consider the option 'case' as deprecaed and recommended to use 'cases' instead.
Updated help messages according to new command line options.
Add warning message when used deprecated options 'case', 'group', 'suite' in command "rebar ct".
|
|\ \
| | |
| | | |
Use target_dir as source of new version in generate-appups
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
fholzhauser-dia_first_files
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With the implementation of dia_first_files option some lines exceeded
79 columns (thanks to Tuncer Ayaz for pointing this out). These are
corrected with this change.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
With this option is is possible to provide a list of files to compile
first. It is necessary when diameter dictionaries have dependencies.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/paulo-ferraz-oliveira/rebar into paulo-ferraz-oliveira-fix/xref_behavior
|
| | | | |
| | | | |
| | | | |
| | | | | |
American alternative to -behaviour()
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
https://github.com/lrascao/rebar into lrascao-feature/add_gpb_proto_error_test_case
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
On a failed build, print an absolute source filename,
if applicable
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
avoid pre-compile time errors in expand_include_lib_path
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously when user specified broken include_lib, such as
-include_lib("my_app.hrl"), the code throwed too early
exception. We fix this simply by avoiding any possible
internal errors, possibly letting even nonsensical paths pass.
These will be checked and filtered later in expand_file_names/2.
|
|/ / / / / |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently this option doesn't work very well because
given parse_transform is applied globally to all modules,
even to parse transform module itself which is not possible
because the module is not yet compiled.
So we just ensure that local parse transformations are not applied
to themselves and probably also to erl_first_files since they
are explicitly stated as to be compiled before anything else.
|