From f44fdc24c5b8d99a71ea8adaadb96af0d1162c92 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Tue, 4 Feb 2020 09:03:01 +0200
Subject: Add note to intro on specifying search paths in compiler mode

---
 doc/intro.cli | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/doc/intro.cli b/doc/intro.cli
index c703399..82c15a8 100644
--- a/doc/intro.cli
+++ b/doc/intro.cli
@@ -429,6 +429,19 @@ $ bdep init ... cc      \
   config.cxx=\"clang++ -m32 -stdlib=libc++\"
 \
 
+The compiler mode options are also the correct place to specify
+\i{system-like} header (\c{-I}) and library (\c{-L}, \c{/LIBPATH}) search
+paths. Where by system-like we mean common installation directories like
+\c{/usr/include} or \c{/usr/local/lib} which may contain older versions of the
+libraries we are trying to build and/or use. By specifying these paths as part
+of the mode options (as opposed to \c{config.*.poptions} and
+\c{config.*.loptions}) we make sure they will be considered last, similar to
+the compiler's build-in search paths. For example:
+
+\
+$ bdep init ... cc config.cxx=\"g++ -L/opt/install\"
+\
+
 |
 
 One difference you might have noticed when creating the \c{gcc} and \c{clang}
-- 
cgit v1.1