aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/utility.hxx
AgeCommit message (Collapse)AuthorFilesLines
2024-12-06Adapt to renaming of some butl::{ucase,lcase,sanitize_identifier}() function ↵Karen Arutyunov1-0/+3
overloads
2024-07-28Factor out and generalize/extend to_stream_quoted(string)Boris Kolpackov1-0/+33
2024-06-07Use combined -L option form for extra system search pathsBoris Kolpackov1-8/+20
The split one was just too much of an eye-sore in the logs.
2024-02-12Move to_string(uint64_t,base,width) to utility, use everywhereBoris Kolpackov1-1/+7
2023-11-22Add support for `import std` in Clang 17 or later with libc++Boris Kolpackov1-2/+4
2023-08-29Add diagnostics color support on Windows (GH issue #312)Boris Kolpackov1-4/+2
Note that currently this has to be enabled with an explicit --diag-color option. In the future the plan is to enable it by default if supported.
2023-06-08Add support for buildfile importationBoris Kolpackov1-2/+4
2023-04-04Add support for installation filtering (GH issue #147)Boris Kolpackov1-0/+1
2023-01-24Add std::back_inserter() to utility.hxxBoris Kolpackov1-1/+2
2022-12-08Add --[no]diag-color options (infrastructure only)Boris Kolpackov1-1/+12
2022-11-23Rework diag_buffer interface to facilitate correct destruction orderBoris Kolpackov1-142/+11
2022-11-14Make $process.run() print builtin command line on error and verbosity level >= 3Karen Arutyunov1-0/+12
2022-11-08Restore original error/ignore_exit semantics in run<>() overloadsBoris Kolpackov1-21/+16
2022-11-08Make process exit diagnostics consistentBoris Kolpackov1-55/+100
In particular, we now always print error message on non-0 exit except in cases where such exit is ignored.
2022-11-08Tighten args const-ness in the run*() function familyBoris Kolpackov1-31/+35
2022-11-08More work on child process diagnostics bufferingBoris Kolpackov1-127/+404
2022-10-13Add support for 'for' loop second (... | for x) and third (for x <...) forms ↵Karen Arutyunov1-0/+1
in script
2022-09-22Add support for hex notation for uint64 typeBoris Kolpackov1-0/+1
Specifically, now we can do: x = [uint64] 0x0000ffff cxx.poptions += "-DOFFSET=$x" # -DOFFSET=65535 cxx.poptions += "-DOFFSET=$string($x, 16)" # -DOFFSET=0xffff cxx.poptions += "-DOFFSET=$string($x, 16, 8)" # -DOFFSET=0x0000ffff Note that there is no hex notation support for the int64 (signed) type.
2022-02-21Factor process-wide initialization to init_process() functionBoris Kolpackov1-0/+14
2021-10-01Add notion of internal scope, translate external -I to -isystem or equivalentBoris Kolpackov1-0/+20
2021-09-28Adapt to libbutl headers extension change from .mxx to .hxxKaren Arutyunov1-6/+6
2021-08-13Cache git status results in version moduleBoris Kolpackov1-33/+0
2021-04-22Add another hash/save_environment() overloadBoris Kolpackov1-0/+6
2021-04-20Track changes to environment in cc rulesBoris Kolpackov1-0/+29
2021-04-02Add support for propagating project environmentBoris Kolpackov1-2/+1
2021-01-30Add std::{map, multimap} to types.hxxBoris Kolpackov1-2/+1
Seeing that std::map is becoming a common Buildfile variable type.
2021-01-30Rework include translation supportBoris Kolpackov1-0/+5
See the config.cxx.translate_include variable documentation in cxx/init.cxx for details.
2020-12-15Cache more results of executing programs (compilers, etc)Boris Kolpackov1-2/+34
2020-11-30Add more default argument values to run_start()Boris Kolpackov1-13/+13
2020-11-23Add $string.lcase() and $string.ucase() functionsKaren Arutyunov1-0/+1
2020-11-06Add support for test timeoutsKaren Arutyunov1-0/+7
2020-08-13Add few more run() overloadsBoris Kolpackov1-2/+17
2020-08-12Add iterator-based versions of find_option{,_prefix}Matthew Krupcale1-3/+13
This allows one to use all of the properties of iterators to manipulate the found option.
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-0/+1
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-1/+3
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-02-12Adapt to renaming butl::fdnull() to fdopen_null()Karen Arutyunov1-1/+1
2020-02-12Add builtins support for $process.run*() functionsKaren Arutyunov1-0/+8
2020-02-12Add convenience run_start() overloadBoris Kolpackov1-1/+26
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-27Improve process run_*() APIBoris Kolpackov1-11/+25
2019-11-14Make use of butl::to_stream(ostream, path, bool)Karen Arutyunov1-1/+2
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-11/+3
2019-11-05Add support for automatic importing of libbuild2 of installed caseBoris Kolpackov1-1/+3
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-0/+13
The new config.export variable specifies the alternative file to write the configuration to as part of the configure meta-operation. For example: $ b configure: proj/ config.export=proj-config.build The config.export value "applies" only to the projects on whose root scope it is specified or if it is a global override (the latter is a bit iffy but we allow it, for example, to dump everything to stdout). This means that in order to save a subproject's configuration we will have to use a scope-specific override (since the default will apply to the outermost amalgamation). For example: $ b configure: subproj/ subproj/config.export=.../subproj-config.build This could be somewhat unnatural but then it will be the amalgamation whose configuration we normally want to export. The new config.import variable specifies additional configuration files to be loaded after the project's default config.build, if any. For example: $ b create: cfg/,cc config.import=my-config.build Similar to config.export, the config.import value "applies" only to the project on whose root scope it is specified or if it is a global override. This allows the use of the standard override "positioning" machinery (i.e., where the override applies) to decide where the extra configuration files are loaded. The resulting semantics is quite natural and consistent with command line variable overrides, for example: $ b config.import=.../config.build # outermost amalgamation $ b ./config.import=.../config.build # this project $ b !config.import=.../config.build # every project Both config.export and config.import recognize the special `-` file name as an instruction to write/read to/from stdout/stdin, respectively. For example: $ b configure: src-prj/ config.export=- | b configure: dst-prj/ config.import=-
2019-10-29Add forward declaration header for build state typesBoris Kolpackov1-7/+1
2019-10-25Add --silent, remap verbosity 0 to 1 while building modules unless silentBoris Kolpackov1-1/+5
Failed that, we may have long periods of seemingly nothing happening (e.g., during implicit bdep sync) while we quietly update the module, which may look like things have hung up.
2019-10-19Add find_stem() utility functionBoris Kolpackov1-0/+14
2019-10-18Add ability to specify "compiler mode" options as part of config.{c,cxx}Boris Kolpackov1-10/+19
Such options are (normally) not overridden by buildfiles and are passed last (after cc.coptions and {c,cxx}.coptions) in the resulting command lines. They are also cross-hinted between config.c and config.cxx. For example: $ b config.cxx="g++ -m64"
2019-10-16Try to find MSVC installation for absolute cl.exe pathsBoris Kolpackov1-1/+4
Without this extra logic recursive invocation of the build system (e.g., in tests) will fail to obtain the full environment.
2019-10-14Implement MSVC installation discovery for version 15 (2017) and laterKaren Arutyunov1-9/+9
In particular, this removes the requirement to build from the Visual Studio command prompt. Note that since MSVC compiler binaries are target-specific (i.e., there are no -m32/-m64 options nor something like /MACHINE), in this case we default to a 64-bit build (a 32-bit build can still be achieved by running from a suitable command prompt). Finally, this mechanism is also used to find Clang bundled with MSVC.
generated by cgit v1.1 at 2024-12-22 07:40:49 +0000