Mirrors/bevy
2
0
Fork 0
mirror of https://github.com/bevyengine/bevy synced 2024-11-22 20:53:53 +00:00
Code Issues Projects Releases Packages Wiki Activity
bevy/crates/bevy_tasks/Cargo.toml

27 lines
634 B
TOML
Raw Normal View History

Task System for Bevy (#384) Add bevy_tasks crate to replace rayon
2020-08-29 19:35:41 +00:00
[package]
name = "bevy_tasks"
Bump Version after Release (#9106) CI-capable version of #9086 --------- Co-authored-by: Bevy Auto Releaser <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: François <mockersf@gmail.com>
2023-07-10 21:19:27 +00:00
version = "0.12.0-dev"
Update to edition 2021 on master (#3028) Objective During work on #3009 I've found that not all jobs use actions-rs, and therefore, an previous version of Rust is used for them. So while compilation and other stuff can pass, checking markup and Android build may fail with compilation errors. Solution This PR adds `action-rs` for any job running cargo, and updates the edition to 2021.
2021-10-27 00:12:14 +00:00
edition = "2021"
release: 0.3.0 (#783)
2020-11-03 21:34:00 +00:00
description = "A task executor for Bevy Engine"
homepage = "https://bevyengine.org"
repository = "https://github.com/bevyengine/bevy"
Relicense Bevy under the dual MIT or Apache-2.0 license (#2509) This relicenses Bevy under the dual MIT or Apache-2.0 license. For rationale, see #2373. * Changes the LICENSE file to describe the dual license. Moved the MIT license to docs/LICENSE-MIT. Added the Apache-2.0 license to docs/LICENSE-APACHE. I opted for this approach over dumping both license files at the root (the more common approach) for a number of reasons: * Github links to the "first" license file (LICENSE-APACHE) in its license links (you can see this in the wgpu and rust-analyzer repos). People clicking these links might erroneously think that the apache license is the only option. Rust and Amethyst both use COPYRIGHT or COPYING files to solve this problem, but this creates more file noise (if you do everything at the root) and the naming feels way less intuitive. * People have a reflex to look for a LICENSE file. By providing a single license file at the root, we make it easy for them to understand our licensing approach. * I like keeping the root clean and noise free * There is precedent for putting the apache and mit license text in sub folders (amethyst) * Removed the `Copyright (c) 2020 Carter Anderson` copyright notice from the MIT license. I don't care about this attribution, it might make license compliance more difficult in some cases, and it didn't properly attribute other contributors. We shoudn't replace it with something like "Copyright (c) 2021 Bevy Contributors" because "Bevy Contributors" is not a legal entity. Instead, we just won't include the copyright line (which has precedent ... Rust also uses this approach). * Updates crates to use the new "MIT OR Apache-2.0" license value * Removes the old legion-transform license file from bevy_transform. bevy_transform has been its own, fully custom implementation for a long time and that license no longer applies. * Added a License section to the main readme * Updated our Bevy Plugin licensing guidelines. As a follow-up we should update the website to properly describe the new license. Closes #2373
2021-07-23 21:11:51 +00:00
license = "MIT OR Apache-2.0"
release: 0.3.0 (#783)
2020-11-03 21:34:00 +00:00
keywords = ["bevy"]
Task System for Bevy (#384) Add bevy_tasks crate to replace rayon
2020-08-29 19:35:41 +00:00
Add optional single-threaded feature to bevy_ecs/bevy_tasks (#6690) # Objective Fixes #6689. ## Solution Add `single-threaded` as an optional non-default feature to `bevy_ecs` and `bevy_tasks` that: - disable the `ParallelExecutor` as a default runner - disables the multi-threaded `TaskPool` - internally replace `QueryParIter::for_each` calls with `Query::for_each`. Removed the `Mutex` and `Arc` usage in the single-threaded task pool. ![image](https://user-images.githubusercontent.com/3137680/202833253-dd2d520f-75e6-4c7b-be2d-5ce1523cbd38.png) ## Future Work/TODO Create type aliases for `Mutex`, `Arc` that change to single-threaaded equivalents where possible. --- ## Changelog Added: Optional default feature `multi-theaded` to that enables multithreaded parallelism in the engine. Disabling it disables all multithreading in exchange for higher single threaded performance. Does nothing on WASM targets. --------- Co-authored-by: Carter Anderson <mcanders1@gmail.com>
2023-07-09 04:22:15 +00:00
[features]
multi-threaded = []
Task System for Bevy (#384) Add bevy_tasks crate to replace rayon
2020-08-29 19:35:41 +00:00
[dependencies]
update dependencies (#470)
2020-09-10 19:54:24 +00:00
futures-lite = "1.4.0"
Update async-executor to 1.3.0 (#526)
2020-09-20 18:27:24 +00:00
async-executor = "1.3.0"
Update multitask dependency to async-executor (#452) * Switch from the deprecated `multitask` crate to `async-executor` * async-executor appears to be essentially multitask 0.3 * use block_on in futures_lite instead of pollster because futures_lite is already in the dependency list of async-executor
2020-09-09 20:12:50 +00:00
async-channel = "1.4.2"
Allow using async_io::block_on in bevy_tasks (#9626) # Objective Fixes #9625 ## Solution Adds `async-io` as an optional dependency of `bevy_tasks`. When enabled, this causes calls to `futures_lite::future::block_on` to be replaced with calls to `async_io::block_on`. --- ## Changelog - Added a new `async-io` feature to `bevy_tasks`. When enabled, this causes `bevy_tasks` to use `async-io`'s implemention of `block_on` instead of `futures-lite`'s implementation. You should enable this if you use `async-io` in your application.
2023-09-25 19:59:50 +00:00
async-io = { version = "1.13.0", optional = true }
fix: explicitly specify required version of async-task (#6509) # Objective Attempting to build `bevy_tasks` produces the following error: ``` error[E0599]: no method named `is_finished` found for struct `async_executor::Task` in the current scope --> /[...]]/bevy/crates/bevy_tasks/src/task.rs:51:16 | 51 | self.0.is_finished() | ^^^^^^^^^^^ method not found in `async_executor::Task<T>` ``` It looks like this was introduced along with `Task::is_finished`, which delegates to `async_task::Task::is_finished`. However, the latter was only introduced in `async-task` 4.2.0; `bevy_tasks` does not explicitly depend on `async-task` but on `async-executor` ^1.3.0, which in turn depends on `async-task` ^4.0.0. ## Solution Add an explicit dependency on `async-task` ^4.2.0.
2022-11-07 21:43:07 +00:00
async-task = "4.2.0"
Update concurrent-queue to 2.0 (#6538) Co-authored-by: devil-ira <justthecooldude@gmail.com>
2022-12-13 21:00:43 +00:00
concurrent-queue = "2.0.0"
Remove unused deps (#2455) # Objective Reduce compilation time # Solution Remove unused dependencies. While this PR doesn't remove any crates from `Cargo.lock`, it may unlock more build parallelism.
2021-07-14 20:52:50 +00:00
WASM asset loading (#559) wasm assets
2020-09-25 22:26:23 +00:00
[target.'cfg(target_arch = "wasm32")'.dependencies]
wasm-bindgen-futures = "0.4"
Remove unused deps (#2455) # Objective Reduce compilation time # Solution Remove unused dependencies. While this PR doesn't remove any crates from `Cargo.lock`, it may unlock more build parallelism.
2021-07-14 20:52:50 +00:00
[dev-dependencies]
instant = { version = "0.1", features = ["wasm-bindgen"] }
Reference in a new issue Copy permalink