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

RFC: Addon in C++ or C #3

Open
marcus-sa opened this issue Jun 12, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@marcus-sa
Copy link
Collaborator

commented Jun 12, 2019

Figure out whether or not it is actually worth writing the addon in C++

We're going to be dependent on:

  1. libvlcpp to provide up-to-date C++ headers for libvlc
  2. node-addon-api to provide up-to-date C++ headers for N-API

Related:

@issue-label-bot

This comment has been minimized.

Copy link

commented Jun 12, 2019

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.58. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@marcus-sa marcus-sa changed the title RPC: Whether or not to write the addon in C++ or C. RPC: Whether or not to write the addon in C++ or C Jun 12, 2019

@marcus-sa marcus-sa changed the title RPC: Whether or not to write the addon in C++ or C RFC: Whether or not to write the addon in C++ or C Jun 12, 2019

@marcus-sa marcus-sa changed the title RFC: Whether or not to write the addon in C++ or C RFC: Addon in C++ or C Jun 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.