-
Notifications
You must be signed in to change notification settings - Fork 618
[javascript][v8] Support for swig 4.1.0 #1064
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
Conversation
|
SWIG 4.0.2 does not work with node v12.x (v8 7.8) & higher, so I verified it with node v10.x (v8 6.8). node v10.24.1 (v8 6.8.275.32) (EoL) I will test node v12.x v14.x v16.x. It may take some time. |
fda8d88 to
454bd9a
Compare
|
I'm adding modifications that I found while testing to the mraa and upm patches. node 12.22.1 (v8 7.8.279.23) node v14.16.1 (v8 8.4.371.19) node v16.1.0 (v8 9.0.257.24) upm: ref eclipse-upm/upm#703 |
In swig 4.1.0, the complicated handling of "SWIG_V8_VERSION" has been cleaned up a bit. I made the same changes as in this swig. Signed-off-by: Hirokazu MORIKAWA <[email protected]>
454bd9a to
f119e36
Compare
I've heard from the SWIG maintainers and while I'm not convinced about the need to support the obsolete V8, I understand it. SWIG is still as it is for now. The handling of V8_VERSION is complicated. I have modified the V8 related code to work with SWIG on the MRAA side and the UPM side. |
|
@nxhack thank you for checking the latest node.js versions. You will need to accept the Eclipse Committer Agreement (ECA) in order for us to merge these changes. It would also help to add a patch file in the MRAA project with the SWIG changes so we can apply that during our CI checks, but that's something we can worry about later. |
|
@Propanu |
|
@Propanu |
Propanu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for clarifying this will work with the latest versions of Node.js and SWIG 4.1.0 as is.
|
I am very sorry not to be able to follow regularly your work. I am building raspberryPi debian Oses with mraa and upm at the moment. I can spend some time on tests. I feel that we are very close to a clean build. Let me know what tests you want me to make; my goal is to build in a bullseye with the most recen node and swig if possible. Test OK node16 commented in #1040 |
|
@Propanu I can see it is approved but I confirm that the patch works perfectly with the following context Linux myPi 5.12.6-v7 #1 SMP Mon May 31 18:19:07 CEST 2021 armv7l GNU/Linux
SWIG Version 4.1.0
gcc version 10.2.1 20210110 (Debian 10.2.1-6)
node v16.2.0
npm 7.15.0
cmake .. -Wno-dev -DCMAKE_INSTALL_PREFIX=/usr -DENABLEEXAMPLES=0 -DBUILDSWIGNODE=ON -DSWIG_EXECUTABLE=/usr/local/bin/swig -DV8_ROOT_DIR=/usr/local/include/node -DNODE_ROOT_DIR=/usr/local/include/node -DPYTHON2LIBS_FOUND=FALSE -DPYTHON2INTERP_FOUND=FALSE -DWERROR=OFF -DCMAKE_CXX_STANDARD=17
|
|
Checked the patch for mrra with node 16.11.0 . Works perfectly |
Support for swig 4.1.0
In swig 4.1.0, the complicated handling of "SWIG_V8_VERSION" has been cleaned up a bit. I made the same changes as in this swig.
Signed-off-by: Hirokazu MORIKAWA [email protected]