Confusion regarding the licensing of vscode-builtin-cpp and vscode-cpptools #8564
-
Hi folks, I wanted to raise a potential problem related to vscode-builtin-cpp, which I believe is the preferred way to add C/C++ functionality to Theia. While I was trying to figure out why PlatformIO's VSCode extension can't be put on the OpenVSX registry, I stumbled open this recent discussion regarding the licensing of VSCode's C/C++ extension. This part of the conversation seemed worrying:
The license they mention is quite strict:
I wanted to confirm that the C++ functionality, which I get from here, does not use these mentioned binaries, and is safe regarding this issue. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
@yunuscukran thank you for the discussion, the two extensions you referenced are different (one being The |
Beta Was this translation helpful? Give feedback.
@yunuscukran thank you for the discussion, the two extensions you referenced are different (one being
vscode-builtin-cpp
and the other beingvscode-cpptools
). You are right thatvscode-cpptools
is quite restrictive, it's one of the reasons we do not use it ourselves, nor is it present in our example apps under theia-apps. Instead, we usevscode-clangd
extension maintained by the LLVM community.The
vscode-builtin-cpp
like other builtins are part of vscode repository (safe to use) and it only provides texmate grammars and snippets for the C/C++ language (these extensions are published by the community under the theia-ide/vscode-builtin-extensions repository.