-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Asking for feedback on LabRecorder distribution #65
Comments
I now have LabRecorder building both the library-bundled version that gets deployed to the GitHub release page, as well as the slimmer version that gets deployed as a bottle. For now it's easy to have both, but I'd rather get rid of the former as it seems harder to maintain. If you already have homebrew installed, labrecorder installs very quickly with |
I managed to get LSL, LabRecorder and SigViewer working properly on a MacBook M1Pro running OSX 12.3.2 (Monterey)... but it took some effort ;-) What I did (on a brand new computer):
And I get the following (extract of the) crash dump (full version):
Maybe I should rebuild LabRecorder from source...
Still not working, with the same crash reason LabRecorder-2022-04-08-183420.txt |
That's great information. Thank you. |
Hi @DenisMot , just got a new MBP and I'm digging in. QtNetwork depends on This appears to be a known The short-term solution is to copy |
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?
The text was updated successfully, but these errors were encountered: