diff options
| author | Jakob Odersky <jodersky@gmail.com> | 2015-01-11 12:19:27 +0100 |
|---|---|---|
| committer | Jakob Odersky <jodersky@gmail.com> | 2015-01-11 12:19:27 +0100 |
| commit | 3d85ab603c7bcf76b8bd14587b957bce21b8586f (patch) | |
| tree | 321b1248d0fb786bf2bf06236244a5f1f3595447 | |
| parent | 78e3ef3797290afa68cc17dcc927717c3f541d20 (diff) | |
| download | akka-serial-3d85ab603c7bcf76b8bd14587b957bce21b8586f.tar.gz akka-serial-3d85ab603c7bcf76b8bd14587b957bce21b8586f.tar.bz2 akka-serial-3d85ab603c7bcf76b8bd14587b957bce21b8586f.zip | |
fix typo
| -rw-r--r-- | documentation/building.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/documentation/building.md b/documentation/building.md index bd3eff0..3d806f6 100644 --- a/documentation/building.md +++ b/documentation/building.md @@ -24,4 +24,5 @@ A second versioning quirk to be aware of is when building native sources. In thi - `M` is the major version, representing backwards incompatible changes - `m` is the minor version, indicating backwards compatible changes such as new feature additions - `p` is the patch number, representing internal modifications such as bug-fixes + Usually (following most linux distribution's conventions), shared libraries produced by a project `name` of version `M.m.p` are named `libname.M.m.p`. However, since when accessing shared libraries through the JVM, only the `name` can be specified and no particular version, the convention adopted by flow is to append `M` to the library name and always keep the major version at zero. E.g. `libflow.3.1.2` becomes `libflow3.0.1.2`. |