Erlang build tool that makes it easy to compile and test Erlang applications, port drivers and releases.
Find a file
alisdair sullivan 89cd24937e improve behaviour of rebar shell
attempt to emulate the behavior of
`erl -pa ebin -pa deps/*/ebin`

fix error messages and formatting issues of `rebar shell` by
shutting down and restarting the user subsystem in a mode more
hospitable to the shell than the simple user started when run
as an escript. emulate `error_logger` behaviour when the shell
is run via `erl`

add documentation of the shell command

limitations:

the erlang interrupt handler is not enabled when running as an
escript and there is no interface to re-enable it via erlang code.
this means `ctrl-c` will immediately exit the running process
unlike when running the shell via `erl`. `ctrl-g` is, however,
unaffected

the user subsystem is killed and restarted but not supervised. if
your code somehow relies on the user subsystem crashing and
restarting `rebar shell` may interfere with it's operation
2014-05-26 22:35:10 +00:00
ebin Merge pull request #255 from tuncer/superfluous-quoting 2014-05-19 09:11:24 -06:00
include Write ERROR messages to standard_error device 2013-12-06 19:05:45 +01:00
inttest Merge pull request #251 from mururu/eunit_compile_opts 2014-05-19 09:14:03 -06:00
priv Fix #56 (always-on recursion) 2014-03-11 21:11:36 +00:00
src improve behaviour of rebar shell 2014-05-26 22:35:10 +00:00
test file_utils: properly report errors (fix #95) 2014-04-11 15:01:26 +02: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 Roll rebar version 2.3.0 2014-05-13 09:01:26 -06:00
THANKS improve behaviour of rebar shell 2014-05-26 22:35:10 +00: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: