From 408c9f7b66d3406a5277dda68a2edb23f64c2493 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niccol=C3=B2=20Bonacchi?= Date: Thu, 16 Apr 2020 10:47:56 +0100 Subject: [PATCH] Fixed README.md links from old liboepcie to liboni --- api/README.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/api/README.md b/api/README.md index 5a21eef..a184c9b 100644 --- a/api/README.md +++ b/api/README.md @@ -3,17 +3,13 @@ The host-side APIs allow high-performance software interfaces and the creation of high level language bindings. API implementations are compliant with the [Open Neuro Interface specification](https://github.com/jonnew/ONI). -- [`liboepcie`](liboepcie) is an ANSI-C implementation of the [Open Ephys++ API - Specificaiton](../spec/README.md). It contains functions for configuring and +- [`liboni`](liboni) is an ANSI-C implementation of the [Open Ephys++ API + Specificaiton](liboni#api-spec). It contains functions for configuring and streaming data to and from hardware. -- [`cppoepcie`](cppoepcie) C++14 bindings for `liboepcie`. -- [`clroepcie`](clroepcie) CLR/.NET bindings for `liboepcie`. +- [`cpponi`](cpponi) C++14 bindings for `liboni`. +- [`clroni`](clroni) CLR/.NET bindings for `liboni`. Minimal example host programs for each of these libraries can be found in the \*-test folder within each library directory. If you are interested in writing a binding or integrating and existing API with your software, please get in touch. - -## Using Xillybus with `liboepcie` -Instructions for using [Xillybus](http://xillybus.com/) as a communication -backend can be found [here](xillybus-backend.md).