One source, two images, deliberately different: a toolchain image carries a compiler and everything a build needs, and the image the same module runs in should carry neither.
Describing both in one recipe keeps them in step — they share a base, a library version and an operating system — while letting each be built and published separately. Empty means the whole recipe, which is what a module with one image says by saying nothing.
Enables mesh-tools splitting its single 280 MB image into a 129 MB toolchain and an 80 MB runtime.
One source, two images, deliberately different: a toolchain image carries a compiler and everything a build needs, and the image the same module *runs* in should carry neither.
Describing both in one recipe keeps them in step — they share a base, a library version and an operating system — while letting each be built and published separately. Empty means the whole recipe, which is what a module with one image says by saying nothing.
Enables mesh-tools splitting its single 280 MB image into a 129 MB toolchain and an 80 MB runtime.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
One source, two images, deliberately different: a toolchain image carries a compiler and everything a build needs, and the image the same module runs in should carry neither.
Describing both in one recipe keeps them in step — they share a base, a library version and an operating system — while letting each be built and published separately. Empty means the whole recipe, which is what a module with one image says by saying nothing.
Enables mesh-tools splitting its single 280 MB image into a 129 MB toolchain and an 80 MB runtime.