Skip to content
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

info command does not support starlark options #15

Closed
drnikolaev opened this issue Jul 26, 2022 · 4 comments
Closed

info command does not support starlark options #15

drnikolaev opened this issue Jul 26, 2022 · 4 comments

Comments

@drnikolaev
Copy link

$ bazel info --curses=no --color=yes --progress_in_terminal_title=no -- (19:48:51) WARNING: info command does not support starlark options. Ignoring options: [--@rules_cuda//cuda:enable=True, --@rules_cuda//cuda:copts=-std=c++17]
Could you check please?

@cloudhan
Copy link
Collaborator

After a brief search, it seems that it is bazel's design choice, or maybe flaw. See bazelbuild/bazel#13473 for the detail.

It seems that your have

build --@rules_cuda//cuda:enable=True

in your .bazelrc, but bazel info reads this build option. This should be harmless, you can just ignore the warning in this case.
If you want to mute it, redirect the warning as mentioned in that issue, or change the .bazelrc to

build:cuda --@rules_cuda//cuda:enable=True

then invoke bazel build ... as bazel build --config cuda .... Your choice.

@drnikolaev
Copy link
Author

This happens inside CLion and prevents it from properly "syncing" the code base. As a result, no code navigation possible. So, for this use case it's not harmless :(

@cloudhan
Copy link
Collaborator

Try this one bazelbuild/bazel#13473 (comment)

@cloudhan
Copy link
Collaborator

cloudhan commented Aug 4, 2022

I'd assume this problem is solved. Close for not. Feel free to reopen if it doesn't.

@cloudhan cloudhan closed this as completed Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants