We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
INFO: From ...
On Windows:
INFO: From Compiling examples/rdc/b.cu: b.cu INFO: From Compiling examples/rdc/b.cu: b.cu INFO: From Compiling examples/rdc/a.cu: a.cu INFO: From Compiling examples/rdc/a.cu: a.cu INFO: From Compiling examples/basic/kernel.cu: kernel.cu INFO: From Compiling examples/basic/kernel.cu: kernel.cu INFO: From Device linking bazel-out/x64_windows-fastbuild/bin/examples/rdc/librdc_dlink.rdc.obj: a.rdc.obj b.rdc.obj INFO: From Device linking bazel-out/x64_windows-fastbuild/bin/examples/rdc/librdc_dlink.rdc.pic.obj: a.rdc.pic.obj b.rdc.pic.obj ...
It comes from cl.exe blindly output input file name to stdout Unless https://togithub.com/bazelbuild/bazel/issues/5511 or https://developercommunity.visualstudio.com/t/allow-having-clexe-not-print-the-compiled-source-f/717761 is addressed.
cl.exe
The text was updated successfully, but these errors were encountered:
Add build --ui_event_filters=-INFO to .bazelrc to avoid it.
build --ui_event_filters=-INFO
.bazelrc
Sorry, something went wrong.
No branches or pull requests
On Windows:
It comes from
cl.exe
blindly output input file name to stdoutUnless https://togithub.com/bazelbuild/bazel/issues/5511 or https://developercommunity.visualstudio.com/t/allow-having-clexe-not-print-the-compiled-source-f/717761 is addressed.
The text was updated successfully, but these errors were encountered: