diff options
| author | Jakob Odersky <jodersky@gmail.com> | 2014-01-18 22:26:37 +0100 |
|---|---|---|
| committer | Jakob Odersky <jodersky@gmail.com> | 2014-01-18 22:26:37 +0100 |
| commit | fd2a6b1e15cdc936b9e4f281119f0a37cac54a2e (patch) | |
| tree | edd263f805ba3a984525661a39f5a2aa6e90d9a2 | |
| parent | 02eea01e1dddc01518a610166644d3d9c80812aa (diff) | |
| download | akka-serial-fd2a6b1e15cdc936b9e4f281119f0a37cac54a2e.tar.gz akka-serial-fd2a6b1e15cdc936b9e4f281119f0a37cac54a2e.tar.bz2 akka-serial-fd2a6b1e15cdc936b9e4f281119f0a37cac54a2e.zip | |
update arm specification
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -19,10 +19,10 @@ ATTENTION: flow uses native libraries to back serial communication, therefore be 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 are supported through this solution. Currently, these are given in the table below. - | OS (tested on) | Architecture | Notes | + | OS | Architecture | Notes | |-------------------|----------------------|------------------------------------------------------------------------| - | Linux (3.2.0) | x86<br>x86_64<br>ARM | ARM specification: v7, hard float ABI (may work on other versions too, any feedback is welcome!)<br>A user accessing a serial port may need to be in the dialout group| - | Mac OS X (10.6.8) | x86_64 | Use /dev/cu* device instead of /dev/tty*. | + | Linux | x86<br>x86_64<br>ARM (v7, hardfloat, glibc 2.13) | A user accessing a serial port may need to be in the dialout group <br> ARM may work on other versions too, any feedback is welcome!<br>| + | Mac OS X | x86_64 | Use /dev/cu* device instead of /dev/tty*. | 2. Maximum scalability: do not include the second dependency above. Instead, for every end-user application that relies on flow, manually add the native library for the current platform to the JVM's library path. This can be achieved through various ways, notably: |