Paul Wankadia
https://alexreinking.com/blog/building-a-dual-shared-and-static-library-with-cmake.html describes the contortions needed, but its focus is really on making it ergonomic to use one or the other, so you still end up building and installing twice anyway.
For RE2, I implemented `py_extension()` in Starlark (see https://code-review.googlesource.com/c/re2/+/58370) such that we inject `copts` for the Python toolchain that Bazel selected (e.g. `-I/usr/include/python3.9`) into the C++ compile command. It's very...
I'm confident that it would, but the idea here is to spare every project the `sha256sum … | base64 -w0` and `base64-subjects` dance and, moreover, to ensure that the `gh...
Just to be clear, the idea is **_not_** to generate the source code archives manually. (GitHub already does that automatically.) The reason to do the [`gh release download`](https://cli.github.com/manual/gh_release_download) and [`gh...
As linked above, https://blog.bazel.build/2023/02/15/github-archive-checksum.html describes the situation quite well, I think, with the screenshot illustrating the difference between `…/archive/refs/tags/…` and `…/releases/download/…` in terms of the release assets. The problem that...
I had "do one thing and do it well" in mind, I think, when I suggested another workflow. `generator_generic_slsa3.yml` has a lot of knobs whereas this use case needs approximately...
In light of CVE-2024-3094, could this effort possibly be prioritised? ;)
In case it helps, I wrote https://github.com/google/re2/blob/main/.github/workflows/release.yml earlier today. :)
IIUC, yes, the PW would run `gh release create` (except using the API instead of the CLI) and then invoke the TRW, which would handle everything else. Although now I'm...