-
Notifications
You must be signed in to change notification settings - Fork 40
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
Support compiling with newer v8 #17
Comments
It seems that with v8-314-devel could work, but it is not able to find it since it installs into its own sub-directory in /usr/include/. Any way of telling it to search into sub-directory? Such as passing arguments to compiler, e.g. "-I/usr/include/v8-3.14" EDIT: So I've managed to make it find it by modifying source code:
|
This this v8: https://github.com/CauldronDevelopmentLLC/v8-3.14.5/ and set The errors in your first message, such as: |
cxxstd=c++11 or cxxstd=gnu++11 solves original issue, but then there is another issue when compiling with newer version, libcbang-gnu++11-c++11.txt. I would prefer to use distribution version if possible. So I've figured I can also specify CXXFLAGS on scons command line by using ccflags="-I/usr/include/v8-3.14/". This issue may be closed as far as I am concerned, unless you want to make it work with newer V8 library which would be nice. |
I did have it working with newer versions of v8 at one point but the API is quite different and I still need to support the older versions because that's what is on Debian and the older versions are much easier to compile on Windows. |
Are you going to rebase your recent work on top of the newer-v8 branch? |
Google has really made a mess of the v8 build system. They don't seem to care if they make things difficult for projects which depend on v8 as long as it works well within Chrome's monstrous build system. There aren't any major advantages to moving to the newer v8 for cbang or CAMotics so at this point. No plans to move to the newer v8. |
Gentoo's security advisories tell that the v8 version used atm contains multiple vulnerabilities. Not sure if v8 handles any potentially hostile data in CAMotics, tho. |
CAMotics is not exposed to the Web so we don't have the same security concerns. The only time CAMoitcs executes JavaScript is when you run a TPL program. These programs are not intended to be sandboxed in the way JavaScript is sandboxed on the Web. It's more like running a Python program locally. |
The last time I built the latest cbang was almost a year ago and I was using V8 6.8. That isn't working anymore. What version of V8 are you using now? |
I'm using the version that comes with libnode-dev because that's what's packaged on Debian. It's currently version 7.8. |
@hpmachining I added an |
Thanks. I still have an error with 6.8.
I'll look into building 7.8 when I get some time. Thanks again! |
Is that the only error? It could easily be
If there were just a few of these it might be worth supporting the older version. |
That worked! Thanks. |
I've been working on building with the current v8 (9.0) because I was having issues rebuilding the older v8 against the latest icu (68.2). I was able to build cbang by adding |
Create an issue in CAMotics with the build errors. I think I was able to build CAMotics with |
It looks like an API change is coming in V8 version 10. See this link: V8 API changes - Ongoing and Planned Changes I am getting this error trying to build against it:
I think an |
Does the commit I just made work? |
Yes, that worked. Thank you. It builds complete without error. |
Edit: This ticket is about supporting newer v8 versions.
v8-devel-5.2.258-7.fc25.x86_64
The text was updated successfully, but these errors were encountered: