Continuous integration possible? Yes, but Linux only unless self-hosted

[cboulay]

A Slack user reported that the most recent 'release' didn't work for them.

build_mex completes, and making sure the liblsl-matlab/bin is in the path - still getting an "Error loading the liblsl library: Exiting now. Make sure liblsl-Matlab/bin is added to path and try running build_mex.m"

it seems the problem is in lsl_loadlib_ (the MEX-file) which throws "Error code: 126"

Temporary solution - downloaded an older version (1.13.0-b11) and extracted only the liblsl64.dll file, replaced it, and now it works...

This is an all-too-familiar problem when there's some minor difference that prevents liblsl from working with a new version of Matlab. Typically a recompilation of liblsl on that specific machine is required, but in this case one of the older release libraries happened to work.

liblsl-Matlab would really benefit from a continuous integration solution. Apparently Azure DevOps and CircleCI now have Matlab support!

• General information
• CircleCI
• Azure DevOps

Unfortunately, the cloud-hosted machines only support Matlab using Linux images. So that makes this pretty low priority because it's Windows where we encounter the most problems. Until then we will just provide releases on demand. And maybe I should update the instructions a little to make it clear that the user should try building liblsl themselves.