Now that liblsl is available via homebrew (brew install labstreaminglayer/tap/lsl), I'm about to make LabRecorder and other LSL Apps available via homebrew as well.
There are some obvious wins here, but the biggest is that it'll be a very easy way for users to "build from source", so users who don't have whatever version of MacOS was used by me or the CI runner will still have an easy way to get the app, as long as their system is compatible with the dependencies (Qt6).
There are some implementation details that are attractive but have some consequences, so I'm asking for feedback.
Can I change it so that LabRecorder links to the homebrew-installed dependencies instead of dependencies packaged inside the app folder?
One of the most annoying parts about using cmake to build cross-platform qt-based apps is packaging the dependencies for the MacOS app. It doesn't work properly all the time, it's different on different computers, and it seems to break with every update.
If I can instead link to the homebrew-provided libraries, it becomes much simpler and we can ditch about 50 lines of CMake code.
The main disadvantage is that we will no longer have a all-in-one file that a user can download on one computer and bring to a different computer. Even if they download the bottle, they will still need the bottles for the dependencies, and I don't know how to do that for Qt. So this means users on not-internet-connected computers are left behind, or they have to download an offline installer for qt and do a manual build.
Thoughts?
Now that liblsl is available via homebrew (
brew install labstreaminglayer/tap/lsl), I'm about to make LabRecorder and other LSL Apps available via homebrew as well.There are some obvious wins here, but the biggest is that it'll be a very easy way for users to "build from source", so users who don't have whatever version of MacOS was used by me or the CI runner will still have an easy way to get the app, as long as their system is compatible with the dependencies (Qt6).
There are some implementation details that are attractive but have some consequences, so I'm asking for feedback.
Can I change it so that LabRecorder links to the homebrew-installed dependencies instead of dependencies packaged inside the app folder?
One of the most annoying parts about using cmake to build cross-platform qt-based apps is packaging the dependencies for the MacOS app. It doesn't work properly all the time, it's different on different computers, and it seems to break with every update.
If I can instead link to the homebrew-provided libraries, it becomes much simpler and we can ditch about 50 lines of CMake code.
The main disadvantage is that we will no longer have a all-in-one file that a user can download on one computer and bring to a different computer. Even if they download the bottle, they will still need the bottles for the dependencies, and I don't know how to do that for Qt. So this means users on not-internet-connected computers are left behind, or they have to download an offline installer for qt and do a manual build.
Thoughts?