Closed afkfish closed 3 years ago
Inside the build folder there is the debug folder and there is the executable. But you can just click on the play button in the blue status bar. Everything works as expected for you
there is no such file and no errorr as well the file on the left is just the source file
https://files.fm/u/gfh368jxf#/view/jmy3rcam8 in video to better understand
Okay, very interesting. Currently i cannot imaging what the problem might be.
Could you try this with a different make/compiler setup (if you have installed something else than msys/mingw64)
im currently installing cygwin
i dont know what is the issue but still with cygwin as well its just bad
Its probably fixed but i dont think it is the best solution, so i tried everything and so i ran the command what the vscode is using when generating the file in a command promt and that generated the files successfully. The generate button still doesnt work it does not change or modify the exe and the run does not start the program but at least i can generate the file manually. I dont know wether this is an issue with the compiler or smt else but from vscode its still bad. If i can provide anything to further investigate what could be the issue please ask.
What is the output of this command in the CMD when you are in the current workspace dir?
tree /F
I dont know if it is maybe a permission problem on your PC with creating the exe.
its the same as in the vs code terminal but here it is working i guess i could be but i dont see why it cant build a file on my desktop
Can you try to start VSCode as admin and then retry?
It did the same, nothing changed still the directories are the only things that are being created.
Do you have by any chance WSL installed on your windows pc? If so, you could try it on the WSL.
I still have the feeling that the issue has something to do with user permissons.
No I don't have that. I'll try it on an another drive. Unfortunately it did nothing either.
Can you try to use the experimental setting (after setting this VSCode restart is needed). This should work then.
I will add a fix that for MinGW Users, Makefile is not used anymore but instead the currently called "experimental setting" is used.
it makes a different errorr but its something
PowerShell really sucks again. I will try to add a fix for the PowerShell.
thank you for all i really apreaciate and i will wait then for the fix, and thank you for your patience
The issue with PowerShell will be fixed in todays release 1.4.0. For the MinGW problem i still dont have a solution.
The experimental thing fixed it so the only issue was the power shell. The new version works well thank you!
Hi im new to this but i'm having an issue and after serious research i still lost. I'm on windows and installed mingw as welll as all the other things that is needed, changed the settings so the gcc and g++.exe is in the correct location and the make.exe as well but when i want to compile a pretty basic c program it always generates an empty folder and leaves no error that i could recognise and solve. As i said i'm pretty noob in this.