Erlang build tool that makes it easy to compile and test Erlang applications, port drivers and releases.
Find a file
Tuncer Ayaz 99fe270e59 Fix #267 (code path regression)
Since the introduction of -r/--recursive, deps were not properly added
to the code path when running ct, eunit, etc.

To fix that, pass a flag down to process_dir1 and conditionalize
execution of the command. This moves the decision into process_dir1
where we can decide to invoke preprocess/2 and postprocess/2 but not
execute the command.

Without this fix, you'd have to, for example, invoke 'rebar -r ct
skip_deps=true', if you wanted to run base_dir's ct suites with deps on
the code path (while skipping all non-base_dir ct suites).

So, with this patch applied, if you run
$ rebar ct
deps will be on the code path, and only base_dir's ct suites will be
tested.

If you want to test ct suites in base_dir and sub_dirs, you have to run
$ rebar -r ct skip_deps=true

If you want to test ct suites in all dirs, you have to run
$ rebar -r ct

The fix is not specific to ct and applies to all commands.

To be able to add inttest/code_path_no_recurse/deps, I had to fix
.gitignore. While at it, I've updated and fixed all entries.
2014-04-23 22:17:23 +02:00
ebin Keep compile recursive and update the tests to not pass -r to compile 2014-03-11 21:24:19 +00:00
include Write ERROR messages to standard_error device 2013-12-06 19:05:45 +01:00
inttest Fix #267 (code path regression) 2014-04-23 22:17:23 +02:00
priv Fix #56 (always-on recursion) 2014-03-11 21:11:36 +00:00
src Fix #267 (code path regression) 2014-04-23 22:17:23 +02:00
test Add partial support for Erlang/OTP 17 2014-03-29 23:22:47 -05:00
.gitignore Fix #267 (code path regression) 2014-04-23 22:17:23 +02:00
.travis.yml Added R16B01 and R16B02 to travis config. 2014-01-26 20:58:20 +01:00
bootstrap bootstrap: avoid trying to run 'debug' command 2013-12-17 14:28:58 +01:00
bootstrap.bat add bat scripts for bootstrap and rebat (windows doesn't understand shebang), make bootstrap work on windows 2010-08-02 20:35:26 +03:00
CONTRIBUTING.md CONTRIBUTING: apply stylistic change suggested by dizzyd 2013-09-20 22:42:00 +02:00
dialyzer_reference erlc: clean-up, enhance, and regression fix fd17693 2014-03-05 15:44:38 +01:00
LICENSE Added HACKING, LICENSE and THANKS files 2009-12-31 20:31:22 +01:00
Makefile erlc: clean-up, enhance, and regression fix fd17693 2014-03-05 15:44:38 +01:00
NOTES.org Initial commit 2009-11-25 15:23:42 -07:00
README.md Extract contributing guide into CONTRIBUTING.md 2013-09-20 20:54:23 +02:00
rebar.config rebar.config: delete unused and unimplemented 'app_bin' option 2012-11-19 00:16:34 +01:00
rebar.config.sample Fix #56 (always-on recursion) 2014-03-11 21:11:36 +00:00
rebar.config.script Clean up rebar.config.script 2013-12-17 14:27:24 +01:00
RELEASE-NOTES.md Bump rebar to 2.2.0 and add proper release notes 2014-02-05 15:01:51 -07:00
THANKS erlc: clean-up, enhance, and regression fix fd17693 2014-03-05 15:44:38 +01:00

rebar

rebar is an Erlang build tool that makes it easy to compile and test Erlang applications, port drivers and releases.

Build Status

rebar is a self-contained Erlang script, so it's easy to distribute or even embed directly in a project. Where possible, rebar uses standard Erlang/OTP conventions for project structures, thus minimizing the amount of build configuration work. rebar also provides dependency management, enabling application writers to easily re-use common libraries from a variety of locations (git, hg, etc).

Building

Information on building and installing Erlang/OTP can be found here (more info).

Dependencies

To build rebar you will need a working installation of Erlang R13B03 (or later).

Should you want to clone the rebar repository, you will also require git.

Downloading

You can download a pre-built binary version of rebar from:

https://github.com/rebar/rebar/wiki/rebar

Building rebar

$ git clone git://github.com/rebar/rebar.git
$ cd rebar
$ ./bootstrap
Recompile: src/getopt
...
Recompile: src/rebar_utils
==> rebar (compile)
Congratulations! You now have a self-contained script called "rebar" in
your current working directory. Place this script anywhere in your path
and you can use rebar to build OTP-compliant apps.

Contributing to rebar

Please refer to CONTRIBUTING.

Community and Resources

In case of problems that cannot be solved through documentation or examples, you may want to try to contact members of the community for help. The community is also where you want to go for questions about how to extend rebar, fill in bug reports, and so on.

The main place to go for questions is the rebar mailing list. If you need quick feedback, you can try the #rebar channel on irc.freenode.net. Be sure to check the wiki first, just to be sure you're not asking about things with well known answers.

For bug reports, roadmaps, and issues, visit the github issues page.

General rebar community resources and links: