Egui logo embedded in the binary?

[UnknownSuperficialNight]

Why is the egui logo embedded in the binary I'm using eframe and am on Linux

Tooling used to find is ghidra

any way to toggle this off?

[gitsult4n]

It is eframe's default window icon, not egui branding sneaking into your app.

crates/eframe/data/icon.png, 12 KB, is pulled in unconditionally at crates/eframe/src/native/epi_integration.rs:440:

fn load_default_egui_icon() -> egui::IconData {
    crate::icon_data::from_png_bytes(&include_bytes!("../../data/icon.png")[..]).unwrap()
}

and used as the fallback when you did not set one, :205:

let icon = native_options
    .viewport
    .icon
    .clone()
    .unwrap_or_else(|| std::sync::Arc::new(load_default_egui_icon()));

So on Linux it becomes the window/taskbar icon of any eframe app that leaves viewport.icon unset.

To stop it being used, set your own:

let options = eframe::NativeOptions {
    viewport: egui::ViewportBuilder::default()
        .with_icon(eframe::icon_data::from_png_bytes(include_bytes!("../assets/my_icon.png")).unwrap()),
    ..Default::default()
};

(ViewportBuilder::with_icon, crates/egui/src/viewport.rs:434.)

There is no feature flag that drops the bytes, though, and setting your own icon will not remove them from the binary either. The include_bytes! is unconditional, and the fallback branch is chosen at runtime from native_options, so the linker cannot prove the data is unreachable. Getting rid of the 12 KB means patching or vendoring eframe, or driving egui through your own winit integration instead.

Read off egui/eframe 0.36.1 (caea233). The dead-code point is reasoning about the code shape, I did not build a binary and diff it.