aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2022-07-26Minor additions to manualBoris Kolpackov1-9/+24
2022-07-25Use 'C:\Program Files' instead of 'C:\Program Files (x86)' in documentationKaren Arutyunov1-1/+1
2022-07-25Minor tweaks to NEWS fileBoris Kolpackov1-7/+7
2022-07-25Update NEWS fileBoris Kolpackov1-0/+223
2022-07-25Fix typo in commentBoris Kolpackov1-1/+1
2022-07-21Make LLVM tools (ar, lld, etc) detection more robustBoris Kolpackov1-6/+18
2022-07-21Use bundle scope when deciding whether project is being distributedBoris Kolpackov1-2/+3
2022-07-21Map Apple Clang 13.1.6 to vanilla Clang 12.0.0Boris Kolpackov1-18/+20
2022-07-21Fix bug in common .pc file generation logic (GitHub issue #198)Boris Kolpackov1-1/+1
2022-07-21Add link to HOWTO entry in conditional dependency declaration warningBoris Kolpackov1-1/+3
2022-07-21Don't issue conditional dependency declaration warning for imported projectsBoris Kolpackov3-9/+46
2022-07-20Fix bug in cc::pkconfig_save()Boris Kolpackov1-1/+1
2022-07-20Tweak diagnosticsBoris Kolpackov1-1/+1
2022-07-20Adjust conditional dependency declaration warning logicBoris Kolpackov2-13/+19
Now instead of ignoring imported stuff (which turned out to be racy), we only consider conditions up to the include boundary. The thinking here is that an included (but not sourced) buildfile is a standalone entity (e.g., imported project but also could be just a side-included buildfile). Note that unfortunately we will still be issuing warnings in imported projects since there is no straightforward way to know what is being distributed and what is not while parsing.
2022-07-20Adjust to match libpkg-config interface/semantics changesBoris Kolpackov1-5/+25
2022-07-19Warn about conditional dependency declarations during distributionBoris Kolpackov2-0/+51
2022-07-19Fix bug in target::matched()Boris Kolpackov2-7/+7
2022-07-18Add few references to manualBoris Kolpackov1-3/+5
2022-07-17Map VC 17 to runtime version 14.3Boris Kolpackov2-3/+6
2022-07-13Work around "storing address of local variable" warning issued by GCC 12Boris Kolpackov1-1/+1
The warning is issued inside the target_lock's move constructor so we sidestep the whole thing by avoiding the call to the move constructor.
2022-07-13In manual adjust link to renamed section in bpkg manualKaren Arutyunov1-2/+1
2022-07-12Use -pthread instead of -lpthread in bootstrap scripts/makefileBoris Kolpackov2-3/+3
2022-07-11Update config submodule (config.guess/config.sub scripts)Boris Kolpackov1-0/+0
2022-07-08Fix some tests to match canned command line semanticsKaren Arutyunov4-4/+4
2022-07-08Fix script::parser::need_cmdline_relex()Karen Arutyunov1-1/+1
2022-07-08Update manual with package manager configuration negotiation informationBoris Kolpackov1-3/+89
2022-07-07Use new cmdline type for canned command lines in {Build,Test}scriptBoris Kolpackov18-108/+443
2022-07-07Fix incorrect function family assignment for $target.process_path()Boris Kolpackov1-1/+1
2022-07-05Drop unused lambda captureBoris Kolpackov1-2/+1
2022-07-05Switch to using libpkg-config instead of libpkgconf by defaultBoris Kolpackov6-9/+286
The use of (now deprecated) libpkgconf is still possible by setting config.build2.libpkgconf to true. Note that libpkgconf is known to have issues on Windows and Mac OS so this should only be used on Linux and maybe BSDs. Also note that we will only keep this until upstream (again) breaks backwards compatibility at which point we will drop this support.
2022-07-05Recognize special .for_install variable suffix in library user metadataBoris Kolpackov2-26/+95
2022-07-04Work around VC16 issueBoris Kolpackov1-0/+2
2022-07-04Factor libpkgconf-based pkgconfig implementation to separate source fileBoris Kolpackov3-461/+499
2022-07-02Minor cleanups in class pkgconf implementationBoris Kolpackov1-22/+32
2022-07-02Add note on version we save in pkg-config filesBoris Kolpackov1-0/+14
2022-07-01Regenerate options parsing filesKaren Arutyunov4-47/+162
2022-07-01Ignore Provides when loading pkg-config informationBoris Kolpackov1-0/+1
Without this flag, on encountering an unknown package, libpkgconf will load *all* pkg-config files it can find in order to see if any of them provide it.
2022-06-29Work around MSVC 14.3 issuesBoris Kolpackov2-3/+3
2022-06-29Make sure we generate common pkg-config file for only liba{}/libs{}Boris Kolpackov5-8/+44
2022-06-29Save cc.type in pkg-config filesBoris Kolpackov2-5/+30
2022-06-29Rework pkg-config variable naming, use build2.metadata as general indicatorBoris Kolpackov3-183/+233
2022-06-28Complete support for saving/loading library metadata to/from pkg-config filesBoris Kolpackov5-167/+308
2022-06-28Add support for querying out-qualified target-specific variablesBoris Kolpackov9-43/+79
2022-06-28Handle out-qualified prerequisitesBoris Kolpackov1-6/+20
2022-06-28Add support for rule-specific import phase 2Boris Kolpackov6-41/+184
For example: import! [metadata, rule_hint=cxx.link] lib = libhello%lib{hello}
2022-06-24Allow ad hoc rules not to list targets that are updated during matchBoris Kolpackov10-37/+136
For example, this allows a Qt moc rule not to list generated headers from libQtCore since they are pre-generated by the library.
2022-06-24Make libul{} rule match without hintBoris Kolpackov3-31/+11
In the end, the extra jumping through the hoops doesn't justify the extra safety we gain. The only plausible accidental mistake is making libul{} a dependency of ./ but then we don't prevent the same for libue{}, which also doesn't make much sense. Though, the consequences of doing this for libul{} could be more severe, like messed up for-install'ness. Oh, well, I guess people will just have to pay attention (this could be a good check for the linter we've been thinking about).
2022-06-24Add ability to control -I translation in $x.lib_poptions()Boris Kolpackov3-11/+22
2022-06-24Add ability to get common interface options via $x.lib_poptions()Boris Kolpackov8-66/+169
Specifically, the output target type may now be omitted for utility libraries (libul{} and libu[eas]{}). In this case, only "common interface" options will be returned for lib{} dependencies. This is primarily useful for obtaining poptions to be passed to tools other than C/C++ compilers (for example, Qt moc).
2022-06-24Match rule to libul{} with explicit bin.metadata hintBoris Kolpackov5-11/+110
This rule picks, matches, and unmatches (if possible) a member for the purpose of making its metadata (for example, library's poptions, if it's one of the cc libraries) available.
generated by cgit v1.1 at 2024-11-14 20:03:06 +0000