aboutsummaryrefslogtreecommitdiff
path: root/libbuild2
AgeCommit message (Collapse)AuthorFilesLines
2019-11-29Reorder {cc,c/cxx}.{poptions,loptions}Boris Kolpackov5-12/+23
Now it is c/cxx first followed by cc which is the reverse order of coptions since the header/library search paths are examined in the order specified (in contrast to the "last value wins" semantics that we assume for coptions).
2019-11-26Rename executable's .lib/.exp to avoid clashes with librariesBoris Kolpackov2-32/+44
Failed that we cannot have an executable and a library with the same name and in the same directory (their .lib's will clash).
2019-11-22Filter out config.install.chroot from default host configurationBoris Kolpackov1-1/+7
2019-11-21Change version to 0.13.0-a.0.zBoris Kolpackov1-1/+1
2019-11-19Release version 0.12.0v0.12.0Boris Kolpackov1-1/+1
2019-11-18Add couple of sanity checksBoris Kolpackov4-6/+14
2019-11-16Revert temporary use of c++17 mode in GCC modules supportBoris Kolpackov1-4/+0
2019-11-16Handle dry-run mode in backlinking implementationBoris Kolpackov2-12/+27
2019-11-15Use path_name_view in location and path_name_value in location_valueKaren Arutyunov10-35/+125
2019-11-15Test and document wildcard character escapingBoris Kolpackov1-1/+1
Also document the new bracket expression ([...]) wildcard support.
2019-11-15Generalize attributes to be comma-separated with arbitrary valuesBoris Kolpackov8-71/+119
Before: x = [string null] After: x = [string, null]
2019-11-15Improve {}-imbalance diagnostics in cc::parser and make it warningBoris Kolpackov3-10/+33
2019-11-15Fix bug in cc::parser location storageBoris Kolpackov4-5/+32
2019-11-14Cleanup attribute parsing codeBoris Kolpackov4-54/+37
2019-11-14Require attributes to be separated from words and similar on RHSBoris Kolpackov1-2/+19
2019-11-14Adjust deadlock diagnostics to reflect its fuzzy natureBoris Kolpackov1-3/+2
2019-11-14Tighten up attribute recognition during parsingBoris Kolpackov9-190/+286
Now it should be possible to use `[]` for wildcard patterns, for example: foo = foo.[hit]xx Note that a leading bracket expression will still be recognized as attributes and escaping or quoting it will inhibit pattern matching. To resolve this case we need to specify an empty attribute list: foo = [] [abc]-foo.cxx
2019-11-14Make use of butl::to_stream(ostream, path, bool)Karen Arutyunov6-13/+19
2019-11-13Increase deadlock detection timeoutBoris Kolpackov1-1/+1
2019-11-13Use path_name in cc::lexer classKaren Arutyunov15-64/+119
2019-11-13Implement config.config.persist logicBoris Kolpackov4-78/+193
Note that the inherited value part is documented but is not yet fully implemented.
2019-11-12Infra work for customizable config var persistence (config.config.persist)Boris Kolpackov5-41/+75
2019-11-12Explicitly load bundled module buildfiles to "use" their importsBoris Kolpackov1-1/+9
2019-11-12Add support for vector<pair<K, V>> variable valuesBoris Kolpackov4-2/+231
2019-11-12Rename config.{import,export} to config.config.{load,save}Boris Kolpackov5-48/+52
Also rename the $config.export() function to $config.save().
2019-11-12Rename config.module to config.config.moduleBoris Kolpackov2-12/+12
The old name was an accidental land-grab.
2019-11-11Change default for unused config.import.* variables from drop to keepBoris Kolpackov4-34/+94
2019-11-11Use path_name for `-` to stdin/stdout translationKaren Arutyunov19-89/+102
2019-11-08Use $regex.replace_lines() for default host config processingBoris Kolpackov1-5/+3
2019-11-08Add $regex.replace_lines() functionKaren Arutyunov1-2/+141
2019-11-08Redo Apple /usr/include detection using patternsBoris Kolpackov1-16/+8
This should cover XCode 11 where the symlinks are the other way around now (see homebrew-core issue #46393 for details).
2019-11-07Raise libcpp version in regex-related check to 9.0Karen Arutyunov1-1/+1
2019-11-07Add libbuild2/config/.gitignore with host-config.cxxBoris Kolpackov1-0/+1
2019-11-07Don't add $install.lib to module library search path if import.build2 is NULLBoris Kolpackov1-6/+21
2019-11-07Use `lib` prefix on MinGW when forming build system module library nameBoris Kolpackov1-1/+3
2019-11-07Initial work on path_name use for `-` to stdin/stdout translationBoris Kolpackov26-109/+112
2019-11-05Fix testsBoris Kolpackov1-3/+3
2019-11-05Add support for automatic importing of libbuild2 of installed caseBoris Kolpackov6-2/+37
2019-11-05Add support for supplying MSVC IFCPATH equivalentBoris Kolpackov7-13/+64
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
generated by cgit v1.1 at 2024-11-05 14:09:23 +0000