Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.

79 linhas
2.6 KiB

  1. rebar
  2. =====
  3. rebar is an Erlang build tool that makes it easy to compile and test Erlang
  4. applications, port drivers and releases.
  5. [![Build Status](https://secure.travis-ci.org/rebar/rebar.png?branch=master)](http://travis-ci.org/rebar/rebar)
  6. rebar is a self-contained Erlang script, so it's easy to distribute or even
  7. embed directly in a project. Where possible, rebar uses standard Erlang/OTP
  8. conventions for project structures, thus minimizing the amount of build
  9. configuration work. rebar also provides dependency management, enabling
  10. application writers to easily re-use common libraries from a variety of
  11. locations (git, hg, etc).
  12. Building
  13. --------
  14. Information on building and installing [Erlang/OTP](http://www.erlang.org) can
  15. be found [here](https://github.com/erlang/otp/wiki/Installation) ([more
  16. info](https://github.com/erlang/otp/blob/master/INSTALL.md)).
  17. ### Dependencies
  18. To build rebar you will need a working installation of Erlang R13B03 (or later).
  19. Should you want to clone the rebar repository, you will also require git.
  20. #### Downloading
  21. You can download a pre-built binary version of rebar from:
  22. https://github.com/rebar/rebar/wiki/rebar
  23. #### Building rebar
  24. ```sh
  25. $ git clone git://github.com/rebar/rebar.git
  26. $ cd rebar
  27. $ ./bootstrap
  28. Recompile: src/getopt
  29. ...
  30. Recompile: src/rebar_utils
  31. ==> rebar (compile)
  32. Congratulations! You now have a self-contained script called "rebar" in
  33. your current working directory. Place this script anywhere in your path
  34. and you can use rebar to build OTP-compliant apps.
  35. ```
  36. Contributing to rebar
  37. =====================
  38. Please refer to [CONTRIBUTING](CONTRIBUTING.md).
  39. Community and Resources
  40. -----------------------
  41. In case of problems that cannot be solved through documentation or examples, you
  42. may want to try to contact members of the community for help. The community is
  43. also where you want to go for questions about how to extend rebar, fill in bug
  44. reports, and so on.
  45. The main place to go for questions is the [rebar mailing
  46. list](http://lists.basho.com/pipermail/rebar_lists.basho.com/). If you need
  47. quick feedback, you can try the #rebar channel on
  48. [irc.freenode.net](http://freenode.net). Be sure to check the
  49. [wiki](https://github.com/rebar/rebar/wiki) first, just to be sure you're not
  50. asking about things with well known answers.
  51. For bug reports, roadmaps, and issues, visit the [github issues
  52. page](https://github.com/rebar/rebar/issues).
  53. General rebar community resources and links:
  54. - [Rebar Mailing List](http://lists.basho.com/pipermail/rebar_lists.basho.com/)
  55. - #rebar on [irc.freenode.net](http://freenode.net/)
  56. - [wiki](https://github.com/rebar/rebar/wiki)
  57. - [issues](https://github.com/rebar/rebar/issues)