Add script to debug fixed point numbers in lldb
This commit is contained in:
@@ -2,6 +2,15 @@
|
||||
|
||||
Fancy heavily advanced platform fighting game
|
||||
|
||||
## Debugging fixed-point values with lldb
|
||||
|
||||
If using CodeLLDB:
|
||||
```json
|
||||
"preRunCommands": [
|
||||
"command script import ${workspaceFolder}/tools/lldb_fixed.py"
|
||||
]
|
||||
```
|
||||
|
||||
## Direct P2P Debugging
|
||||
|
||||
```text
|
||||
@@ -16,18 +25,9 @@ cargo run -- --debug-match --players 2 --local-port 7001 \
|
||||
|
||||
## Production Build
|
||||
|
||||
Production builds use the `production` Cargo profile and do not dynamically
|
||||
link Bevy or Rust. Development builds retain Bevy dynamic linking for faster
|
||||
iteration. Cargo stores the production profile under `target/production`,
|
||||
separate from development artifacts under `target/debug`.
|
||||
|
||||
```sh
|
||||
cargo run --locked \
|
||||
--bin process-assets --no-default-features --features debug_features
|
||||
cargo build --locked \
|
||||
--profile production --no-default-features --features debug_features
|
||||
```
|
||||
|
||||
The asset preprocessing command must be run from the repository root. It
|
||||
populates `imported_assets/Default`, which is then consumed by the production
|
||||
game without running the asset processor at startup.
|
||||
```
|
||||
Reference in New Issue
Block a user