-
Notifications
You must be signed in to change notification settings - Fork 312
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
Unable to resolve includes from "external" targets #6495
Comments
Hi, I was not able to reproduce your issue. Can you try |
So I tried that but I had no luck, is there an easy way to see what include paths are being provided by the plugin to Clion to allow it to find an included header? .. This was just an example but I have multiple third party/external libraries that are imported in via rules in the WORKSPACE file; using new_local_repository, new_git_repository and http_archive that are not being found/resolved by Clion's intellisense .. Couple of other things; I am using Clion in the Dev Container mode so I'm not sure if that is supported, also I have tried this with VSCode's Bazel plugin and it seems to do fine at resolving these includes, though I do prefer using CLion so I'm hoping theres a way to get this working . |
@sid-kumar-figure could you share your OS and Bazel version, too? |
OS is Ubuntu 22.04 LTS |
Hi, sorry for the late response. I tried to reproduce your issue by connecting to a remote machine using ssh. So far everything is still working in my case. You can see all the include paths and more for a file when you run the Btw easiest way to find this action is to search for it. |
I apologize for the later reply. I think the Here is the requested info:
|
Description of the bug:
Clion is unable to find any of my included targets from "external" targets that are imported in WORKSPACE.
I am running Clion with a Dev Container.
Example:
Clion cannot find
flexi_cfg/reader.h
:Which I have included via this
git_repository
rule in WORKSPACE:This is the build_file content just for completeness:
I can manually see the file :
Which category does this issue belong to?
CLion
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I'm fairly new to using Bazel in Clion, But atleast in my setup you can reproduce this problem by importing any "external" library/package in WORKSPACE and trying to include a header file from that library/package.
Which Intellij IDE are you using? Please provide the specific version.
Clion 2024.1.3
What programming languages and tools are you using? Please provide specific versions.
Language: C++
What Bazel plugin version are you using?
2024.06.04.0.2-api-version-241
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: