War story from the build system trenches: Integrating Bazel and Testwell CTC++ code coverage - скачать в хорошем качестве

War story from the build system trenches: Integrating Bazel and Testwell CTC++ code coverage -

This talk was recorded at NDC TechTown in Kongsberg, Norway. #ndctechtown #ndcconferences #developer #softwaredeveloper Attend the next NDC conference near you: https://ndcconferences.com https://ndctechtown.com/ Subscribe to our YouTube channel and learn every day: / ‪@NDC‬ Follow our Social Media!   / ndcconferences     / ndc_conferences     / ndc_conferences   #cplusplus #clanguage #platform Not all tools play well together, and this talk describes a particularly challenging integration that we recently encountered at one of our automotive clients. [Bazel](https://bazel.build) is an open source build system popular with large and complex code bases, especially those that combine multiple languages and platforms. Thus it is not surprising that it's gaining traction in the embedded and automotive space. Bazel's motto, "{ Fast, Correct } -- Choose two", is achieved by making each step of the build process reproducible and thus cacheable. [Testwell CTC++](https://verifysoft.com/en_ctcpp.html) is a proprietary code coverage tool from Verifysoft, and a popular choice for ensuring good code coverage in the automative industry. It relies on instrumenting the source code during the build process as well as generating extra build-time and run-time outputs that are not particularly reproducible or cacheable. We'll cover how we resolved the impedance mismatch between these two tools: Adjusting the Bazel sandbox to allow CTC++ to run successfully from Bazel Hacking the intermediate outputs from CTC++ to achieve reproducibility, and thus be able to benefit from Bazel's caching. Various bumps we ran into along the way, including some light ELF hacking for fun and profit!