From 670730aad1380cf15ee82f8a9d063230c7152399 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Mon, 2 Jul 2018 12:45:21 +0200 Subject: Update intro with changes to bdep-new output --- doc/intro.cli | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/intro.cli b/doc/intro.cli index ea29c48..290eb09 100644 --- a/doc/intro.cli +++ b/doc/intro.cli @@ -215,7 +215,7 @@ $ cat hello/buildfile libs = #import libs += libhello%lib{hello} -exe{hello}: {hxx ixx txx cxx}{*} $libs testscript +exe{hello}: {hxx ixx txx cxx}{**} $libs testscript \ As the name suggests, this file describes how to build things. While its @@ -224,9 +224,9 @@ without going into too much detail (the details are discussed in the following sections). That \c{exe{hello\}} on the left of \c{:} is a \i{target} (executable named \c{hello}) and what we have on the right are \i{prerequisites} (C++ source files, libraries, etc). This \c{buildfile} uses -\l{b#name-patterns wildcard patterns} (that \c{*}) to automatically locate all -the C++ source files. This means we don't have to edit our \c{buildfile} every -time we add, remove, or rename a source file in our project. There also +\l{b#name-patterns wildcard patterns} (that \c{**}) to automatically locate +all the C++ source files. This means we don't have to edit our \c{buildfile} +every time we add, remove, or rename a source file in our project. There also appears to be some (commented out) infrastructure for importing and linking libraries (that \c{libs} variable). We will see how to use it in a moment. -- cgit v1.1