From 38a2dca937a0af1cd7456ed7508c1540e93b1ac2 Mon Sep 17 00:00:00 2001 From: Yannik Tausch Date: Tue, 5 Mar 2024 14:34:57 +0100 Subject: [PATCH] Clarify run_exports/weak --- docs/source/resources/define-metadata.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/source/resources/define-metadata.rst b/docs/source/resources/define-metadata.rst index e0e5bfff2d..720f4f4624 100644 --- a/docs/source/resources/define-metadata.rst +++ b/docs/source/resources/define-metadata.rst @@ -734,7 +734,7 @@ implicitly added by host requirements (e.g. libpng exports libpng), and with - libpng Here, because no specific kind of ``run_exports`` is specified, libpng's ``run_exports`` -are considered "weak." This means they will only apply when libpng is in the +are considered "weak". This means they will only apply when libpng is in the host section, when they will add their export to the run section. If libpng were listed in the build section, the ``run_exports`` would not apply to the run section. @@ -746,6 +746,9 @@ listed in the build section, the ``run_exports`` would not apply to the run sect strong: - libgcc +There is also ``run_exports/weak`` which is equivalent to an unspecific kind of +``run_exports`` but useful if you want to define both strong and weak run exports. + Strong ``run_exports`` are used for things like runtimes, where the same runtime needs to be present in the host and the run environment, and exactly which runtime that should be is determined by what's present in the build section.