"*.gch" files created during lint about linter-gcc HOT 12 CLOSED

What about using -fsyntax-only flag? I tested it and the linter is working, saving header files doesn't generate anything anymore and the only disadvantage of this solution is the lack of any information about linker errors (but without -fsyntax-only flag linter isn't giving any details about the latters anyway, only "ld returned 1 exit status" error).

from linter-gcc.

Hello. I'm afraid this is unavoidable. When you run g++ -c headerfile.h, GCC compiles the header and generates headerfile.h.gch. I'm sorry but I haven't found a way of preventing g++ from generating these files. If you do, please feel free to re-open this issue. However, if you are hosting a C/C++ project on github, you can simply add *.gch to your .gitignore file to tell git to ignore these files.

from linter-gcc.

Hello, so the reason behind the creation of the headerfile.h.gch file is so atom can tell if there is an syntax error?

from linter-gcc.

I have just done some reading and it turns out there is a way to avoid actual compilation. The way to do this is by supplying the -gnats option to GCC. More info here

Edit: I've just tried using the -gnats option and it looks like it doesn't work.

from linter-gcc.

Is there a way of disabling linting on .h files? In some situations the spontaneous creation of .gch files is very unhelpful.

from linter-gcc.

Yes that's actually not a bad idea. I can add a regex field to generalise this so the user can choose to exclude files matching a certain pattern. What do you think?

from linter-gcc.

If that works, then you can simply add that to your flags. No need to add an extra option for header files.

from linter-gcc.

So, we have a solution :)

from linter-gcc.

I'll add a note in the README about this.

from linter-gcc.

@Toreno96: Thanks, that works nicely!

from linter-gcc.

Wow, thanks @Toreno96!

from linter-gcc.

Just a heads up, I know this is an old thread but I have found saving using "Save All" in the file menu or on MacOS CMD+OPTION/ALT+S works and avoids .gch files being made. This I believe, for whatever reason skips the linter on save and simply saves the file. I expect however if you are relying on syntax checking your file it may be skipped in this case.

from linter-gcc.