aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/bin/init.cxx
AgeCommit message (Collapse)AuthorFilesLines
2020-08-24Use representation when passing target_triplet as hintBoris Kolpackov1-1/+1
2020-06-18Complete NetBSD compatibilityBoris Kolpackov1-1/+1
2020-06-18Add NetBSD compatibilitymagenbluten1-1/+1
2020-06-16Add $bin.link_member() functionBoris Kolpackov1-2/+14
Given a linker output target type ("exe", "lib[as]", or "libu[eas]") return the target type of lib{} group member ("liba" or "libs") that will be picked when linking a lib{} group to this target type.
2020-06-02Add process_path_ex with program stable name and checksumBoris Kolpackov1-14/+16
2020-05-22Make template definition available in all translation units where usedBoris Kolpackov1-1/+1
We were trying to be clever but GCC 10's IPA-SRA optimization didn't like it.
2020-04-27Rework tool importation along with cli moduleBoris Kolpackov1-1/+1
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-03-31Fix bug in install_path() call (Windows-specific)Boris Kolpackov1-2/+6
2020-03-31Switch to project variable visibility by defaultBoris Kolpackov1-30/+27
2020-03-17Rework config::{omitted,required,optional}() into unified config_lookup()Boris Kolpackov1-72/+76
2020-03-11Minor config variable lookup cleanupsBoris Kolpackov1-4/+4
2020-02-24Extract version for lld-linkBoris Kolpackov1-4/+33
2020-02-07Drop copyright notice from source codeKaren Arutyunov1-1/+0
2020-01-29Rename module_base to module, redo module boot/init argument passingBoris Kolpackov1-30/+21
2020-01-28Use scope::var_pool()Boris Kolpackov1-12/+12
2020-01-28Use scope::insert_rule()Boris Kolpackov1-2/+2
2020-01-27See through lib{} group during distBoris Kolpackov1-1/+6
2020-01-27Improve module loading APIBoris Kolpackov1-26/+12
2019-11-12Infra work for customizable config var persistence (config.config.persist)Boris Kolpackov1-1/+1
2019-10-29Add support for specifying custom load prefix and version clean patternsBoris Kolpackov1-5/+14
2019-10-09Prepend pattern search paths to PATH when running binutilsBoris Kolpackov1-24/+1
This way any dependent tools (such as mt.exe that is invoked by link.exe) are first search for in there.
2019-10-09Work around issue with undefined symbol to constexpr constBoris Kolpackov1-1/+1
Note that this only manifests itself when compiling in the C++14 mode (e.g., during bootstrap or with an older compiler like GCC 4.9).
2019-10-08Redo bin pattern as PATH-like search paths rather than fallback directoryBoris Kolpackov1-23/+39
Also, unlike the fallback directory, the search paths are searched first rather than last.
2019-08-28Move bin build system module to separate libraryKaren Arutyunov1-0/+963