You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Homebrew for Casks and MacPorts for command line tools.
I have all my dependencies in /opt/local/ for MacPorts.
When I first tried to build, it seems like the build script prefers Homebrew, even if it detects MacPorts.
After removing Homebrew from my $PATH, I was able to build successfully.
[ 82%] Built target barriers
Checking for bundle contents
Copying binaries into bundle
MacPorts found, searching for macdeployqt
Disk image (dmg) only created for Release builds
Building debug bundle
Bundle created successfully
[ 82%] Built target Barrier_MacOS
I readded Homebrew to my $PATH and confirmed that it is the case that it doesn't build.
[ 82%] Built target barriers
Checking for bundle contents
Copying binaries into bundle
MacPorts found, searching for macdeployqt
Homebrew found, searching for macdeployqt
Error: No such keg: /opt/homebrew/Cellar/qt@5
Please install package qt
make[2]: *** [CMakeFiles/Barrier_MacOS] Error 1
make[1]: *** [CMakeFiles/Barrier_MacOS.dir/all] Error 2
make: *** [all] Error 2
What happened?
I use Homebrew for Casks and MacPorts for command line tools.
I have all my dependencies in
/opt/local/
for MacPorts.When I first tried to build, it seems like the build script prefers Homebrew, even if it detects MacPorts.
After removing Homebrew from my
$PATH
, I was able to build successfully.I readded Homebrew to my
$PATH
and confirmed that it is the case that it doesn't build.Version
From Git HEAD or commit (specify below)
Git commit hash (if applicable)
433126e
If applicable, where did you install Barrier from?
No response
What OSes are you seeing the problem on? (Check all that apply)
macOS
What OS versions are you using?
macOS 12.1, Darwin 21.2.0, ARM64, on a Macbook Air M1
Relevant log output
No response
Any other information
No response
The text was updated successfully, but these errors were encountered: