Modules compile in the toolchain and ship on the runtime #22

2026-09-14T00:02:22Z

jschoubben commented

2026-09-14 00:02:22 +00:00

Each of the three modules now names two bases rather than one: the image it is compiled in, and the image it runs in. The mesh answers both with the copies it holds.

The effect is that the compiler stops travelling into everything that runs. postgres comes out at 97 MB rather than around 300, and still carries the database client it provisions through; the catalogue at 80 MB, still carrying its own database driver.

Verified on a bare machine: both bases built from one recipe, then all three modules built against them, each image containing its compiled code, the library, and no compiler.

Needs mesh-tools' split and mesh-control's target support.

Each of the three modules now names two bases rather than one: the image it is compiled in, and the image it runs in. The mesh answers both with the copies it holds. The effect is that the compiler stops travelling into everything that runs. postgres comes out at 97 MB rather than around 300, and still carries the database client it provisions through; the catalogue at 80 MB, still carrying its own database driver. Verified on a bare machine: both bases built from one recipe, then all three modules built against them, each image containing its compiled code, the library, and no compiler. Needs mesh-tools' split and mesh-control's `target` support.

jschoubben added 1 commit 2026-09-14 00:02:23 +00:00

Modules compile in the toolchain and ship on the runtime cf116a4932

jschoubben merged commit 071afc1e2c into main

2026-09-14 00:02:42 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#22