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

Redirect people to SWIG 4.1 instead of our fork #3541

Open
lissyx opened this issue Feb 25, 2021 · 1 comment
Open

Redirect people to SWIG 4.1 instead of our fork #3541

lissyx opened this issue Feb 25, 2021 · 1 comment

Comments

@lissyx
Copy link
Collaborator

lissyx commented Feb 25, 2021

NodeJS v12-v15 has been merged upstream and should be part of SWIG 4.1 ; we should direct people to use that release instead of relying on our fork (which will continue only for TC integration purposes).

@lissyx
Copy link
Collaborator Author

lissyx commented Mar 24, 2021

NodeJS v12-v15 has been merged upstream and should be part of SWIG 4.1 ; we should direct people to use that release instead of relying on our fork (which will continue only for TC integration purposes).

can I work on this issue?

Unfortunately, there is nothing to do here until SWIG does a 4.1 release.

However, if you are looking into hacking, you could have a look at #3317

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

No branches or pull requests

1 participant