19 unstable releases (9 breaking)

0.13.2 Apr 4, 2024
0.13.1 Mar 18, 2024
0.13.0 Feb 17, 2024
0.12.1 Nov 30, 2023
0.4.0 Dec 19, 2020

#2191 in Game dev

Download history 2265/week @ 2024-01-03 3143/week @ 2024-01-10 2654/week @ 2024-01-17 3011/week @ 2024-01-24 2321/week @ 2024-01-31 3107/week @ 2024-02-07 3616/week @ 2024-02-14 3263/week @ 2024-02-21 3193/week @ 2024-02-28 3101/week @ 2024-03-06 2782/week @ 2024-03-13 3692/week @ 2024-03-20 3295/week @ 2024-03-27 3406/week @ 2024-04-03 2699/week @ 2024-04-10 2658/week @ 2024-04-17

12,539 downloads per month
Used in 52 crates (via bevy)

MIT/Apache

34KB
289 lines

Forces dynamic linking of Bevy.

Dynamic linking causes Bevy to be built and linked as a dynamic library. This will make incremental builds compile much faster.

Warning

Do not enable this feature for release builds because this would require you to ship libstd.so and libbevy_dylib.so with your game.

Enabling dynamic linking

The easiest way to enable dynamic linking is to use the --features bevy/dynamic_linking flag when using the cargo run command:

cargo run --features bevy/dynamic_linking

The unrecommended way

It is also possible to enable the dynamic_linking feature inside of the Cargo.toml file. This is unrecommended because it requires you to remove this feature every time you want to create a release build to avoid having to ship additional files with your game.

To enable dynamic linking inside of the Cargo.toml file add the dynamic_linking feature to the bevy dependency:

features = ["dynamic_linking"]

The manual way

Manually enabling dynamic linking is achieved by adding bevy_dylib as a dependency and adding the following code to the main.rs file:

#[allow(unused_imports)]
use bevy_dylib;

It is recommended to disable the bevy_dylib dependency in release mode by adding the following code to the use statement to avoid having to ship additional files with your game:

#[allow(unused_imports)]
#[cfg(debug_assertions)] // new
use bevy_dylib;

Dependencies

~16–46MB
~725K SLoC