Armin

@ilopX This looks like different build error to me, most likely related to #314. An because I am not sure the error happens with Python 3 we switched to recently,...

Update: The stale IDE results were caused by IntelliJs Rust plugin when `cargo check` was enabled, and were fixed in a recent nightly. Also the macro support was improved, so...

I'm reopening this, because Rust / Cargo release version 1.33 might affect us: https://github.com/rust-lang/rust/blob/stable/RELEASES.md#cargo

This issue seems to stick with us until it gets fixed properly. Currently, there are two problems caused by it: - The crate verfication of skia-bindings fails, because it detects...

@JackRedstonia Sounds unrelated, every time the build scripts runs from within a crate, binaries are downloaded. I suppose that there should be a test if matching binaries already exist.

Here an update regarding the blockers for the PR: # Rust Analyzer has full support, but it must be enabled in the VSCode settings first: ```json { "rust-analyzer.cargoFeatures.loadOutDirsFromCheck": true, }...

@willcassella Thank you for sharing, I'd like to keep this issue open until I've time to reproduce the problem and perhaps find a workaround in the build support of skia-bindings.

@yohopanda Ok, I am planning to release binaries (at least d3d, d3d+textlayout) with 0.34.0, if you need more feature configurations, please open a new issue for that.

@JackRedstonia You've mentioned that the download happens every time a compiler flag is changed. Can you provide one example that can be used to prove a working fix? I am...

@jedahan I think it should not make a difference, because the Skia branch in use is already tainted (i.e. needs a number of commits on top of it to compile...