diff options
| author | Jakob Odersky <jodersky@gmail.com> | 2015-09-04 12:11:19 +0200 |
|---|---|---|
| committer | Jakob Odersky <jodersky@gmail.com> | 2015-09-04 12:11:19 +0200 |
| commit | 986728875c47414a34ee240ebaf95772f286f76b (patch) | |
| tree | c49825735f4875893961e51a38069c084605b11c /README.md | |
| parent | ce410f1d21a3c908fbb53ced65d187dfce842225 (diff) | |
| download | akka-serial-986728875c47414a34ee240ebaf95772f286f76b.tar.gz akka-serial-986728875c47414a34ee240ebaf95772f286f76b.tar.bz2 akka-serial-986728875c47414a34ee240ebaf95772f286f76b.zip | |
upgrade to akka 2.3.13; release
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -13,7 +13,7 @@ Serial communication library for Scala, designed to be reactive, lightweight and ## Getting Started Flow uses sbt as build system. To get started, include a dependency to flow in your project: - libraryDependencies += "com.github.jodersky" %% "flow" % "2.2.1" + libraryDependencies += "com.github.jodersky" %% "flow" % "2.2.2" ### Including Native Library *NOTICE: flow uses native libraries to back serial communication, therefore before you can run any application depending on flow you must include flow's native library! To do so, you have two options.* @@ -21,7 +21,7 @@ Flow uses sbt as build system. To get started, include a dependency to flow in y #### The easy way In case your OS/architecture combination is present in the below table, add a second dependency to your project: - libraryDependencies += "com.github.jodersky" % "flow-native" % "2.2.1" + libraryDependencies += "com.github.jodersky" % "flow-native" % "2.2.2" | OS | Architecture | Notes | |-------------------|-----------------------------|---------------------------------------------------------------------------------| @@ -106,7 +106,7 @@ object Terminal { More examples on flow's usage are located in the flow-samples directory. The examples may be run with sbt: `samples-<sample_name>/run`. -Since flow integrates into the Akka-IO framework, a good resource on its general design is the framework's [documentation](http://doc.akka.io/docs/akka/2.3.12/scala/io.html). +Since flow integrates into the Akka-IO framework, a good resource on its general design is the framework's [documentation](http://doc.akka.io/docs/akka/2.3.13/scala/io.html). ## Native side Since hardware is involved in serial communication, a Scala-only solution is not possible. Nevertherless, the native code is kept simple and minimalistic with the burden of dealing with threads left to Scala. The code aims to be POSIX compliant and therefore easily portable. |