Skip to content

No C/C++ extension on the Open VSX marketplace (for Arch Linux, VSCodium, etc.) #6518

Closed

Description

Type: General

Describe the bug

  • OS and Version: Linux Deepin 2020
  • VS Code Version: VSCodium 1.51.1
  • C/C++ Extension Version: none
  • Other extensions you installed (and if the issue persists after disabling them): python
  • A clear and concise description of what the bug is.
    There is no a c/c++ extension on VSCodium marketplace....

Expected behavior
Would you publish one to open-vsx.org in addition to the VS Code Marketplace. The publishing process is documented in the Open VSX Wiki.

Activity

  1. sean-mcmanus commented on Nov 16, 2020

    @sean-mcmanus
    Contributor

    Our license doesn't support vscodium, only VS Code. We've had previous issues like this. Maybe we could keep this open as a request to change our license?

    In particular, see https://github.com/microsoft/vscode-cpptools/tree/master/RuntimeLicenses

  2. BackMountainDevil commented on Nov 16, 2020

    @BackMountainDevil
    Author

    Thanks for your answer. Actually, it is impolite to ask your company you change the license. Maybe just like VSCodium, rebuild a clean one. Is that ok?
    According to this comment from a Visual Studio Code maintainer:

       When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, 
    we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, 
    logo, etc.), and then produce a build that we release under our license.
        When you clone and build from the vscode repo, none of these endpoints are configured in the 
    default product.json. Therefore, you generate a “clean” build, without the Microsoft 
    customizations, which is by default licensed under the MIT license
    

    Thanks all the time.

  3. sean-mcmanus commented on Nov 16, 2020

    @sean-mcmanus
    Contributor

    A "clean" C/C++ extension with just the MIT license (i.e. TypeScript on GitHUb) would not include the cpptools/cpptools-svr binaries listed under https://github.com/microsoft/vscode-cpptools/tree/master/RuntimeLicenses , so it wouldn't be usable. Therefore, the license would need to be changed for those binaries.

  4. changed the title [-]There is no a c/c++ extension on VSCodium marketplace[/-] [+]No C/C++ extension on the Open VSX marketplace (for Arch Linux, VSCodium, etc.)[/+] on Nov 16, 2020
  5. BackMountainDevil commented on Nov 17, 2020

    @BackMountainDevil
    Author

    You can use Clangd extension in VScodium.

    The Clangd extension requires the clangd language server. Emm, is that work with gcc??

  6. modified the milestones: Triage, Backlog on Nov 18, 2020
  7. removed
    more votes neededIssues that have been postponed until more community members upvote it
    on Nov 18, 2020
  8. github-actions commented on Nov 18, 2020

    @github-actions

    This feature request has received enough votes to be added to our backlog.

  9. BackMountainDevil commented on Nov 22, 2020

    @BackMountainDevil
    Author

    Here are some solution I found:

    1. Just gcc command line like this
    $ gcc filename
    $ ./a.out

    I use that for less operation for a few days
    2. just make command like this

    $ make
    $ ./a.out

    But you need to make a Makefile before like this one, this will use less word

    a.out:tmp.c
    	gcc tmp.c  -Wall -Wextra -pedantic -std=c99
    1. Use extendsion called Code Runner, install it . Make Sure it check in Setting "Run in Termianl"
      see this
  10. chintan-mishra commented on Dec 1, 2020

    @chintan-mishra

    @rouisibra

    Which C and C++ compiler are you using with Clangd plugin?

    LLVM Clang or GCC?

    How is the performance, and code completion experience?

  11. bobbrow commented on Dec 2, 2020

    @bobbrow
    Contributor

    This feature request has received enough votes to be added to our backlog.

    Unfortunately, this issue is not something that we are going to be able to address. We've discussed the licensing terms with our product managers and legal team and it doesn't look like anything is going to change (at least for now). I'm closing this issue to set the correct (though understandably disappointing) expectations for folks.

  12. G2G2G2G commented on Jan 11, 2021

    @G2G2G2G

    Microsoft obviously doesn't <3 open source

  13. locked and limited conversation to collaborators on Jan 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions