.o files in my home directory. about linter-gcc HOT 16 CLOSED

I think you might need to add -fsyntax-only to your C/C++ flags. That should prevent the generation of object files but still do syntax checking. Could you repeat the steps above, but with -fsyntax-only in your C/C++ flags?

from linter-gcc.

I just had an idea!!!! Try adding this option: -o /dev/null. This will tell GCC to write the object file to /dev/null, which means it will simply get thrown away!

from linter-gcc.

Hello. Could you open the developer console (by pressing Ctrl+Shift+I), copy the linter-gcc command, and paste it here?

from linter-gcc.

Here it is :

linter-gcc: /usr/bin/gcc -W -Wall -Wextra -pedantic -std=c++11 -c -fmax-errors=0 -I/home/grange_c/vox/include/ -I/home/grange_c/vox/include/lib/ -I/home/grange_c/vox/include/class/ -I/home/include/ -I/home/grange_c/include/ /home/grange_c/vox/src/main.cpp

from linter-gcc.

Ok. Could you try the following:

1. Close Atom
2. Delete the *.o files
3. Edit your C/C++ compile flags so that -c is right at the start
4. Use linter-gcc normally, and see if any new *.o files are generated.

from linter-gcc.

Hi !

I tried the 4 steps, and yeah it's still making *.o files.

linter-gcc: /usr/bin/gcc -c -W -Wall -Wextra -pedantic -std=c++11 -fmax-errors=0 -I/home/grange_c/.froot/include/ -I/home/grange_c/vox/include/ -I/home/grange_c/vox/include/lib/ -I/home/grange_c/vox/include/class/ /home/grange_c/vox/src/main.cpp

By the way, i think the *.o files are generated only when i'm saving a *.cpp file without any GCC error.

Thanks for the help !

from linter-gcc.

Yeah it's wokring like that, but i don't like -fsyntax-only, it's adding useless errors while working with libraries like opengl. >_>

But it's working fine, thanks !

from linter-gcc.

You say there are useless errors when working with opengl. I assume these are to do with certain functions being undefined. Is that correct? In that case you could simply link against the opengl library (with an option like -lgl or something like that). But then again if you link you might get errors saying your main is undefined (if linting a source file that doesn't contain a main function).

from linter-gcc.

Brilliant ! It works fine !

Would be great if it was enable by default ^_^

from linter-gcc.

Yes I will add it to the default flags, and to the README in the next version.

from linter-gcc.

@hebaishi -o /dev/null not working on windows with gcc 5.3.0, and solution for this ? It's generating .o files everywhere for every atom projects I open...

from linter-gcc.

I believe the default null device on Windows is NUL. So try -o NUL.

from linter-gcc.

@Ehekatl everything working for you?

from linter-gcc.

@hebaishi work like a charm, many thanks : )

from linter-gcc.

I have the same issue and both, -fsyntax-only and -o /dev/null worked for me (deleting it make a .o file instantly).
But I have a doubt about if -fsyntax-only could generate conflict with -Wall making it useless.
Can someone explain?

Thanks for the help ;)

from linter-gcc.

I have the same issue and both, -fsyntax-only and -o /dev/null worked for me (deleting it make a .o file instantly).
But I have a doubt about if -fsyntax-only could generate conflict with -Wall making it useless.
Can someone explain?

Thanks for the help ;)

I'd suggest you don't need the -fsyntax-only if you're just discarding output with -o /dev/null...

from linter-gcc.