bors[bot] ca2193201d Merge #82
82: Return Queue separately r=grovesNL a=kvark

What problem is this PR trying to solve? We want `Device` to be freely accessible from multiple threads/objects and internally synchronized. `Arc<Device>` seems like a natural choice of such a sharable object, especially since all except one methods are `&self`.

That one method is `get_queue()`, and it returns a temporary object `Queue<'a>`. If we turn it into `&self`, we'd end up with multiple instances of `Queue` created at any time, which contradicts the initial design (of this Rust wrapper). If it stays `&mut` and the user wraps the device into `Arc`, they'll never be able to submit any work...

So this PR solves this by moving the `Queue` completely outside of the device.

Co-authored-by: Dzmitry Malyshau <dmalyshau@mozilla.com>
2019-09-10 13:27:14 +00:00
2019-06-16 21:15:22 -07:00
2019-09-10 09:26:18 -04:00
2019-09-10 09:26:18 -04:00
2019-08-21 23:51:09 -04:00
2019-06-16 21:15:15 -07:00
2019-09-09 21:39:55 -04:00
2019-05-10 10:36:31 -04:00

wgpu-rs

Build Status Crates.io Gitter

This is an idiomatic Rust wrapper over wgpu-native. It's designed to be suitable for general purpose graphics and computation needs of Rust community. It currently only works for the native platform, in the future aims to support WASM/Emscripten platforms as well.

Cube Shadow MipMap vange-rs Brawl GLX map

Usage

Running an example

All examples are located under the examples directory. We are using the default syntax for running examples, as found in the Cargo documentation.

cargo run --example cube

Hello Compute

hello-* examples show barebones setup without any helper code.

For "hello-compute", pass 4 numbers separated by spaces as arguments:

cargo run --example hello-compute 1 2 3 4

More examples can be found under the examples directory.

Friends

Shout out to the following projects that work best with wgpu-rs:

Development

If you need to test local fixes to gfx-rs or other dependencies, the simplest way is to add a Cargo patch. For example, when working on DX12 backend on Windows, you can check out the "hal-0.2" branch of gfx-rs repo and add this to the end of "Cargo.toml":

[patch.crates-io]
gfx-backend-dx12 = { path = "../gfx/src/backend/dx12" }
gfx-hal = { path = "../gfx/src/hal" }

If a version needs to be changed, you need to to do cargo update -p gfx-backend-dx12.

Description
No description provided
Readme 137 MiB
Languages
Rust 79.9%
WGSL 16.2%
HLSL 2%
GLSL 1.7%
JavaScript 0.2%