github/rebar
1
0
Fork 0
mirror of https://github.com/correl/rebar.git synced 2024-12-25 03:00:16 +00:00
Code Issues Projects Releases Packages Wiki Activity
Erlang build tool that makes it easy to compile and test Erlang applications, port drivers and releases.
1695 commits 5 branches 11 tags 2.8 MiB
Erlang 93.6%
Shell 5.3%
Batchfile 0.6%
C 0.3%
Makefile 0.2%
Find a file
David Kubecka 22acf8db67 Assemble Dirs passed to update_erlcinfo in one place 
Current separation of part of the logic into include_path
obscures the purpose of Dirs (see expand_file_names).
Moreover for each particular Erl its source file was included
twice in Dirs, which is now corrected.

Also InclDirs (specified in erl_opts) as part of erlcinfo
since they can affect resulting graph, which needs to be
therefore regenerated when InclDirs change.  See added
test as an example.
2015-04-05 00:46:34 +02:00
ebin Support .appup.src[.script] files 2015-02-04 22:33:16 +00:00
include Revert "Merge pull request #281 from tuncer/rebar-h-internal" 2014-06-23 13:48:49 -04:00
inttest Assemble Dirs passed to update_erlcinfo in one place 2015-04-05 00:46:34 +02:00
priv Add 'shell' sub-command to shell-completion 2015-02-13 09:05:33 +00:00
src Assemble Dirs passed to update_erlcinfo in one place 2015-04-05 00:46:34 +02:00
test add tests for 'compiler keep_going' 2015-04-02 16:55:48 +02:00
.gitignore Fix #267 (code path regression) 2014-04-23 22:17:23 +02:00
.travis.yml .travis.yml: print information before running script 2015-01-22 22:23:05 +01:00
bootstrap Fix OS X resource fork handling (Reported-by: Richard O'Keefe) 2014-07-25 20:52:30 +02: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 Fix minor typo in CONTRIBUTING.md 2014-09-06 16:11:08 +02:00
dialyzer_reference Adapt dialyzer_reference to ba466e2d changes 2014-11-02 14:00:15 +01:00
LICENSE Added HACKING, LICENSE and THANKS files 2009-12-31 20:31:22 +01:00
Makefile Allow running specific retest suites 2015-04-05 00:15:07 +02:00
README.md Update reference to installation notes 2014-12-03 12:37:05 +01:00
rebar.config Recompile .proto files with gpb also with prefix/suffix 2015-01-24 22:11:04 +01:00
rebar.config.sample Support custom protobuf directory 2015-01-31 19:47:59 +00:00
rebar.config.script Clean up rebar.config.script 2013-12-17 14:27:24 +01:00
RELEASE-NOTES.md Bump to 2.5.1 2014-07-30 17:37:49 +00:00
THANKS Add 'cover_export_json' option 2015-03-11 06:09:07 -04:00

README.md

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: