mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #448] Fix dependencies #358
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#358
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JonasGessner on GitHub (May 27, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/448
Describe the bug
I tried cloning the project and building it myself and I ran into several issues all boiling down to the fact that the Cartfile has no versions/commit hashes set:
~> 3.4.masterin the Cartfile. This is an issue because after I fixed the AVMCoreAudio problem I noticed that the app I compiled myself doesn't work properly – most of the time nothing changes on my display. Only after spamming volume/brightness keys anything starts to change. The latest version installed through homebrew does not have this problem. This could be a regression inDDC, but since there is no commit information/tag version for DDC in the Cartfile I do not know which commit you linked against!Environment Information (please complete the following information):
@JoniVR commented on GitHub (May 27, 2021):
Hi, all of this is being worked on in the refactor/Preferences branch.
I just need to fix some of the storyboard stuff and it'll be ready for a merge.
Changes so far:
The switch to SPM also resolved command reliability, I have no idea why but I suspect it has something to do with Carthage.
So I suggest you work off that branch if you want to make changes, though I will probably squash merge it, it shouldn't be an issue.
@JonasGessner commented on GitHub (May 27, 2021):
That's great, thanks for the quick reply!