Tristan Stenner

Originally I thought it'd be difficult, because the target platform needs a working environment for Asio, but apparently [that's a thing](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/protocols/asio.html) nowadays.

I once wrote a [wireshark dissector](https://github.com/sccn/liblsl/blob/master/testing/lsl.lua) that splits some LSL packets. > So my question is what are the steps to create an outlet by using TCP, UDP, IGMP and...

> Do we have to send the reply on the port 16571? The discovery (`shortinfo`) request has the query in the first line, followed by `\r\n` and the response port...

I think I found the [source of the problem](https://github.com/sccn/liblsl/blob/089ebf60bfd747faef9d1a9cda8dced06c4be1f3/src/api_config.cpp#L118). By default, `127.0.0.1` is set as machine-local multicast address but it's a unicast address so only the last socket to bind...

1. Not that I know of, starting with TCP's lack of multicast support so you'd need some kind of discovery program that offers a list of local streams via e.g....

CC @chkothe as he knows most about it.

> That's not the way the examples work. At most, the code should throw an error to say, "don't do that". The inlet info should be gathered from a resolve...

> Option A: We could go back to using a single wheel for all platforms, and that wheel will contain liblsl compiled for every possible platform. This will require weird...

> Step 1: We need better testing on the build systems. I was only testing that the shared object could load and we could get the library version, but I...

And Docker on Appveyor produces a binary: https://ci.appveyor.com/api/buildjobs/7v79ltt6jq6vk29s/artifacts/build_manylinux%2Finstall%2Flib%2Fliblsl.so.1.13.0 Could you check if pypi accepts it?