Not working in Windows 10 - followed evrything

AtomLinter / linter-gcc

Atom-linter extension to lint C/C++ source files using gcc/g++

Other

71 stars 21 forks source link

Not working in Windows 10 - followed evrything #158

Closed ShakilAhmedShaj closed 5 years ago

ShakilAhmedShaj commented 6 years ago

Checklist

[x] Check that you have the GNU C Compiler installed by typing gcc --version into a terminal.
[x] If you don't have the linter package installed, either update to the latest version of linter-gcc or install linter directly with apm install linter.
[x] Ensure that you are using a valid grammar - either C/C++/C++14
[x] Ensure that you have read all the relevant information in the wiki, particularly the Common Issues page.

Issue (including debugging messages):

I have followed every step from this link - https://github.com/hebaishi/linter-gcc/wiki/Windows-Users-Guide

This is my package settings -

These are my windows path links -

and this is my atom editor pic, its just blank

and here is the g++ output -

please help me ;-(

DamSenViet commented 6 years ago

It's a linter, not a terminal that you can run programs in. It's supposed to be blank if there are no ERRORS... linter-gcc does throw warnings from gcc's -Wall flag though. If what you want is a program you can run c programs in, get platformio-ide-terminal and use the command line to compile and run.

ShakilAhmedShaj commented 6 years ago

I just given this terminal view to let u know that gcc is working, I dont want to run my code in terminal, my linter gcc is not working I mean its not running or showing any error.

sweenish commented 6 years ago

It is indeed broken on Windows 10, at least.

If I delete a semi-colon, the status bar will change to show one error and one warning, but when I pull up the panel, it's blank. After I add the semi-colon back, the status bar never changes. C:\MinGW\bin in the PATH (have rebooted as well), include directory setup as well (C:\MinGW\include), have tried using both / and \ at the end, but it makes no difference. Have used it with Atom's built-in C++, and the language-cpp14 package, doesn't work with either one.

The linter is broke on Windows, and flaky at best on Linux.

On Windows, it has failed to work with mingw and MSYS2. Have not tried Cygwin, but if it doesn't work with those two, I don't see Cygwin working.

Would it stand a chance at working with the VS C++ libraries in the include path while still using g++ as the compiler? I'm leaning toward no, but I haven't tried that yet. VS Code is set up to lint using those libraries, but I always compile manually through the integrated bash terminal (Arch in my case).

babingbaboom commented 5 years ago

Same problem, the linter didn't seem to manage to produce anything.

walnutwaldo commented 5 years ago

I'm having the same problem.

Filliny commented 5 years ago

Same here- no errrors in dev console, no displaying errors in code... if it works - it works silent)

dot-tb commented 5 years ago

Linter GCC doesn't work anymore, get LinterGCC2