Skip to content

Extensions for running applications other than Node.js do not work #2391

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cheshie opened this issue Dec 2, 2020 · 6 comments
Closed

Extensions for running applications other than Node.js do not work #2391

cheshie opened this issue Dec 2, 2020 · 6 comments
Labels
docs Documentation related

Comments

@cheshie
Copy link

cheshie commented Dec 2, 2020

Hi, started using your app recently and I tried today to add extension for running/debugging C/C++ applications. The extension installs alright, both from inside the app list and installing manually via .vxsix file. However, it does not edit the launch.json file and the vs code does not see it on the list of installed extensions either. What is the problem here? Is it that vs code server does only help with running node.js so far, or are other languages supported as well? If so, there should be some documentation from you saying how to add these extensions, 'cause my "thorough" 2hrs research just simply didn't work.
Btw great app. Apart from minor issues, my main development env on iPad Pro (vs code runs on Linux Centos VPS)

@cheshie cheshie added the docs Documentation related label Dec 2, 2020
@code-asher
Copy link
Member

code-asher commented Dec 2, 2020 via email

@cheshie
Copy link
Author

cheshie commented Dec 4, 2020

Hi, thank you for the help. I tried with to run vs with --debug trace option. After opening vs again on my iPad i received a notification saying that extension ms-vscode.cpptools-1.1.2 did not install correctly, and asking whether I'd like to install it again. I did so, and received:

/home/coder/.local/share/code-server/extensions/ms-vscode.cpptools-1.1.2/bin/cpptools: /home/coder/.local/share/code-server/extensions/ms-vscode.cpptools-1.1.2/bin/cpptools: cannot execute binary file

I also tried downloading and installing cpptools-linux-aarch64.vsix. It installed successfully, however for some reason no change is visible. On the tab "Run and Debug" there is still default text "To customize Run and Debug create a launch.json file (...)". I even did so manually, and it is still not visible in this tab, just like vs code still does not see it. Installing and launching Node.js, Edge, Chrome extensions work, in terms that I chose the extension, installed it, and it was automatically written to launch.json file. However, I did not test whether any of these actually work, as I usually don't develop anything in js. As for the logs, I attached ms-vscode-cpptools.txt from the ~/.local/share/code-server/logs dir.

Is there anything else I can do? I tried your IDE, it works well for me, apart from minor issues with using Magic Keyboard on my iPad (but I've already seen you work on it, as there were some existing issues here relating to the topic). I'd really like to make these Extensions thing work, though.
ms-vscode-cpptools.txt

@code-asher
Copy link
Member

code-asher commented Dec 4, 2020

Ohhh, it looks like this is causing the crash:

telemetry/C_Cpp/LanguageServer/missingBinary {"properties":{"source":"mono.linux-x86_64"}}

You might be running into this issue then: #2263

Did you install cpptools-linux-aarch64.vsix from the cpptools GitHub repository or from our marketplace?

@code-asher
Copy link
Member

Also keep in mind you'll need cpptools-linux.vsix (not aarch64) if you're not using arm.

@cheshie
Copy link
Author

cheshie commented Dec 5, 2020

Thank you very much for the help, using cpptools-linux.vsix manually resolved the issue and now I can use the extension with no problems. I am extremely sorry for the trouble, if only I'd read that aarch64 extends to ARM-arch64, not just "arch64" (which I thought at a first glance), I would've probably resolved the issue on my own.
Anyway, the manual install worked for me, but the automatic installation from your marketplace is still an issue I think. I won't need any more help, and can close the issue, since I can now run this extension, but is there anything I can do (like provide more logs), so that you'll be able to figure out why automatic installation didn't work? I mean if some others stumble over this problem in the future

@code-asher
Copy link
Member

code-asher commented Dec 7, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation related
Projects
None yet
Development

No branches or pull requests

2 participants