summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2024-05-21Merge branch 'just-rules' into rulesKlaus Aehlig
2024-05-21["CC/auto", "config"] also honor shell-toolchain-provided PATHKlaus Aehlig
2024-05-15Use defaults as shell defaultsKlaus Aehlig
2024-05-15Update just reference to 1.4.0-alpha+20240515Klaus Aehlig
... to bring in the required defaults for the protobuf build.
2024-05-15Merge commit '4788e56dae6f6c1367084c064e62eb1b86d5583f' into rules/rules-ccKlaus Aehlig
2024-05-15Merge branch 'just-rules' into rulesKlaus Aehlig
2024-05-15Add shell defaultsKlaus Aehlig
So far, our rules, where depending on the shell, implicitly use "normal" defaults, hard-coded in the rules. Support configuring those in a default target, in the same way we do so for other tools, like the C compiler. In this, it is also possible to bring your own shell, built as a (compiled) target.
2024-05-13Update docsPaul Cristian Sarbu
2024-05-13Merge commit '1365efcaa32c7f4752e3caaa7e45c81b4ed7e3d8' into HEADPaul Cristian Sarbu
2024-05-13Merge commit '07924d28e81fe36ddb8e020552a7392fcf1227a0' into HEADPaul Cristian Sarbu
2024-05-13rules: Support staging debug artifacts in install-with-deps rulePaul Cristian Sarbu
The existing rule is extended to also stage source files if in debug mode, in order for a debugger to be able to find all needed symbols. Conflicting paths are allowed; in case of conflicts, the file from the closest target in the dependency chain wins.
2024-05-13install-with-deps result: Remove unneeded importsPaul Cristian Sarbu
2024-05-06Merge commit '81374a006d99c0a1276b9a46350a72ab48d2ded9' into HEADKlaus Aehlig
2024-05-06Merge commit '3b1d1e390b0de137a32bc5c4a8865e5417b3673b' into HEADKlaus Aehlig
2024-05-04["CC/pkgconfig", "system_library"]: honor ENV also for aux actionKlaus T. Aehlig
Our pkg config rule postprocesses the output of pkgconfig to add options -rpath where appropriate. This postprocessing, however, relies on (standard) tools from the environment, in particular cat(1). Therefore, the environment (in particular PATH) needs to be set properly for this auxilliary action.
2024-05-03Update derived filesOliver Reiche
2024-05-03Update to latest just releaseOliver Reiche
2024-05-03Add tests for object_only libraryOliver Reiche
2024-05-03Merge commit '5b23ba149a136c2669eda62be24deb0da5d31120' into rules/rules-ccOliver Reiche
2024-05-03Implement object_only libraryOliver Reiche
2024-04-29Update derived filesKlaus Aehlig
2024-04-29Merge branch 'just-rules' into rulesKlaus Aehlig
2024-04-29Merge subtree 'rules' into rules-ccKlaus Aehlig
2024-04-29["CC", "defaults"] rule: Add "ADD_COMPILE_FLAGS"Klaus Aehlig
The C++ programming language is tightly related to the C programming language. Consequently, the command line interface for C and C++ are also related and share quite a number of compile flags. Honor this tight connection by have in our defaults a field allowing to extend both compile flags, those for C as well as those for C++. In this way, build defaults can be described in a more readable way.
2024-04-29Update derived filesKlaus Aehlig
2024-04-29Merge branch 'just-rules' into rulesKlaus Aehlig
2024-04-29Merge subtree 'rules' into rules-ccKlaus Aehlig
2024-04-29["CC/test", "test"]: support TIMEOUT_SCALEKlaus Aehlig
... to allow test actions to have a larger time out, while not changing anything in the build actions (and hence being able to use cache hits from normal build of the library being tested).
2024-04-17Update derived filesKlaus Aehlig
2024-04-17Merge branch 'just-rules' into rulesKlaus Aehlig
2024-04-17Merge subtree 'rules' into rules-ccKlaus Aehlig
2024-04-17["CC/test", "test"] runner: set TMPDIRKlaus Aehlig
... to the same value as TEST_TMPDIR. While TEST_TMPDIR is the conventional name that tests should use for their temporary file, setting TMPDIR as well has the advantage that more library functions can be used to create temporary files and directories, as quite a few of them inspect the variable TMPDIR. While there, also fix some typos in the documentation strings.
2024-04-17["CC/test", "test"] use stage expressionKlaus Aehlig
... instead of inlining the code. In this way, we also have all the checks that the test runner consists of precisely one artifact.
2024-03-05Merge branch 'just-rules' into rulesKlaus Aehlig
2024-03-05Merge subtree 'rules' into rules-ccKlaus Aehlig
2024-03-05test summarizer: in case of FLAKY tests, also report failure rateKlaus Aehlig
2024-02-15Merge branch 'just-rules' into rulesKlaus Aehlig
2024-02-15Merge subtree 'rules' into rules-ccKlaus Aehlig
2024-02-15Remove unnecessarily quadratic expressionsKlaus Aehlig
... not that everyone has updated to 1.2 or later we can use the built-in expressions "reverse" and "set".
2023-11-30Merge subtree 'rules' into rules-ccKlaus Aehlig
2023-11-30CC/foreign/shell rules: avoid empty path segmentKlaus Aehlig
... and hence accidentally picking up executables from the current working directory.
2023-11-20docs: Add foreign shell libraryOliver Reiche
2023-11-20tests: No need to copy zlib librariesOliver Reiche
2023-11-20Merge subtree 'rules' into rules-ccOliver Reiche
2023-11-20Merge branch 'just-rules' into rulesOliver Reiche
2023-11-20rules: Fix flag inheritanceOliver Reiche
... which should accumulate values from all base targets unless the flag type (CFLAGS, CXXFLAGS, or LDFLAGS) is explicity overwritten by the inheritor.
2023-11-20foreign: Implement shell libraryOliver Reiche
2023-11-20foreign: Only resolve symlinks on user requestOliver Reiche
2023-11-20foreign: Do not follow symlinks of tool pathsOliver Reiche
2023-11-20prebuilt: Consider "deps" for flag reader inputsOliver Reiche
... so that if e.g., libfoo depends on libbar via "deps", the flag "-lbar" should be filtered out from the flag file generated via pkg-config from file foo.pc. Omitting these flags is always correct, due to those libraries being part of the explicit link dependencies already.