From b3baa94eb11ac42bc0f23f1b0966d9cbc0e71601 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Fri, 9 Apr 2021 09:51:44 +0200 Subject: Mention hermetic build configuration support in introduction --- doc/intro.cli | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/intro.cli b/doc/intro.cli index b59dd6d..006d603 100644 --- a/doc/intro.cli +++ b/doc/intro.cli @@ -395,7 +395,15 @@ an absolute path to \c{cl.exe} that you wish to use. For example: ... \ -| +In case of the command prompt, you may also want to make your configuration +\i{hermetic} (\l{b#module-config-hermetic Hermetic Build Configurations}): + +\ +> bdep init -C ... cc ... config.config.hermetic=true +\ + +Hermetically configuring our project in a suitable Visual Studio command +prompt makes us free to build it from any other prompt or shell, IDE, etc.| \N|Besides the \c{coptions} (compile options) and \c{loptions} (link options), other commonly used \c{cc} module configuration variables are \c{poptions} -- cgit v1.1