Open kittydoor opened 4 years ago
OK, I need to do further testing, as it might be that that the version of Xcode now available doesn't quite work with Barrier anymore. Not totally sure yet.
In the meantime, here's a link to an archive built by our CI for macOS. You will need to extract it, and install the Barrier-2.3.2-Release.dmg
package within. This is built straight from master
, so give that a go in the interim.
Thanks.
I haven't tested on this macOS version, but I somehow suspend that command line tools have not been installed. @kittydoor could you try to launch Xcode itself? It should prompt to install any additional packages needed for full functionality.
Looks like an issue with the toolchain, the pthread header should be installed with Xcode in the MacOSX sdk:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/pthread/pthread.h
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/pthread.h
@p12tic
$ xcode-select --install
xcode-select: error: command line tools are already installed, use "Software Update" to install updates
@simons-public
From my understanding, everything looks good? I'm not sure why Cmake is not liking it. Maybe some environment variables are being overridden by me that is causing the issue?
Testing this theory with bash (which I have not made any modifications to the rc of, just updated via brew, the error is the same.
Hm, interesting. I did come across a Stackoverflow page about cmake not finding pthread.h
on Mojave..
@kittydoor Can you try building without the clean_build.sh
script?
mkdir tempbuild
cd tempbuild
cmake -DCMAKE_BUILD_TYPE=Release ..
make
CMake builds just fine on my machine without a lot of the variables set in clean_build.sh
and osx_environment.sh
(as long as the prerequisites are installed). I am using macports though, so I can't say for sure that it will work that way with homebrew.
If it works fine that might indicate an issue in the script, if it fails at least we can rule it out a problem with those scripts and go from there.
Also, what version of Xcode do you have installed?
@simons-public
Xcode Version 11.5 (11E608c) xcode-select version 2373.
We appear to have made progress, which means the script does seem to be at least partially guilty. However, I'm unsure why Cmake is now having issues with finding Qt5 libs.
This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.
Let's not close valid bugs without a valid reason.
I had to change my xcode path in clean_build.sh from:
B_CMAKE_FLAGS="-DCMAKE_OSX_SYSROOT=$(xcode-select --print-path)/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -DCMAKE_OSX_DEPLOYMENT_TARGET=10.9 $B_CMAKE_FLAGS"
to
B_CMAKE_FLAGS="-DCMAKE_OSX_SYSROOT=$(xcode-select --print-path)/SDKs/MacOSX.sdk -DCMAKE_OSX_DEPLOYMENT_TARGET=10.9 $B_CMAKE_FLAGS"
I had to change my xcode path in clean_build.sh from:
B_CMAKE_FLAGS="-DCMAKE_OSX_SYSROOT=$(xcode-select --print-path)/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -DCMAKE_OSX_DEPLOYMENT_TARGET=10.9 $B_CMAKE_FLAGS"
to
B_CMAKE_FLAGS="-DCMAKE_OSX_SYSROOT=$(xcode-select --print-path)/SDKs/MacOSX.sdk -DCMAKE_OSX_DEPLOYMENT_TARGET=10.9 $B_CMAKE_FLAGS"
I found the same was true on macOS Big Sur 11.4.
In case it's relevant, I was using cmake 3.21.1 from homebrew.
Operating Systems
Server: Linux
Client: macOS Catalina 10.15.5
Barrier Version
master
Steps to reproduce bug
Other info
Latest commit at time of issue: 2393393b8897df2e18ff8a4a1754161084da2b5e