summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
7 daysUpdate README with changes in template fileHEADmasterPaul Cristian Sarbu
7 daysREADME template: Add section on debug fissionPaul Cristian Sarbu
While there, fix a typo.
7 daysAdd extra documentation for debug fissionPaul Cristian Sarbu
8 daysUpdate README with docs fixesPaul Cristian Sarbu
8 daysMerge commit 'e3bf397df26fc63c7348ec834bf7e6f31ef6f894' into HEADPaul Cristian Sarbu
8 daysrules foreign make: Fix typos in docsPaul Cristian Sarbu
8 daysrules foreign make: Fix typos in docsPaul Cristian Sarbu
2025-05-28Update README with recent documentation fixesv1.6.0-alpha+20250606Paul Cristian Sarbu
2025-05-28rules lint: Fix spacing for missing target namePaul Cristian Sarbu
2025-05-28rules lint: Fix spacing for missing target namePaul Cristian Sarbu
2025-05-28rules documentation: Fix typosPaul Cristian Sarbu
2025-05-28rules documentation: Fix typosPaul Cristian Sarbu
2025-05-28Merge commit 'c293add09786c810380602f1ea3c29ad32c4635a' into HEADPaul Cristian Sarbu
2025-05-28Merge commit '65888db62a3bb33285978b60c6c496081105e46d' into HEADPaul Cristian Sarbu
2025-05-28rules documentation: Fix typosPaul Cristian Sarbu
2025-05-21Merge subtree 'rules' into rules-ccKlaus Aehlig
2025-05-21Merge branch 'just-rules' into rulesKlaus Aehlig
2025-05-21shell-test runner: explicitly set HOMEKlaus Aehlig
... to a value that is a non-existent directory. Too many tools try search for rc-files in the user's home directory. To make things worth, the shell as well as many tools take an unset HOME variable as instruction to look up the the user's home directory in the system configuration. While it is good practise to write tests in such a way that they explcitly do not depend on such machine-specific defaults, still be on the safe side by explictly setting HOME to a directory in the action directory we know our rules will no create. Co-authored-by: Paul Cristian Sarbu <paul.cristian.sarbu@huawei.com> Co-authored-by: Sascha Roloff <sascha.roloff@huawei.com>
2025-05-20Update just referenceKlaus Aehlig
... after the grpc update.
2025-05-12Update documentationKlaus Aehlig
2025-05-12Include ["test", "matrix"] in rules documentationKlaus Aehlig
2025-05-12Merge branch 'just-rules' into rulesKlaus Aehlig
2025-05-12Merge subtree 'rules' into rules-ccKlaus Aehlig
2025-05-12["test", "matrix"] Building a group of tests in many configurationsKlaus Aehlig
Often it is desirable to run tests in a variety of configurations: different toolchain used, different target architecture, different protocol versions in end-to-end tests, etc. The rule ["test", "matrix"] allows running tests in those exponentially many combinations in a single target and thus makes full test coverage maintainable.
2025-05-08Update derived filesKlaus Aehlig
2025-05-08Merge branch 'just-rules' into rulesKlaus Aehlig
2025-05-08Merge subtree 'rules' into rules-ccKlaus Aehlig
2025-05-08rules: Allow all false values to disable DEBUGKlaus Aehlig
While activating DEBUG requires setting it to a non-empty map, providing information on whether and how debugg fission should be used, we should still allow any logically false value (rather than just null) to disable a debug build in order to make it easier for the user to explicitly disable debugging. Also adopt and fix the documentation strings.
2025-05-07Merge subtree 'rules' into rules-ccOliver Reiche
* commit 'b909c514866f1f0713edd831d183e4fa1e5c91f5': Do not assume out_dirs exist rules: Do not assume out_dirs exist
2025-05-07Do not assume out_dirs existOliver Reiche
2025-05-07Merge branch 'just-rules' into rulesOliver Reiche
* rules/oss: rules: Do not assume out_dirs exist
2025-05-07rules: Do not assume out_dirs existOliver Reiche
2025-04-23Update README with debug-fission changesPaul Cristian Sarbu
2025-04-23Merge commit '1e7f2ce643f9b2c7e07c7cec7f04bcf13b489668' into HEADPaul Cristian Sarbu
2025-04-23Merge commit '20b7c7fa1b10a90e0e3aad46579ebe450d6720b9' into HEADPaul Cristian Sarbu
2025-04-23rules-cc tests: Update DEBUG config variable to mapPaul Cristian Sarbu
In preparation for the rule changes, to avoid introducing false positives during future bisections.
2025-04-23rules CC: Extend install-wih-deps to stage DWARF package filesPaul Cristian Sarbu
2025-04-23rules CC: Libraries and binaries provide DWARF package filesPaul Cristian Sarbu
The "library" and "binary" rules are modified to generate, if needed, the appropriate DWARF package from the DWARF objects of their compilation units and the DWARF package files of their link dependencies, if any. The resulting artifact is made available to consumers in the provides map.
2025-04-23expressions CC: Add expression generating DWARF packagesPaul Cristian Sarbu
2025-04-23expressions CC: Small refactoringPaul Cristian Sarbu
Allow the expressions running the actions producing the library and binary artifacts to pass along more information to consumers if needed by extending their return values to maps. Ensure the changes do not affect other consumers of the current expressions, such as the test rules, which do not expect extra information besides the single action artifact.
2025-04-23rules CC: Add DWP configuration variablePaul Cristian Sarbu
...defining the DWARF format packaging tool to use once debug fission is supported.
2025-04-23rules CC: Support debug fission in lintingPaul Cristian Sarbu
As the command passed to the linter can produce additional outputs if debug fission is enabled, pass those artifact paths in a new variable "extra outs", which the ["lint", "targets"] rule can then make it available in the meta.json file expected by the linter.
2025-04-23rules CC: Support debug fission in objectsPaul Cristian Sarbu
For this purpose, the DEBUG configuration variable is updated to expect a map with at least the USE_DEBUG_FISSION flag field. If set, compilation of source files is expected to produce besides the regular object file also a DWARF file.
2025-04-23rules CC proto: Update docstring for DEBUG variablePaul Cristian Sarbu
...to reflect the value change from boolean to map. Behavior of the proto rules remains the same, as only the truth value of the variable is currently being taken into account.
2025-04-23rules CC: Make DEBUG variable a mapPaul Cristian Sarbu
It expects now the key 'USE_DEBUG_FISSION', which enables debug fission, but does not add any flags on its own. For this, the 'FISSION_CONFIG' key is expected with certain entries that provide the compile and/or link flags that configure debug fission. The flags are added only where needed, i.e., before running or storing the respective compile or link actions.
2025-04-23rules CC: Use the -g flag as fallback in debug mode...Paul Cristian Sarbu
...if no flags are otherwise configured (by toolchain or rule-specific configuration variables).
2025-04-23rules CC defaults: Add DEBUGFLAGS and ADD_DEBUGFLAGS config varsPaul Cristian Sarbu
If in debug mode - DEBUGFLAGS replaces any resulting CFLAGS and CXXFLAGS, and - ADD_DEBUGFLAGS is appended to the resulting debug compile flags.
2025-04-23expressions CC: Remove unused importPaul Cristian Sarbu
2025-03-21Update just reference to 1.5.0v1.5.0Klaus Aehlig
2025-03-21Merge commit '8308f26bb563c711915f40660898e37ef1c92155' into HEADPaul Cristian Sarbu