aboutsummaryrefslogtreecommitdiff
path: root/libbuild2
AgeCommit message (Collapse)AuthorFilesLines
2019-11-05Cosmetic changeBoris Kolpackov1-2/+2
2019-11-05Recognize latest C (2x) and C++ (2b) standardsBoris Kolpackov2-16/+23
2019-11-05Fix function call diagnostics to use diag_frameBoris Kolpackov2-24/+19
2019-11-04Add support for ~host special configuration name in config.importBoris Kolpackov3-8/+72
This is the "default host configuration" that corresponds to how the build system itself was built. For example: $ b create: tools/,cc config.import=~host
2019-11-04Add $config.export() functionBoris Kolpackov11-85/+174
This is similar to the config.export variable functionality except it can be called from within buildfiles. Note that this function can only be used during configure unless the config module creation was forced for other meta-operations with config.module=true in bootstrap.build.
2019-11-04Add support for configuration exporting and importingBoris Kolpackov16-175/+415
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-31Update comment on Apple Clang to vanilla Clang version mappingBoris Kolpackov1-15/+14
2019-10-31Fix crashing on unhandled invalid_path thrown by parser::parse_include()Karen Arutyunov1-17/+36
2019-10-29Add forward declaration header for build state typesBoris Kolpackov25-101/+97
2019-10-29Regularize and make accessible install/uninstall primitivesBoris Kolpackov2-36/+70
2019-10-29Add support for specifying custom load prefix and version clean patternsBoris Kolpackov2-10/+24
2019-10-29Tighten up versioned libraries clean patternsBoris Kolpackov2-73/+128
2019-10-25Fix maybe used uninitialized warningBoris Kolpackov1-1/+1
2019-10-25Fix inconsistent loaded_modules_lock declarationBoris Kolpackov1-1/+1
2019-10-25Expand context commentBoris Kolpackov1-2/+13
2019-10-25Add --silent, remap verbosity 0 to 1 while building modules unless silentBoris Kolpackov4-4/+31
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-23Expand commentBoris Kolpackov1-2/+2
2019-10-23Un-tune scheduler when building build system modulesBoris Kolpackov8-100/+167
2019-10-22Handle invalid_argument when constructing build system module project nameBoris Kolpackov1-1/+9
2019-10-22Implement loaded_modules state lockingBoris Kolpackov4-2/+62
This would be necessary if someone runs two parallel top-level contexts.
2019-10-22Minor fixesBoris Kolpackov2-2/+2
2019-10-22Add load_builtin_module()Boris Kolpackov2-0/+15
2019-10-22Rename global_mutex_shards to global_mutexesBoris Kolpackov8-20/+24
2019-10-22Add tracing to find_module() and import_module()Boris Kolpackov1-1/+20
2019-10-22Move global mutex shards to contextBoris Kolpackov11-42/+68
2019-10-21Work around LLD bug #43744Boris Kolpackov1-0/+23
2019-10-21Build thin archives for utility libraries if using llvm-libBoris Kolpackov1-0/+13
2019-10-21Add more information on C and C++ compiler mode options to manualBoris Kolpackov3-0/+6
2019-10-19Recognize various LLD drivers as well as LLVM lib and rcBoris Kolpackov2-24/+94
2019-10-19Add find_stem() utility functionBoris Kolpackov3-23/+39
2019-10-18Add $quote() function for quoting valuesBoris Kolpackov3-8/+59
This can be useful if we want to pass a value on the command line, for example, in a testscript: $* config.cxx=$quote($recall($cxx.path) $cxx.mode, true)
2019-10-18Add ability to specify "compiler mode" options as part of config.{c,cxx}Boris Kolpackov15-235/+402
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-18Optimize config::required() to move default value if possibleBoris Kolpackov2-6/+9
2019-10-17Derive msvc_cpu from cl.exe signature rather than pathBoris Kolpackov1-41/+29
2019-10-17Add support for VS search by cl.exe path in find_msvc()Karen Arutyunov1-48/+93
2019-10-17Add temporary fallback to x64 in find_msvc()Boris Kolpackov1-3/+8
2019-10-16Make target CPU part of msvc_info structBoris Kolpackov1-18/+21
2019-10-16Try to find MSVC installation for absolute cl.exe pathsBoris Kolpackov6-53/+118
Without this extra logic recursive invocation of the build system (e.g., in tests) will fail to obtain the full environment.
2019-10-15Remove no longer used lambda captureBoris Kolpackov1-4/+1
2019-10-14Fix bug in guess_msvc()Karen Arutyunov1-1/+1
2019-10-14Add missing #ifndef BUILD2_BOOTSTRAP around find_msvc() callBoris Kolpackov1-0/+2
2019-10-14Implement MSVC installation discovery for version 15 (2017) and laterKaren Arutyunov12-202/+1715
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-11Various fixes to make clang-cl workBoris Kolpackov2-31/+45
Note that clang-cl's /showInclude output differs from cl's in the face of missing headers. In particular, it does not issue C1083 that we expect. As a result, this part of clang-cl's support is currently non-functional (the rest seems to work, however).
2019-10-11Switch clang-apple to primary/variant version setupBoris Kolpackov3-39/+60
2019-10-11Add support for clang-clBoris Kolpackov6-160/+319
The compiler type is `msvc`, variant `clang`.
2019-10-10Add %VCINSTALLDIR%\Tools\Llvm\bin as fallback search directory for ClangBoris Kolpackov1-6/+28
2019-10-09Prepend pattern search paths to PATH when running binutilsBoris Kolpackov5-48/+139
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-08Extend /LIBPATH handling to win32-msvc target systemBoris Kolpackov2-2/+4
2019-10-08Pass MSVC and Platform SDK bin\ directories as binutils search pathsBoris Kolpackov1-16/+39
generated by cgit v1.1 at 2024-11-05 19:09:32 +0000