Env - deps`arborium` build failed
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- macos, rust, wasm
- Domain
- build-system
Research direction
Start with the dependency declarations in Cargo.toml and reproduce the failure with dx serve for a wasm32-unknown-unknown target. Read the arborium-sysroot v2.18.1 build output and compare how CC and CXX are handled on macOS; done means the documented reproduction builds without the Apple Clang WebAssembly-target error.
Written by the indexing model from the issue text.
Description
Description
Using dioxus-code in a Dioxus web application causes the WASM build
to compile arborium-sysroot.
On macOS, the default Apple Clang does not include the WebAssembly
backend, so dx serve fails unless CC and CXX are explicitly set
to a Homebrew LLVM installation.
Reproduction
Cargo.toml:
[dependencies]
dioxus = "0.7"
dioxus-code = "0.1"
Then run:
dx serve
Environment
- macOS
- Apple Clang
- dioxus-code 0.1.2
- target: wasm32-unknown-unknown
Output
[cargo] error: failed to run custom build command for `arborium-sysroot v2.18.1`
[cargo] Caused by:
...
[cargo] cargo:warning=error: unable to create target: 'No available targets are compatible with triple "wasm32-unknown-unknown"'
- Dominant language
- CSS
- Stars
- 8
- Forks
- 0
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
open-telemetry/opentelemetry-go-compile-instrumentation#1450 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
bazel-contrib/rules_go#4736 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day