tauri-docs
tauri-docs copied to clipboard
Error with build Rust example
Comand : cargo make run
I get the error:
error: failed to run custom build command for `yew v0.17.2`
--- stderr
thread 'main' panicked at 'Yew does not allow the `web_sys` and `std_web` cargo features to be used simultaneously', /home/euuki/.cargo/registry/src/github.com-1ecc6299db9ec823/yew-0.17.2/build.rs:7:9
stack backtrace:
0: 0x5611b1046d05 - backtrace::backtrace::libunwind::trace::h396c07d2071b43af
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86
1: 0x5611b1046d05 - backtrace::backtrace::trace_unsynchronized::h7aa0e4bb23d9c158
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66
2: 0x5611b1046d05 - std::sys_common::backtrace::_print_fmt::hd15ac5d4adcd355b
at src/libstd/sys_common/backtrace.rs:78
3: 0x5611b1046d05 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hec5354be8ccc3ecc
at src/libstd/sys_common/backtrace.rs:59
4: 0x5611b1063b5c - core::fmt::write::h3d34909eeb4f225b
at src/libcore/fmt/mod.rs:1076
5: 0x5611b10454b3 - std::io::Write::write_fmt::h1da287b3de55ed16
at src/libstd/io/mod.rs:1537
6: 0x5611b1049210 - std::sys_common::backtrace::_print::h4d206838e1ace354
at src/libstd/sys_common/backtrace.rs:62
7: 0x5611b1049210 - std::sys_common::backtrace::print::h1f778e9940ee5977
at src/libstd/sys_common/backtrace.rs:49
8: 0x5611b1049210 - std::panicking::default_hook::{{closure}}::h704403a56cbf5783
at src/libstd/panicking.rs:198
9: 0x5611b1048f5c - std::panicking::default_hook::ha4567a10dec4ef8d
at src/libstd/panicking.rs:218
10: 0x5611b10497f7 - std::panicking::rust_panic_with_hook::h88a1f16ec8a7bb20
at src/libstd/panicking.rs:486
11: 0x5611b1041085 - std::panicking::begin_panic::h3598f0db20e8a237
at /rustc/5c1f21c3b82297671ad3ae1e8c942d2ca92e84f2/src/libstd/panicking.rs:410
12: 0x5611b10414f5 - build_script_build::main::h85370e4dcdf6f937
at /home/euuki/.cargo/registry/src/github.com-1ecc6299db9ec823/yew-0.17.2/build.rs:7
13: 0x5611b1040cab - std::rt::lang_start::{{closure}}::ha9c6bfcd5e96c3b2
at /rustc/5c1f21c3b82297671ad3ae1e8c942d2ca92e84f2/src/libstd/rt.rs:67
14: 0x5611b1049bc8 - std::rt::lang_start_internal::{{closure}}::h6d21eebfa4beaf70
at src/libstd/rt.rs:52
15: 0x5611b1049bc8 - std::panicking::try::do_call::h560a27b87db38b9c
at src/libstd/panicking.rs:297
16: 0x5611b1049bc8 - std::panicking::try::h453d4afd696011f9
at src/libstd/panicking.rs:274
17: 0x5611b1049bc8 - std::panic::catch_unwind::h211d02671f23030f
at src/libstd/panic.rs:394
18: 0x5611b1049bc8 - std::rt::lang_start_internal::h464df2bbf46c7e7c
at src/libstd/rt.rs:51
19: 0x5611b1040c87 - std::rt::lang_start::heafefdaace759a1b
at /rustc/5c1f21c3b82297671ad3ae1e8c942d2ca92e84f2/src/libstd/rt.rs:67
20: 0x5611b10415fa - main
21: 0x7f3f3558b0b3 - __libc_start_main
22: 0x5611b104017e - _start
23: 0x0 - <unknown>
warning: build failed, waiting for other jobs to finish...
error: build failed
error: build failed
[cargo-make] ERROR - Error while executing command, exit code: 101
[cargo-make] WARN - Build Failed.
I try build example with clear rust With node Work :+1:
$ yarn init
$ yarn add tauri
$ yarn tauri init
$ mkdir example_app/dist
$ touch example_app/dist/index.html (And some simple html and css code line)
$ yarn tauri build --debug
Examples as so no clear. I want build app with backend rust and frontend with rust(this will the best). If I couldn't frontend rust that how other ? What is my frontend part what backend. In my opinion is needed one very clear tutorial how build app from zero to debug in ONE techonologes (best in Rust :) ) For me on the web page is no clear https://tauri.studio/docs/development/integration How add frontend filess and connect with src-tauri. But probably i do some wrong. In other side very good project and i'm hopefully that will be grows.
I agree that we need better documentation about how to do what it is that you want to do. Unfortunately, these examples are primarily for our core smoke-testing needs to make sure that builds actually continue to work. I am moving this issue to the documentation repo, because as things stand we don't hold anybody's hand when they are trying to integrate with their front end framework of choice.