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

Unable to Linter without clang #7

Open
Tomaqa opened this issue Sep 17, 2021 · 1 comment
Open

Unable to Linter without clang #7

Tomaqa opened this issue Sep 17, 2021 · 1 comment

Comments

@Tomaqa
Copy link

Tomaqa commented Sep 17, 2021

I'm not 100% sure if this issue is related to the Atom package or to the ccls itself.

I'm using gcc with its specific flags. I configured the ccls to use it (tried both .ccls and compile_commands.json) and it works fine in the case of indexing, hyperclicking etc.
However, the issue is that the "Linter part" seemly still uses clang and not gcc, which results in highlighting many "errors", that I know that do not appear at gcc.
I also tried to configure Linter to blacklist ccls or ide-ccls, but it does not work at the moment.

Ideally, I'd like to be able to configure the "Linter part" to use gcc too, which I did not figure out how to do it (I suppose that from Atom it is impossible to configure the --init option for the ccls).
Well, I'm not sure if completely abandoning clang is possible in ccls at all, but I would be glad if the "Linter part" could be, at least, just disabled in the package, so I can just keep on using linter-gcc package.

@isundaylee
Copy link
Owner

Hi - sorry I haven't been using Atom in a while so haven't been following up here. As far as I understand ccls would still be using clang under the hood for linting since it's built on top of the clang framework, but folks over at the ccls project would have a better understanding there.

As for passing the --init option, that was added in #2. If a particular option is missing it would be possible to add it there. Unfortunately since I no longer use Atom I won't be able to test it. But feel free to fork the project/submit PRs.

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