From bb5a4fffe21e0f6816ac0f8ef7fbc5c95b905ced Mon Sep 17 00:00:00 2001 From: Jakob Odersky Date: Tue, 12 May 2015 23:12:19 +0200 Subject: prepare release 2.1.2 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 18e64b8..795135d 100644 --- a/README.md +++ b/README.md @@ -7,13 +7,13 @@ The main reason for yet another serial communication library for the JVM is that ## Dependencies Flow is built and its examples run with SBT. To get started, include a dependency to flow in your project: - libraryDependencies += "com.github.jodersky" %% "flow" % "2.1.1" + libraryDependencies += "com.github.jodersky" %% "flow" % "2.1.2" *ATTENTION*: 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. 1. The easy way: add a second dependency to your project: - libraryDependencies += "com.github.jodersky" % "flow-native" % "2.1.1" + libraryDependencies += "com.github.jodersky" % "flow-native" % "2.1.2" This will add a jar to your classpath containing native libraries for various platforms. At run time, the correct library for the current platform is selected, extracted and loaded. This solution enables running applications seamlessly, as if they were pure JVM applications. However, since the JVM does not enable full determination of the current platform (only OS and rough architecture are known), only a couple of platforms can be supported through this solution at the same time. Currently, these are given in the table below. -- cgit v1.2.3