`bevy/dynamic_linking` fails on `SCHEDULE_LABEL_INTERNER`

Abierto
#22 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@sharmis-tp ya está trabajando en esto.

Desde el 26/10/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
build-system

Línea de trabajo

Start by reading the rustd workspace loading and symbol lookup code involved in resolving writable statics from dylib dependencies; the issue does not name specific files or tests. Reproduce with the minimal Bevy app and the reduced dylib example, then compare behavior with and without crate-type = ["dylib"]. Done means rustd handles the exported static or clearly documents this limitation.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Enabling bevy/dynamic_linking makes cargo rustd build fail on a minimal Bevy 0.19.1 app. Plain cargo builds and runs it.

Repro:

# Cargo.toml
[package]
name = "bevy-rustd-repro"
version = "0.1.0"
edition = "2024"

[dependencies]
bevy = { version = "0.19.1", default-features = false, features = ["default_app", "dynamic_linking"] }
// src/main.rs
use bevy::prelude::*;

struct Probe;

impl Plugin for Probe {
    fn build(&self, app: &mut App) {
        app.add_systems(Update, || {});
    }
}

fn main() {
    let mut app = App::new();
    app.add_plugins((MinimalPlugins, Probe));
    app.update();
}

Rust 1.99.0, rustd 0.0.0-4510078-18e09d1a1f901124, Linux x86-64.

cargo run exits 0. cargo rustd build exits 101:

error: the daemon could not load the workspace (exit status: 1: Error:
`...::Probe as ...Plugin>::build` is not compiled by rustd: unsupported:
callee `add_systems`: ... callee `intern`: unsupported: writable static
`SCHEDULE_LABEL_INTERNER` without a rustc symbol)

SCHEDULE_LABEL_INTERNER is the interner behind ScheduleLabel::intern in bevy_ecs. The plugin's add_systems(Update, ...) reaches it through that method, and with bevy_dylib linked the static lives in the dylib.

I reduced it without Bevy. A dylib crate with a private static COUNTER: AtomicUsize and a generic function that increments it fails the same way when an app crate calls that function. Removing crate-type = ["dylib"] makes rustd pass. nm -D shows the static exported by the dylib, so the symbol lookup seems to be the gap, not dylib linking itself. I can post the two crate version if useful.

Is this expected to work? If not, it would help to document the limitation for dylib dependencies.

Lenguaje dominante
Rust
Estrellas
248
Forks
13
Merge medio
7 h 52 min
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DioxusLabs/rustd

Todos los issues de DioxusLabs/rustd

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.