Closed ssempervirens closed 2 years ago
Sorry about the issue you're running into! We've been unable to release a new version of turtle for a few years because of dependency issues (#183). That means that the version on crates.io is severely outdated and won't work on most machines these days. :(
You can usually address this by switching to the master branch as detailed here: https://github.com/sunjay/turtle/issues/202#issuecomment-695811144. You will still run into issues on Mac because of #183, but the crate should be mostly usable.
Appreciate you reporting this issue! Please let me know if this suggestion resolves things for you.
Thanks for the response! I gave that a try, and replaced the crate line in my cargo.toml file with turtle = {git = "https://github.com/sunjay/turtle", rev = "bf64b8333a2be1914378d8a22a4788947711182b"}
.
Unfortunately, I get the same error as before with winit. It seems like this workaround no longer works for some reason. In any case it sounds like this issue isn't new, but what might be new is that switching to the master branch doesn't work?
Thanks again.
I am also having the same issue even after putting the suggested line in.
Does it work if you use the following in your Cargo.toml
? (Removed the rev
so it uses the latest master
branch)
turtle = {git = "https://github.com/sunjay/turtle"}
You may need to run cargo update
in conjunction with this to make sure Cargo updates your Cargo.lock file to the latest revision of this repository.
Please keep in mind that the crate will have some known bugs (#183) when you use the master branch like this. It should hopefully still be fairly usable though.
Appears to be fixed now (at least on the master branch). Make sure you run cargo update
so you have latest version of all the dependencies. My Cargo.lock
file lists winit
version 0.25.0
and that seems to work fine.
I tried to add turtle to my project by adding
turtle = "1.0.0-rc.3"
. When I rancargo build
, I get a compile error which looks to be an issue of one of turtle's dependencies, winit v0.19.5. This might be a mac specific issue of some kind? I am on a M1 macbook, Big Sur version 11.2.3. Here's the mess of error I get. Thanks for any help resolving this, and thanks again for your work maintaining this project!