Skip to content

Commit 5c6c155

Browse files
committed
Updated README to give more info on using examples.
1 parent 93845d1 commit 5c6c155

1 file changed

Lines changed: 12 additions & 5 deletions

File tree

README.md

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,19 @@
11
# C# bindings
22

33
The is the C# interface to the lab streaming layer. To use it, you need to include the file LSL.cs in
4-
your project, and make sure that the library liblsl32.dll is found (e.g., in your application's root
5-
directory or in a system path).
4+
your project, and make sure that the lsl library (e.g. liblsl32.dll) is found (e.g., in your application's
5+
root directory or in a system path).
6+
7+
If you are deploying for something other than Unity, and on a platform that requires a different binary
8+
than liblsl32.dll (e.g., liblsl64.so on 64-bit Linux, or liblsl64.dylib on Mac OS)
9+
then you need to replace the libname constant in LSL.cs by the corresponding file name.
10+
11+
These example applications can be debugged from within the IDE (i.e. Visual Studio). However, the built
12+
products are DLL files, not EXE files. The DLL files can be run at console with `dotnet my_application`
13+
(from within same folder as my_application.DLL). This will work anywhere the .NET Core Runtime works.
14+
To make a more portable but platform-dependent product, use `dotnet publish -C Debug -r win10-x64`
15+
(or Release instead of Debug) and this will generate an EXE file.
616

7-
If you are deploying on a platform that requires a different binary than liblsl32.dll (e.g., liblsl64.so
8-
on 64-bit Linux, or liblsl64.dylib on Mac OS, then you need to replace the libname constant in LSL.cs
9-
by the corresponding file name).
1017

1118
## C# Example Programs
1219

0 commit comments

Comments
 (0)