-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide pdb file for cydlib/bin on Windows in a pdb_file
output group
#1065
Conversation
8b0e966
to
e30d133
Compare
Looks like the test launcher adds its own |
e30d133
to
5cc6a21
Compare
The launcher is actually something I think we need to remove. I can ad an incompatibility flag for it |
c222696
to
32518eb
Compare
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?
32518eb
to
0bc4fdf
Compare
Sorry this took so long. I've opened #1070 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for putting this together, Awesome work! 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, one last change, if you don't mind 😅
57f0e43
to
f2a641d
Compare
f2a641d
to
2c92366
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much!
I've chose the
pdb_file
name for the output group since it matches whatcc_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 therustc_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 therustc_flags
for it but I don't know if it's the right place to do so?