| commit | c0bdb55ec101133a051bfcf13ff3295f60055739 | [log] [tgz] |
|---|---|---|
| author | Damien DeVille <damien@ddeville.me> | Thu Dec 16 12:13:04 2021 -0800 |
| committer | GitHub <noreply@github.com> | Thu Dec 16 12:13:04 2021 -0800 |
| tree | 9952743ead580b7577af063f055c3b06a1607aef | |
| parent | 004e629d719248df3e16a7589615b3cd4908a175 [diff] |
Provide pdb file for cydlib/bin on Windows in a `pdb_file` output group (#1065) I've chose the `pdb_file` name for the output group since it matches what `cc_binary` uses (https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/rules/cpp/CcBinary.java;l=707) There is one edge case that is not covered here: if the user passes `/DEBUG:NONE` in the `rustc_flags` no pdb will be generated and I imagine the build will fail since it's now missing an output. I guess we could check the `rustc_flags` for it but I don't know if it's the right place to do so?
This repository provides rules for building Rust projects with Bazel.
General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust.
Please refer to the full documentation.