### Run Bevy FMOD Example with Live Update

Source: https://github.com/salzian/bevy_fmod/blob/main/README.md

This command demonstrates how to run a Bevy FMOD example with the 'live-update' feature enabled. This allows for real-time audio updates during development by connecting FMOD Studio to the running game.

```Shell
cargo run --example minimal --features live-update
```

--------------------------------

### Rust Developer Import Options

Source: https://github.com/salzian/bevy_fmod/blob/main/STYLEGUIDE.md

Shows the two ways a developer can import the FmodStudioPlugin in their code: either directly from the module or via the prelude.

```rust
use bevy_fmod::prelude::*;
// or 
use bevy_fmod::fmod_studio::FmodStudioPlugin;
```

--------------------------------

### Rust Library Code Structure

Source: https://github.com/salzian/bevy_fmod/blob/main/STYLEGUIDE.md

Demonstrates the typical structure for library code in Bevy Fmod, including module definitions and re-exports for the prelude.

```rust
pub mod fmod_studio;

// fmod_studio.rs
pub struct FmodStudioPlugin;

// prelude.rs
pub use crate::fmod_studio::FmodStudioPlugin;
```

--------------------------------

### Add bevy_fmod Dependency

Source: https://github.com/salzian/bevy_fmod/blob/main/README.md

Installs the bevy_fmod crate using Cargo, the Rust package manager. This is the primary method for including the plugin in your Bevy project.

```shell
cargo add bevy_fmod
```

--------------------------------

### macOS FMOD Linking Configuration

Source: https://github.com/salzian/bevy_fmod/blob/main/README.md

Provides a .cargo/config.toml file example for macOS to correctly link FMOD libraries. It specifies library search paths and runtime paths (rpath) to ensure the executable can find the necessary .dylib files.

```toml
[target.aarch64-apple-darwin]
rustflags = [
    "-L", "native=./vendor/fmod",
    "-C", "link-arg=-Wl,-rpath,./vendor/fmod",
]
```

--------------------------------

### macOS Project Structure for FMOD

Source: https://github.com/salzian/bevy_fmod/blob/main/README.md

Illustrates the recommended project directory structure for macOS when integrating FMOD libraries. This includes placing libraries in a 'vendor/fmod' directory and configuring Cargo to use them.

```text
my_game/
├── .cargo/
│   └── config.toml
├── src/
│   └── <source files>
├── vendor/
│   ├── fmod/
│   │   ├── libfmod.dylib
│   │   ├── libfmodL.dylib
│   │   ├── libfmodstudio.dylib
│   │   └── libfmodstudioL.dylib
│   └── <other external libraries>
└── Cargo.toml
```

--------------------------------

### Windows FMOD Library Linking

Source: https://github.com/salzian/bevy_fmod/blob/main/README.md

Demonstrates the required file structure and naming conventions for linking FMOD libraries on Windows. This includes copying DLLs to the project root and renaming them with a '_vc' suffix for compatibility with the libfmod crate.

```text
My Game/
├── My Game.exe
├── fmod_vc.dll
└── fmodstudio_vc.dll
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.