vscode粘在“启动构建”上。

发布于 2025-01-25 11:16:26 字数 484 浏览 3 评论 0原文

我将VSCODE与GCC一起使用来编译C代码。上周我也使用了同一启动和tasks.json文件。它被困在“启动构建...”上

,但是,如果我将命令粘贴在“启动构建...”下,直接粘贴到终端,则确实创建了编译的二进制文件。

我没有帮助谷歌搜索。

karthik@cosmic:~$ code --version
1.66.2
dfd34e8260c270da74b5c2d86d61aee4b6d56977
x64
karthik@cosmic:~$ uname -osr
Linux 5.16.19-76051619-generic GNU/Linux

I use VSCode along with gcc to compile C code. I was using the same launch.json and tasks.json file last week too but it no longer compiles since today; it's stuck on "Starting Build..."

However, if I paste the command under "Starting Build..." directly to the terminal, the compiled binary is indeed created.

I got no help in Googling.

Please have look at this

karthik@cosmic:~$ code --version
1.66.2
dfd34e8260c270da74b5c2d86d61aee4b6d56977
x64
karthik@cosmic:~$ uname -osr
Linux 5.16.19-76051619-generic GNU/Linux

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

枯叶蝶 2025-02-01 11:16:26

我也遇到了同样的问题,但是在访问github和#9421 我注意到问题是由于新版本的C/C ++扩展。只需尝试将版本降低到1.9.8(最新版本为1.10.7,ofient)。

此解决方法对我和最新版本的VS代码(1.68.1)期间编制了。

(请注意,我的文件夹名称中也有空格

  • vs code-1.68.1

  • GCC版本(MSYS2)-11.2.0

I also faced the same issue, but on visiting your issue on GitHub and #9421 I noticed that the issue was due to the new version of the C/C++ extension. Just try to downgrade the version back to 1.9.8 (the latest version is 1.10.7, period).

This workaround worked for me and the code compiled in the latest version of VS code, 1.68.1, period.

(Note that I also had spaces in my folder names. So, I tweaked tasks.json by adding inverted commas for the file path.)

  • OS-Windows 10

  • VS code-1.68.1

  • GCC version(MSYS2)- 11.2.0

花落人断肠 2025-02-01 11:16:26

在GitHub开了一个问题之后,获悉,这是截至2022年5月2日的最新版本VSCODE的错误,他们已经在修复它,

现在可以确保目录名称和目录名称和目录名称中没有空格您的项目工作区中的文件名;因此,更新任务。JSON和启动。

更多信息在这里

After opening an issue at Github, it was informed that this was a bug with the latest version of VSCode as of 02nd May 2022 and they're already on fixing it

A possible work-around for now is ensuring there's no spaces in directory names and file names in your project workspace; thus update the tasks.json and launch.json too with the same.

More info here

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文