Age | Commit message (Collapse) | Author |
|
...to match the ones produces by latest binaries and rules.
|
|
While there, update outputs to what is expected with current
released binaries and rules.
Co-authored-by: Klaus Aehlig <klaus.aehlig@huawei.com>
|
|
...to example export targets and defaults.
|
|
...instead of replacing CFLAGS and CXXFLAGS, thus also fixing a
mismatch introduced in c008c07656fff528c80add260397c7c7702aa2a8.
|
|
|
|
It is already supported to ask just-mr (via the rc file) to log for
each invocation the artifacts that were built. Add a similar option
for the artifacts that were to be built, i.e., for dumping the
intensional description of the output artifacts. That information
can be used, e.g., to compute the critical path.
|
|
A typical invocation logging would also include a value
for "--dump-artifacts". Mention this in the tutorial.
|
|
... as this also works together with, e.g., linting. While there,
also rerun the examples to get the latest output messages.
|
|
|
|
|
|
|
|
In preparation for the rule changes, to avoid introducing false
positives during future bisections.
|
|
... under the advanced chapter of our tutorial.
|
|
... and ensure that pandoc processes them correctly. In particular,
add an empty line around itemize environments.
|
|
|
|
Also update the README.
|
|
...instead of using the master branch.
|
|
Add the artifacts and outputs of the updated rules, as well as
some explanatory remarks.
|
|
- As we build a binary hello, make it an extension of the hello
we had before.
- Make the passing of time more explicit.
- Add actual output of rerunning the tutorial.
|
|
As our defaults rule supports flags common for C and C++ use
them, especially as our example only uses common flags.
|
|
|
|
|
|
... in particular in the case of targets producing precisely one
artifact; this better emphasizes the idea that we talk to the tool
in terms of targets. While there, also add some clarifying comments.
|
|
|
|
|
|
|
|
|
|
This is an essential step in the debugging process that was missing
in the tutorial.
|
|
... as they will be used in newer versions of rules-cc to set the
path for the test-summary action.
|
|
This showcases that also generated proto headers will be staged for
debugging.
|
|
|
|
This is good practice and it makes it easier to later demonstrate
debugging, as the flag value is honored.
Also renames the final repos.json example, in order to ensure that
any chapters depending on the output of this chapter receives the
correct repository description.
|
|
|
|
...to version fully supporting debugging.
|
|
... so that the tutorial also works with the latest version of our rules.
|
|
Also updates the tests and all relevant documentation accordingly.
|
|
|
|
When tutorial docs were changed to showcase running commands with
just-mr instead of just, the outputs were not changed. This is now
fixed to showcase the results run with current master just-mr (and
just), together with other small improvements and fixes.
|
|
|
|
|
|
When explaining CC tests, the option --request-action-input is used
to get hold of the actual test binary. This is the first time in
the tutorial where the action graph is larger than the part that
that is traversed during the build. Use this oportunity to explain
the difference between those concpets as, reportedly, some users
got confused about this.
|
|
... and point to the repository with machine-readable instructions
on how to properly build them.
|
|
|
|
|
|
|
|
While there,
- remove the outdated claim that in package build of just the prebuilt
library aproach of a header-only library with link dependencies
is chosen, and
- remove a wrong footnote separator.
|
|
... while providing a native descirption still is the cleaner approach.
Nevertheless, hinting on this fact early avoids scaring off novice
users having a lot of dependencies.
|
|
... as a way to find out more about the defining rule of a target.
While there, also be a bit more explicit about target naming and the
fact that the default target is a target of the rules repository.
|
|
... emphasizing that source files are just targets and that we
could as well use a defined target there.
|
|
|