Erlang build tool that makes it easy to compile and test Erlang applications, port drivers and releases.
Find a file
Tuncer Ayaz 77a0eb6fe4 Fix #56 (always-on recursion)
Always-on recursive application of all rebar commands causes too many
issues. Recursive application is required for:
1. dealing with dependencies: get-deps, update-deps, and compile of deps
   right after get-deps or update-deps
2. projects with a riak-like apps/ project structure and dev process

The vast majority of projects are not structured like riak. Therefore,
moving forward it's best to (by default) restrict recursive behavior to
dealing with deps. This commit does that and also adds command line and
rebar.config options for controlling or configuring recursion. Also, we
introduce two meta commands: prepare-deps (equivalent to rebar -r
get-deps compile) and refresh-deps (equivalent to rebar -r update-deps
compile). riak-like projects can extend the list of recursive commands
(to include 'eunit' and 'compile') by adding
{recursive_cmds, [eunit, compile]} to rebar.config.
2014-03-11 21:11:36 +00:00
ebin Fix #56 (always-on recursion) 2014-03-11 21:11:36 +00:00
include Write ERROR messages to standard_error device 2013-12-06 19:05:45 +01:00
inttest Fix #56 (always-on recursion) 2014-03-11 21:11:36 +00:00
priv Fix #56 (always-on recursion) 2014-03-11 21:11:36 +00:00
src Fix #56 (always-on recursion) 2014-03-11 21:11:36 +00:00
test Merge branch 'xref_20130130' of git://github.com/spilgames/rebar into spg-xref 2013-06-17 16:31:09 -06:00
.gitignore erlc: clean-up, enhance, and regression fix fd17693 2014-03-05 15:44:38 +01: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: