Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Erlang/OTP
Erlang C C++ Java Emacs Lisp XSLT Other

This branch is 7041 commits behind erlang:master

Failed to load latest commit information.
HOWTO Update copyright years
bin
bootstrap Update primary bootstrap
erts Merge branch 'sverk/nif-cut-timeslice'
lib Update deprecation message for gs
make Update copyright years
plt
system Update copyright years
xcomp Update for new version of ppc compilation chain
.gitattributes Stop including in .gitignore files in the source tar files
.gitignore Merge branch 'nox/enable-silent-rules/OTP-10726'
.mailmap Add .mailmap file
AUTHORS The R13B03 release.
EPLICENCE The R13B03 release.
Makefile.in Implement ./otp_build configure --enable-silent-rules
README.md Merge branch 'maint'
TAR.include Move README and INSTALL to HOWTO folder
aclocal.m4 Update copyright years
configure.in Implement ./otp_build configure --enable-silent-rules
erl-build-tool-vars.sh OTP-8323 Cross compilation improvements and other build system
otp_build If GCC is used, treat -Wreturn-type as error
prebuild.delete Regenerate bootstrap/{erl,erlc} when switching target
prebuild.skip OTP-8323 Cross compilation improvements and other build system

README.md

Erlang/OTP

Erlang is a programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of its uses are in telecom, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.

OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.

More information can be found at erlang.org.

Building and Installing

Information on building and installing Erlang/OTP can be found in the $ERL_TOP/HOWTO/INSTALL.md document.

Contributing to Erlang/OTP

Here are the instructions for submitting patches.

In short:

  • We prefer to receive proposed updates via email on the erlang-patches mailing list rather than through a pull request. Pull requests are not practical because we have a strict policy never to merge any untested changes to the development branch (the only exception being obviously correct changes, such as corrections of typos).

  • We merge all proposed updates to the pu (proposed updates) branch, typically within one working day.

  • At least once a day, the contents of the pu branch will be built on several platforms (Linux, Solaris, Mac OS X, Windows, and so on) and automatic test suites will be run. We will email you if any problems are found.

  • If a proposed change builds and passes the tests, it will be reviewed by one or more members of the Erlang/OTP team at Ericsson. The reviewer may suggest improvements that are needed before the change can be accepted and merged.

  • Once or twice a week, a status email called "What's cooking in Erlang/OTP" will be sent to the erlang-patches mailing list.

Copyright and License

%CopyrightBegin%

Copyright Ericsson AB 2010-2012. All Rights Reserved.

The contents of this file are subject to the Erlang Public License, Version 1.1, (the "License"); you may not use this file except in compliance with the License. You should have received a copy of the Erlang Public License along with this software. If not, it can be retrieved online at http://www.erlang.org/.

Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.

%CopyrightEnd%

Something went wrong with that request. Please try again.