Stream: git-wasmtime

Topic: wasmtime / issue #13732 CMake Build producing very large ...

view this post on Zulip Wasmtime GitHub notifications bot (Jun 24 2026 at 20:40):

Irrgh opened issue #13732:

I tried building wasmtime v44.0.1 as a dependency in my C++ project using the c-api as instructed in https://docs.wasmtime.dev/c-api/.

Building with CMAKE_BUILD_TYPE Debug produces a very large static library:

<img width="800" height="337" alt="Image" src="https://github.com/user-attachments/assets/f934e783-81f4-404c-842f-b6e85aa4be68" />

Under otherwise the same settings for Release it produces:

<img width="764" height="332" alt="Image" src="https://github.com/user-attachments/assets/f8431348-2257-4ced-8558-1147d48884c3" />

Binaries being larger on Debug is not suprising, but more than 2GB for a static lib doesn't really make sense no matter how i think about it.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 29 2026 at 13:47):

alexcrichton closed issue #13732:

I tried building wasmtime v44.0.1 as a dependency in my C++ project using the c-api as instructed in https://docs.wasmtime.dev/c-api/.

Building with CMAKE_BUILD_TYPE Debug produces a very large static library:

<img width="800" height="337" alt="Image" src="https://github.com/user-attachments/assets/f934e783-81f4-404c-842f-b6e85aa4be68" />

Under otherwise the same settings for Release it produces:

<img width="764" height="332" alt="Image" src="https://github.com/user-attachments/assets/f8431348-2257-4ced-8558-1147d48884c3" />

Binaries being larger on Debug is not suprising, but more than 2GB for a static lib doesn't really make sense no matter how i think about it.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 29 2026 at 13:47):

alexcrichton commented on issue #13732:

Rust's debug builds are known to be quite large, so this is just sort of how it is unless you or someone knows how to investigate further and see where all the size is coming from.

Last updated: Jul 29 2026 at 05:03 UTC