aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/utility.cxx
AgeCommit message (Collapse)AuthorFilesLines
2022-11-08Tighten args const-ness in the run*() function familyBoris Kolpackov1-5/+5
2022-11-08Rework header dependency extraction with diagnostics bufferingBoris Kolpackov1-2/+2
2022-11-08More work on child process diagnostics bufferingBoris Kolpackov1-27/+282
2022-10-27Initial work on child process diagnostics bufferingBoris Kolpackov1-0/+2
Currently this is implemented for C/C++ compile and link rules.
2022-04-21Work around bogus -Wrestrict in GCC 12 (GCC bug #105329)Boris Kolpackov1-2/+2
2022-02-21Factor process-wide initialization to init_process() functionBoris Kolpackov1-0/+87
2022-02-02Redo diagnostics without operator<< in namespace stdBoris Kolpackov1-7/+2
2021-07-06Clear errno before calling strto*() functionsBoris Kolpackov1-0/+1
2020-11-06Add support for test timeoutsKaren Arutyunov1-0/+18
2020-05-27Initial support for ad hoc recipes (still work in progress)Boris Kolpackov1-0/+4
2020-04-07Pass LC_ALL=C when extracting locale-dependent information on POSIXBoris Kolpackov1-1/+1
2020-02-12Adapt to renaming butl::fdnull() to fdopen_null()Karen Arutyunov1-2/+2
2020-02-12Add builtins support for $process.run*() functionsKaren Arutyunov1-0/+25
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-27Improve process run_*() APIBoris Kolpackov1-5/+23
2019-11-15Use path_name_view in location and path_name_value in location_valueKaren Arutyunov1-3/+3
2019-11-14Make use of butl::to_stream(ostream, path, bool)Karen Arutyunov1-3/+4
2019-11-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov1-3/+2
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov1-32/+8
2019-11-04Add support for configuration exporting and importingBoris Kolpackov1-1/+31
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-18Add ability to specify "compiler mode" options as part of config.{c,cxx}Boris Kolpackov1-6/+10
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/+9
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-3/+3
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-08Redo bin pattern as PATH-like search paths rather than fallback directoryBoris Kolpackov1-10/+12
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-8/+8
2019-08-28Redo build_installed without requiring linking whole archiveBoris Kolpackov1-2/+0
2019-08-26Implement auto-import of development build2 buildBoris Kolpackov1-0/+2
2019-08-23Introduce notion of build contextBoris Kolpackov1-5/+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-21Cleanup context.hxx and its usageBoris Kolpackov1-0/+1
2019-08-21Implement dynamic loading of build system modulesBoris Kolpackov1-0/+5
2019-08-17Add support for default options filesKaren Arutyunov1-2/+8
2019-08-07Improve deadlock diagnostics (suppress stack trace, reword)Boris Kolpackov1-3/+6
2019-07-01Split build system into library and driverBoris Kolpackov1-0/+517