Closed gww-parity closed 3 years ago
Please note that it works for:
The optick crate only provides windows binaries, so the error when running the first command on linux is expected.
For the second error, I'm not certain, but my guess is that this change (https://github.com/imgui-rs/imgui-rs/commit/7e2293bde67f869750ab0e649fbfbd842fb0c785#diff-f54c36ae82d7f23d02ea587211a3211db799fabe7b22c4eb5bad39bcc8fcfa7d) has caused imgui_winit_support to use winit 0.24 and everything else to use 0.23, leading to these errors. You can try running:
cargo update --package imgui_winit_support --precise 0.6.0
to confirm if this is the correct issue.
Or something like this:
cargo update --package winit --precise 0.23
cargo update --package winit:0.24.0 --precise 0.23
"multiple versions of winit at once" seems to happen a lot sadly
Therefore maybe it's god to block optick code by adding something like?
// Optick is Windows Only?
#[cfg(target_os = "windows")]
Or maybe use some macros to get on Linux more meaningful error message? (or comment in build file too?)
I've added clearer messaging to the readme on platform support, so hopefully that helps!
The other build error can be fixed with cargo update -p winit:0.24.0 --precise 0.23
. It's very unfortunate, but it's caused by imgui-rs being updated in a non-semver-compatible way, and I don't see an out-of-the-box alternative that will force it to use the intended version of winit by default. Thankfully this only affects the example, not the published crate. The best fix for this might be to update the upstream dependencies to also use winit 0.24, but I'm not sure exactly when I'll get around to doing it.
(It's also worth noting that winit 0.24 is required for apple silicon support)
Fixed it by forcing imgui_winit_support = "=0.6.0"
Added issue here: https://github.com/imgui-rs/imgui-rs/issues/412 - I'm hoping we can find a better long term solution than pinning an exact version
After running copy&paste form examples section:
OR
Things does not compile.
Error for second "only puffing" example:
for first example :
Using:
It happens when using
+stable
and+nightly