Open lilyball opened 7 years ago
You need to set QTDIR64
(or QTDIR
if you're on 32 bit) to the install prefix of Qt. So QTDIR64=`brew --prefix qt5` cargo build
should do the trick. Sorry, I forgot to document this.
I looked at the build.rs script and it has code in there that explicitly looks in the Homebrew install area (/usr/local/opt/qt5
) on macOS, so why would that environment variable be necessary?
In fact, brew --prefix qt5
spits out /usr/local/opt/qt5
, and setting QTDIR64
to that value has literally no effect. I get the exact same error.
What happens when you remove qt5
and install homebrew/versions/qt55
?
Same error, using env QTDIR64=$(brew --prefix qt@5.5) cargo build
.
Also, incidentally, homebrew says homebrew/versions/qt55
is deprecated and the correct syntax is qt@5.5
.
Seems this has been fixed with current master, however whenever you use qml = "0.0.9"
in you will be using a version that will give you the above errors. Instead you should reference a more recent working build. In my project I used the SHA from a PR merged from Feb 22.
qml = { git = "https://github.com/White-Oak/qml-rust", rev = "d731e336fbd1e713"}
I'm trying to build this on macOS 10.12.3. I first installed qt5 with Homebrew via
brew install qt5
, and confirmed that /usr/local/opt/qt5 exists. I then stuckqml = "0.0.9"
in my Cargo.toml and rancargo
build, and it panicked:I'm using CMake 3.7.2.