aboutsummaryrefslogtreecommitdiff
path: root/doc/manual.cli
AgeCommit message (Collapse)AuthorFilesLines
2020-07-02Document private installation subdirectory mechanismBoris Kolpackov1-5/+76
A private installation subdirectory can be used to hide the implementation details of a project. This is primarily useful when installing an executable that depends on a bunch of libraries into a shared location, such as /usr/local/.
2020-06-29Add config.install.share variableBoris Kolpackov1-3/+4
Its default value is data_root/share/ and it is now used as a common root for config.install.{data,doc,man} variables.
2020-06-29Add legal{} target type and config.install.legal variableBoris Kolpackov1-0/+1
This allows separation of legal files (LICENSE, AUTHORS, etc) from other documentation. For example: ./: ... doc{README} legal{LICENSE} $ b install ... config.install.legal=/usr/share/licenses/hello/
2020-06-29Use buildfile{} instead of build{} for target typeBoris Kolpackov1-1/+1
This feels like an oversight from transitioning to full names, like testscript{}, etc.
2020-06-26Add note to manualBoris Kolpackov1-4/+21
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-10/+13
Specifically, now config.<tool> (like config.cli) is handled by the import machinery (it is like a shorter alias for config.import.<tool>.<tool>.exe that we already had). And the cli module now uses that instead of custom logic. This also adds support for uniform tool metadata extraction that is handled by the import machinery. As a result, a tool that follows the "build2 way" can be imported with metadata by the buildfile and/or corresponding module without any tool-specific code or brittleness associated with parsing --version or similar outputs. See the cli tool/module for details. Finally, two new flavors of the import directive are now supported: import! triggers immediate importation skipping any rule-specific logic while import? is optional import (analogous to using?). Note that optional import is always immediate. There is also the import-specific metadata attribute which can be specified for these two import flavors in order to trigger metadata importation. For example: import? [metadata] cli = cli%exe{cli} if ($cli != [null]) info "cli version $($cli:cli.version)"
2020-04-08Proofreading fixes to manualBoris Kolpackov1-11/+11
2020-04-08Document project-specific configuration supportBoris Kolpackov1-18/+775
2020-03-09Document UTF-8 encoding for buildfiles and testscriptsBoris Kolpackov1-1/+4
2020-02-13Adjust documentation to change to bdep-new binless sub-optionBoris Kolpackov1-1/+1
2020-02-13Minor documentation consistency cleanupBoris Kolpackov1-2/+2
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-02-04Add note to manual on specifying search paths in compiler modeBoris Kolpackov1-0/+13
2019-11-15Test and document wildcard character escapingBoris Kolpackov1-14/+40
Also document the new bracket expression ([...]) wildcard support.
2019-11-01Add note to manual on absolute cl.exe pathsBoris Kolpackov1-6/+12
2019-10-29Update manual regarding platform-specific version supportBoris Kolpackov1-1/+1
2019-10-22Add documentation for MSVC and Clang compiler toolchainsBoris Kolpackov1-3/+163
2019-10-21Add more information on C and C++ compiler mode options to manualBoris Kolpackov1-4/+164
2019-10-21Note compiler mode options in manualBoris Kolpackov1-0/+11
2019-10-17Update Visual Studio instructions in manualBoris Kolpackov1-7/+18
2019-10-16Minor documentation tweakBoris Kolpackov1-1/+1
2019-10-10Fix bug in documentationBoris Kolpackov1-5/+5
2019-10-01Minor documentation fixesBoris Kolpackov1-4/+4
2019-09-30Document pattern matching support (switch)Boris Kolpackov1-8/+175
2019-07-22Mention LDLIBS in addition to LIBS as analogous to *.libsBoris Kolpackov1-3/+3
2019-06-21Add support for [config.]{cc,c,cxx}.aoptions (archive options)Boris Kolpackov1-3/+16
In particular, this can be used to suppress lib.exe warnings, for example: cc.aoptions += /IGNORE:4221
2019-06-08Minor documentation updateBoris Kolpackov1-1/+1
2019-06-08Fix misleading in module documentationBoris Kolpackov1-3/+3
2019-05-24Adapt to increasing standard version major, minor, and patch max values up ↵Karen Arutyunov1-21/+21
to 99999
2019-05-17Update manual with README.md generation by bdep-newBoris Kolpackov1-9/+11
2019-05-16Document generalized variable assignment blocksBoris Kolpackov1-5/+30
2019-03-07Add support for alternative build file/directory naming schemeBoris Kolpackov1-0/+35
Now the build/*.build, buildfile, and .buildignore filesystem entries in a project can alternatively (but consistently) be called build2/*.build2, build2file, and .build2ignore. See a note at the beginning of the Project Structure section in the manual for details (motivation, restrictions, etc).
2019-01-16Update copyright yearKaren Arutyunov1-1/+1
2018-11-30Various documentation updates, section on debugging build issuesBoris Kolpackov1-96/+595
2018-10-18Add note to manual on creating binless libraries with bdep-newBoris Kolpackov1-1/+11
2018-10-17Fix few bugs in manualBoris Kolpackov1-9/+10
2018-10-04Add note on C++ module interface unit naming to manualBoris Kolpackov1-1/+8
2018-09-16Fix bug in manualBoris Kolpackov1-1/+1
2018-09-10Documentation fixes and improvementsBoris Kolpackov1-158/+167
2018-09-08More documentation fixesBoris Kolpackov1-1/+1
2018-09-08Documentation fixBoris Kolpackov1-1/+1
2018-09-08Documentation fixesBoris Kolpackov1-466/+503
2018-09-07Explain subprojects and amalgamation in manualBoris Kolpackov1-5/+245
2018-09-06Explain unit test support implementation in manualBoris Kolpackov1-4/+180
2018-09-05Documentation fixesBoris Kolpackov1-141/+170
2018-09-05Add note on header-only/binless libraries in manualBoris Kolpackov1-0/+14
2018-09-04Document .buildignoreBoris Kolpackov1-3/+4
2018-09-04Rename .test/test{} to .testscript/testscript{}Boris Kolpackov1-1/+1
2018-09-03Write introduction (still WIP)Boris Kolpackov1-22/+3063
2018-08-09Add support for name patterns without wildcard charactersBoris Kolpackov1-9/+11
In particular, this allows the "if-exists" specification of prerequisites, for example: for t: $tests exe{$t}: cxx{$t} test{+$t}
generated by cgit v1.1 at 2024-11-16 05:12:25 +0000