-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
example_bot build fail #2
Comments
You need to build the example bot for the |
rustup target add wasm32-unknown-unknown
cd example_bot
cargo build compiled. next is \botnet> cargo build or > cargo build --release --manifest-path=botnet/Cargo.toml results in Compiling botnet v0.1.0 (C:\Users\Death\Desktop\Botnet\botnet\botnet)
error: couldn't read src\../../example_bot/target/wasm32-unknown-unknown/release/example_bot.wasm: The system cannot find the path specified. (os error 3)
--> src\game.rs:41:21
|
41 | / include_bytes!(
42 | | "../../example_bot/target/wasm32-unknown-unknown/release/example_bot.wasm"
43 | | ),
| |_____________________^
|
= note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)
error: could not compile `botnet` due to previous error |
You need to compile the example bot in release, or change that include_bytes path to /debug/. |
Attempt to run server PS C:\Users\Death\Desktop\Botnet\botnet> RUST_LOG=botnet cargo run --manifest-path=botnet/Cargo.toml
RUST_LOG=botnet : The term 'RUST_LOG=botnet' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ RUST_LOG=botnet cargo run --manifest-path=botnet/Cargo.toml
+ ~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (RUST_LOG=botnet:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException |
|
Fail to build
example_bot
. Standard recomended Rust install config, Win 11, 64-bit,Error log
The text was updated successfully, but these errors were encountered: