diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2018-06-05 12:27:25 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2018-06-05 12:27:25 +0200 |
commit | 431766f1d16d19427fa30bcb676d3b4ea4ab8966 (patch) | |
tree | 7cb3a17c303ed7ed645d2c588ffc5286bdf467f3 /doc | |
parent | a9245dcfa498f125649e277ce32a7a92ff02fe05 (diff) |
Fix typo in intro
Diffstat (limited to 'doc')
-rw-r--r-- | doc/intro.cli | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/intro.cli b/doc/intro.cli index 3a538b5..c766db6 100644 --- a/doc/intro.cli +++ b/doc/intro.cli @@ -1428,9 +1428,9 @@ It also makes sense to have the same default configuration and use identical configuration names in all the projects.| The last step is to move the desired functionality from \c{hello} to -\c{libhello} and at the same add a dependency on \c{libhello}, just as we did -earlier (add a \c{depends} entry to \c{manifest}, then import the library in -\c{buildfile}, and so on). One interesting question is what to put as a +\c{libhello} and at the same time add a dependency on \c{libhello}, just as we +did earlier (add a \c{depends} entry to \c{manifest}, then import the library +in \c{buildfile}, and so on). One interesting question is what to put as a prerequisite repository in \c{repositories.manifest}. Our own setup will work even if we don't put anything there \- the dependency will be automatically resolved to our local version of \c{libhello} since we have initialized it in |