diff options
author | Mats Wichmann <mats@linux.com> | 2022-05-23 14:18:51 (GMT) |
---|---|---|
committer | Mats Wichmann <mats@linux.com> | 2022-05-25 18:31:19 (GMT) |
commit | b14c20e353712291e0321c0fa1e7557bf385ea04 (patch) | |
tree | a5e078ed029b3a674c1f757199699da5f8c0dc67 | |
parent | 45e9eec5a86adcd815a9bebfba536a44c7f9a756 (diff) | |
download | SCons-b14c20e353712291e0321c0fa1e7557bf385ea04.zip SCons-b14c20e353712291e0321c0fa1e7557bf385ea04.tar.gz SCons-b14c20e353712291e0321c0fa1e7557bf385ea04.tar.bz2 |
Further tweak of VariantDir doc [skip appveyor]
Signed-off-by: Mats Wichmann <mats@linux.com>
-rw-r--r-- | SCons/Environment.xml | 15 |
1 files changed, 6 insertions, 9 deletions
diff --git a/SCons/Environment.xml b/SCons/Environment.xml index 346fc75..294562d 100644 --- a/SCons/Environment.xml +++ b/SCons/Environment.xml @@ -3482,14 +3482,11 @@ The subsidiary SConscript file must be called as if it were in <parameter>variant_dir</parameter>, regardless of the value of <parameter>duplicate</parameter>. -When calling an SConscript file, -you can pass an appropriately set up environment -using the <parameter>exports</parameter> keyword -argument so the SConscript can pick up the right settings -for that variant build. -This is how you tell -&scons; -which variant of a source directory to build: +When calling an SConscript file, you can use the +<parameter>exports</parameter> keyword argument +to pass parameters (individually or as an appropriately set up environment) +so the SConscript can pick up the right settings for that variant build. +The SConscript must &f-link-Import; these to use them. Example: </para> <example_commands> @@ -3511,7 +3508,7 @@ in conjunction with calling a subsidiary SConscript file. </para> <para> -Examples: +More examples: </para> <example_commands> |