Skip to content
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

Using Microsoft C/C++ extension via "emulation"? #85

Open
natevw opened this issue Sep 20, 2019 · 3 comments
Open

Using Microsoft C/C++ extension via "emulation"? #85

natevw opened this issue Sep 20, 2019 · 3 comments

Comments

@natevw
Copy link

natevw commented Sep 20, 2019

I would like to use the official C/C++ extension on my Chromebook, but it fails to install when I click the button from within the Code-OSS extensions tab.

This wasn't a major surprise since "The extension has platform-specific binary dependencies" and only the four big build targets (Windows, macOS, Linux 32-bit, Linux 64-bit binaries) are mentioned. So I figured that was the end of that, until I noticed this in the Code-OSS FAQ:

Any dependencies that are not local to your architecture (e.g. x86 binary code on an ARM chromebook) will be emulated to ensure compatibility [...]

What's this now?? Is this something added on by this project or does the mainline VSC provide some sort of cross-CPU emulation? That seems pretty ambitious, but I'm wondering if I can take advantage of it for this C/C++ plugin. If so, which of the four available "offline" VSIX options would be the best to try it with?

@natevw
Copy link
Author

natevw commented Dec 10, 2019

Based on the subjunctive tense in the recent microsoft/vscode#1031 (comment) posting my guess is that the FAQ text was a Forward Looking Statement at that time too :-)

@headmelted
Copy link
Owner

I had this working quite some time back but there were changes in the upstream builds that broke it and it kind of fell by the wayside.

It’s not a big job to do (one of my other repos, Archie, uses this extensively to produce these builds), but I’m kind of wondering if it belongs better in a separate script for people that need it.

I’m going to look at this next and will update this ticket when I have something for you to test.

@natevw
Copy link
Author

natevw commented Dec 12, 2019

Ah, okay! Thanks for the clarification/pointers and welcome back :-)

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

No branches or pull requests

2 participants