A workspace member with several crate types fails builds of unrelated packages
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 58/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- rust
- Ambito
- build-system
Direzione di ricerca
Start by locating the client-side workspace crate-type check: the report says it runs before the daemon starts and appears to inspect every workspace member. Trace how cargo rustd build -p app selects packages, then compare that with the crate-type validation. Done means the unrelated ffi member no longer blocks app; the report also describes the expected behavior when ffi is a dependency.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
cargo rustd build -p <crate> fails for the whole workspace when any workspace member declares more than one crate type, for example crate-type = ["lib", "cdylib", "staticlib"]. The failing member does not need to be a dependency of the crate being built.
This pattern is common for crates that expose an FFI surface (UniFFI, cbindgen, JNI) and also keep a lib target for Rust consumers.
Reproduction
Environment: macOS arm64 (Darwin), rustd from the nightly release, Rust 1.99.0 with rust-src.
Create a workspace with two members. app is a plain binary. ffi is a library with three crate types. app does not depend on ffi.
Cargo.toml
[workspace]
members = ["app", "ffi"]
resolver = "3"
ffi/Cargo.toml
[package]
name = "ffi"
version = "0.1.0"
edition = "2024"
[lib]
crate-type = ["lib", "cdylib", "staticlib"]
ffi/src/lib.rs
pub fn add(a: u32, b: u32) -> u32 {
a + b
}
app/Cargo.toml
[package]
name = "app"
version = "0.1.0"
edition = "2024"
app/src/main.rs
fn main() {
println!("{}", 1 + 2);
}
Then run:
cargo +1.99.0 rustd build -p app
Actual result
error: `ffi` is built as `lib` and `cdylib` and `staticlib`, which the daemon does not link yet: it builds a `lib`, an `rlib` or a `bin` alone
Expected result
Either of these would help:
- Building
appsucceeds, becauseffiis not in its dependency graph. - If
ffiis a dependency,rustdbuilds itslibtarget and ignores thecdylibandstaticliboutputs when no requested target needs them.
Notes from isolating it
| Variant | Result |
|---|---|
Both crates are workspace members, ffi has three crate types |
Fails, error above |
ffi removed from members (so it is not in the workspace) |
cargo rustd build -p app succeeds |
Both are members, ffi has the default crate type |
cargo rustd build -p app succeeds |
So the check seems to run over every workspace member, not only the packages selected by -p or the dependencies of those packages. I have not read the source, so this is an inference from the behavior.
I also saw that the error is printed even when the daemon is not running (cargo rustd stop reports daemon: not running), so the check looks like it happens in the client before the daemon starts. This is from observation only.
Why it matters
The README already lists "workspace crates built as cdylib, dylib or staticlib" under "What is not supported", so I understand this is a known limit. The part that may be unintended is its reach. A workspace that ships an FFI crate next to other packages cannot use rustd at all today, even for packages that do not touch that crate. The README does not say that the check applies to the whole workspace.
Related: #1 (macOS support). The trivial workspace above builds and runs under rustd on macOS arm64 once ffi is excluded, which is useful data for that issue.
Happy to test a fix or a branch.
- Lingua principale
- Rust
- Stelle
- 248
- Fork
- 13
- Merge medio
- 7h 52m
- PR unite (30g)
- 5
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di DioxusLabs/rustd
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
DioxusLabs/rustd#15 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
DioxusLabs/rustd#28 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
DioxusLabs/rustd#27 ·
I maintainer di solito rispondono entro 1 giorno
-
Workspace fails to load: rquickjs types give layout of …: HasErrorType, and rustd never falls backAperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
DioxusLabs/rustd#26 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 65/100
DioxusLabs/rustd#25 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di DioxusLabs/rustd
Issue simili
-
Bump Python to 3.14 or 3.15Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
bug rust
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 2 giorni
-
type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
franciscoBSalgueiro/en-croissant#1111 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
oxc-project/oxc-htmlish-parser#34 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
longbridge/nsh#2541 ·
I maintainer di solito rispondono entro 1 giorno