examples `chaos_game` and `threads` not building, winit unresolved imports
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 193
- Forks
- 100
- Avg merge
- 17h 55m
- Merged PRs (30d)
- 9
Description
In trying to track down a Metal issue with pathfinder, I'm trying to build and run the demos here.
The offscreen demo builds and runs fine, but the chaos_game and threads demos both fail with the same compile errors:
Compiling surfman v0.4.3 (/Users/.../surfman/surfman)
error[E0432]: unresolved imports `winit::DeviceEvent`, `winit::Event`, `winit::EventsLoop`, `winit::KeyboardInput`, `winit::VirtualKeyCode`
--> surfman/examples/chaos_game.rs:9:13
|
9 | use winit::{DeviceEvent, Event, EventsLoop, KeyboardInput, VirtualKeyCode};
| ^^^^^^^^^^^ ^^^^^ ^^^^^^^^^^ ^^^^^^^^^^^^^ ^^^^^^^^^^^^^^ no `VirtualKeyCode` in the root
| | | | |
| | | | no `KeyboardInput` in the root
| | | no `EventsLoop` in the root
| | no `Event` in the root
| no `DeviceEvent` in the root
error[E0432]: unresolved imports `winit::WindowBuilder`, `winit::WindowEvent`
--> surfman/examples/chaos_game.rs:10:13
|
10 | use winit::{WindowBuilder, WindowEvent};
| ^^^^^^^^^^^^^ ^^^^^^^^^^^ no `WindowEvent` in the root
| |
| no `WindowBuilder` in the root
This is on macOS 12.1, rustc 1.58.0.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with surfman/examples/chaos_game.rs and the corresponding threads example, focusing on the unresolved winit imports shown in the report. Check the winit dependency and API used by both demos, then verify that the chaos_game and threads examples build successfully on the reported Rust setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100