aboutsummaryrefslogtreecommitdiff
path: root/libbuild2
AgeCommit message (Collapse)AuthorFilesLines
2021-10-21Add build.progress global variable with --[no-]progress option valueBoris Kolpackov1-0/+11
2021-10-20Change to version 0.15.0-a.0.zBoris Kolpackov1-1/+1
2021-10-16Release version 0.14.0v0.14.0Boris Kolpackov1-1/+1
2021-10-16Skip regenerating .pc files during uninstallBoris Kolpackov2-2/+13
2021-10-16Improve info meta-operation not to print trailing spacesBoris Kolpackov1-8/+22
2021-10-15Allow explicit amalgamation by simple projectsBoris Kolpackov1-9/+8
2021-10-14Map latest to -std=c++2b from Clang 13, /std:c++20 from MSVC 16.11Boris Kolpackov1-17/+16
2021-10-14Use tidier pc and def names instead of generic gen for .pc and .def generationBoris Kolpackov2-2/+2
2021-10-14Disable re-parse of sole expansions in BuildscriptBoris Kolpackov6-12/+53
2021-10-14Pass along parse_names_result during script command parsingBoris Kolpackov4-28/+34
2021-10-14Add ability to detect sole expansion in parser::parse_names()Boris Kolpackov2-7/+15
2021-10-13Add --cwd|-t option to env pseudo-builtinKaren Arutyunov5-17/+87
2021-10-13Allow out-qualified names in $name.*() function familyBoris Kolpackov1-19/+36
2021-10-11Update Apple to vanilla Clang version mapping for Apple Clang 13.0.0Boris Kolpackov1-2/+5
2021-10-11Update bin.lib.version documentationBoris Kolpackov1-3/+0
2021-10-07Fix bug in internal scope logicBoris Kolpackov1-1/+1
2021-10-07Allow forcing installation of exe{} prerequisites of file targetsBoris Kolpackov3-3/+13
This can be achieved with prerequisite-specific install=true, for example: exe{foo}: exe{bar}: install = true # foo runs bar
2021-10-07Verify libraries and targets they are linked to a for-install-compatibleBoris Kolpackov10-11/+45
2021-10-07Minor install-related cleanupsBoris Kolpackov5-18/+43
2021-10-06Do not install exe{} prerequisites of file targetsBoris Kolpackov2-7/+18
2021-10-05Get rid of no longer necessary diagnosticsBoris Kolpackov1-38/+2
2021-10-04Document internal scope functionalityBoris Kolpackov1-1/+1
2021-10-04Optimize internal scope implementationBoris Kolpackov7-74/+68
2021-10-04Add support for treating specific libraries as always internalBoris Kolpackov5-8/+76
2021-10-01Add notion of internal scope, translate external -I to -isystem or equivalentBoris Kolpackov13-53/+552
2021-10-01Add missing return to scope::bundle_root()Boris Kolpackov1-0/+4
2021-09-29Add notion of bundle amalgamation scopeBoris Kolpackov5-0/+58
2021-09-28Adapt to libbutl headers extension change from .mxx to .hxxKaren Arutyunov34-84/+84
2021-09-24Fortify tests against NDEBUGKaren Arutyunov12-10/+36
2021-09-21Add more libraries to list of Windows system librariesBoris Kolpackov1-0/+5
2021-09-20Add more libraries to list of Windows system librariesBoris Kolpackov1-2/+10
2021-09-20Add support for disabling clean through target-prerequisite relationshipBoris Kolpackov7-37/+59
Our current semantics is to clean any prerequisites that are in the same project (root scope) as the target and it may seem more natural to rather only clean prerequisites that are in the same base scope. While it's often true for simple projects, in more complex cases it's not unusual to have common intermediate build results (object files, utility libraries, etc) reside in the parent and/or sibling directories. With such arrangements, cleaning only in base (even from the project root) may leave such intermediate build results laying around (since there is no reason to list them as prerequisites of any directory aliases). So we clean in the root scope by default but now any target-prerequisite relationship can be marked not to trigger a clean with the clean=false prerequisite-specific value.
2021-09-20Improve MSVC /showIncludes output handlingBoris Kolpackov1-13/+35
2021-09-20Add netapi32.lib to the list of Windows system librariesBoris Kolpackov1-0/+1
2021-09-20Assign pre-defined semantics to config.<project>.develop variablesBoris Kolpackov6-45/+123
This variable allows a project to distinguish between development and consumption builds. While normally there is no distinction between these two modes, sometimes a project may need to provide additional functionality during development. For example, a source code generator which uses its own generated code in its implementation may need to provide a bootstrap step from the pre-generated code. Normally, such a step is only needed during development. See "Project Configuration" in the manual for details.
2021-09-17Add fallback update-for-uninstall rule to global scopeBoris Kolpackov1-3/+6
2021-09-16Fix diagnostics corner case in perform_clean_extra()Boris Kolpackov1-5/+5
2021-09-16Fix over-tight assumption in standard operation match()Boris Kolpackov1-0/+1
2021-09-15Do variable lookup in ad hoc target groupsBoris Kolpackov4-22/+52
2021-09-14Add support for passing multiple names to $name.*() functionsBoris Kolpackov1-3/+49
2021-09-14Fix few issues with new config.install.scopeBoris Kolpackov1-32/+31
2021-09-14Impose 12K line count limit for regex matches in TestscriptBoris Kolpackov1-1/+15
2021-09-14Consistently install prerequisites from any scope by defaultBoris Kolpackov9-60/+131
It is also now possible to adjust this behavior with global config.install.scope override. Valid values for this variable are: project -- only from project strong -- from strong amalgamation weak -- from weak amalgamation global -- from all projects (default)
2021-09-13Impose 16KB line length limit for regex matches in TestscriptBoris Kolpackov1-1/+14
2021-09-09Handle Emscripten -pthread modeBoris Kolpackov1-0/+15
2021-09-08Adjust to renaming of butl::fdbuf to fdstreambufBoris Kolpackov2-4/+4
2021-09-02Don't consider aliasing in variable override lookupBoris Kolpackov3-6/+13
2021-09-02Add diag_frame around export stub loadingBoris Kolpackov1-2/+11
This gives the location of the importer in case the export stub issues any diagnostics.
2021-08-25Keep mtime check always enabled on WindowsBoris Kolpackov2-3/+5
Windows is known not to guarantee monotonically increasing mtimes.
2021-08-23Clear data in target::data() modifiersBoris Kolpackov1-2/+4
Currently we may end up resetting the data during the rule ambiguity detection.