aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/utility.hxx
AgeCommit message (Collapse)AuthorFilesLines
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.
2019-10-09Prepend pattern search paths to PATH when running binutilsBoris Kolpackov1-15/+19
This way any dependent tools (such as mt.exe that is invoked by link.exe) are first search for in there.
2019-10-08Redo bin pattern as PATH-like search paths rather than fallback directoryBoris Kolpackov1-2/+15
Also, unlike the fallback directory, the search paths are searched first rather than last.
2019-10-01Adapt to renaming butl::casecmp() to icasecmp()Karen Arutyunov1-3/+3
2019-08-30Make build_installed constBoris Kolpackov1-3/+2
2019-08-28Redo build_installed without requiring linking whole archiveBoris Kolpackov1-2/+0
2019-08-26Implement auto-import of development build2 buildBoris Kolpackov1-0/+6
2019-08-23Introduce notion of build contextBoris Kolpackov1-4/+3
All non-const global state is now in class context and we can now have multiple independent builds going on at the same time.
2019-08-21Implement dynamic loading of build system modulesBoris Kolpackov1-1/+5
2019-08-07Improve deadlock diagnostics (suppress stack trace, reword)Boris Kolpackov1-1/+7
2019-08-01Fix linkage failure due to inline functions defined in ↵Karen Arutyunov1-1/+1
libbuild2/algorithm.ixx and referred from libbuild2/target.txx
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+671
generated by cgit v1.1 at 2024-11-28 03:16:28 +0000