bvssvni
commented
3 years ago Check Cargo.lock for different versions of the same library.
Closed Herohtar closed 3 years ago
bvssvni
commented
3 years ago Check Cargo.lock for different versions of the same library.
Herohtar
commented
3 years ago A specific library, or just any duplicates? There are multiple libraries that are listed twice with different versions in Cargo.lock, but cargo tree -d just lists these:
PS D:\piston-rodio> cargo tree -d
gl_generator v0.13.1
[build-dependencies]
└── gl v0.13.0
└── pistoncore-glutin_window v0.69.0
└── piston_window v0.120.0
└── piston-rodio v0.1.0 (D:\piston-rodio)
gl_generator v0.14.0
[build-dependencies]
├── gfx_gl v0.6.1
│ └── gfx_device_gl v0.16.2
│ └── piston_window v0.120.0 (*)
├── glutin_egl_sys v0.1.5
│ └── glutin v0.26.0
│ └── pistoncore-glutin_window v0.69.0 (*)
└── glutin_wgl_sys v0.1.5
└── glutin v0.26.0 (*)
miniz_oxide v0.3.7
└── png v0.16.8
└── image v0.23.14
└── piston-gfx_texture v0.41.0
└── piston2d-gfx_graphics v0.73.0
└── piston_window v0.120.0 (*)
miniz_oxide v0.4.4
└── tiff v0.6.1
└── image v0.23.14 (*)
I'm not sure which package is "at fault" or has the ability to resolve the issue, but
piston_windowno longer plays nice withrodio. Here's the minimal code necessary to reproduce:Cargo.toml
main.rs
Stack trace
Alternative stack trace
This is the stack trace that results from swapping lines 5 and 6 in the example code so that
PistonWindowis initialized beforeOutputStream: