Re: [v8-users] Re: Building v8 shared library on windows

obviously) >>>>>>> >>>>>>> * python tools\dev\v8gen.py -b x64.release msvc -- is_clang=false >>>>>>> is_component_build=true* >>>>>>> >>>>>>> Run the build, which should comple

Re: [v8-users] Re: Building v8 shared library on windows

>> >>>>>> * python tools/run-tests.py --outdir out.gn/msvc >>>>>> <http://out.gn/msvc>* >>>>>> >>>>>> You should find the resulting v8.dll, along with supporting dlls and >>>>>> .lib files, in the .\out.

Re: [v8-users] Re: Building v8 shared library on windows

t.gn/msvc >>>>>> <http://out.gn/msvc>* >>>>>> >>>>>> You should find the resulting v8.dll, along with supporting dlls and >>>>>> .lib files, in the .\out.gn\msvc directory. >>>>>> >>>>>&

Re: [v8-users] Re: Building v8 shared library on windows

t;>> I haven't tested much beyond running the tests and doing a few ad-hoc >>>>> D8 experiments, and obviously this is unsupported/untested upstream >>>>> (where >>>>> the are no bots building/testing/fuzzing this configuration). >>

Re: [v8-users] Re: Building v8 shared library on windows

ted/untested upstream (where >>>> the are no bots building/testing/fuzzing this configuration). >>>> >>>> I'll tidy this up, open a CL, and see if this is something we can get >>>> upstreamed, as several folks seem to want this option. Assuming

[v8-users] Re: Building v8 with msvc 2019 failed

By installing a python package it has been solved. python -m pip install pywin32 I just make visual studio solution file by 'call gn gen --ide=vs2019 out.gn/x86.release --args="is_clang=false is_debug=false use_glib=false is_component_build=true v8_use_external_startup_data=true v8_static_libr

Re: [v8-users] Re: Building v8 shared library on windows

es, >>> is would then be beholden on us (the V8 community) to keep it working. >>> (Personally, it seems to me like the only long-term sustainable solution >>> for cross-compiler support is a C-based API, similar to N-API for Node.js, >>> but I doubt there's much appetite for this currentl

Re: [v8-users] Re: Building v8 shared library on windows

stainable solution >> for cross-compiler support is a C-based API, similar to N-API for Node.js, >> but I doubt there's much appetite for this currently). >> >> - Bill >> >> >> On Friday, December 20, 2019 at 10:29:07 AM UTC-8, Ivan Pizhenko wrote: >>

Re: [v8-users] Re: Building v8 shared library on windows

t. Thank you. I will try to apply similar patch locally to >> the 7.8.279.23, since I am allowed to use only “stable” versions of V8. >> >> - Ivan >> >> >> >> >> >> *From: *'Bill Ticehurst' via v8-users >> *Sent: *Friday, D

RE: [v8-users] Re: Building v8 shared library on windows

;mailto:ivan.pizhe...@genesys.com> Sent: Friday, December 20, 2019 20:29 To: v8-users@googlegroups.com<mailto:v8-users@googlegroups.com> Subject: RE: [v8-users] Re: Building v8 shared library on windows Oh, that’s great. Thank you. I will try to apply similar patch locally to the 7.8.279.

Re: [v8-users] Re: Building v8 shared library on windows

; On Friday, December 20, 2019 at 10:29:07 AM UTC-8, Ivan Pizhenko wrote: >> >> Oh, that’s great. Thank you. I will try to apply similar patch locally to >> the 7.8.279.23, since I am allowed to use only “stable” versions of V8. >> >> - Ivan >> >> >> >&

Re: [v8-users] Re: Building v8 shared library on windows

d to use only “stable” versions of V8. > > - Ivan > > > > > > *From: *'Bill Ticehurst' via v8-users > *Sent: *Friday, December 20, 2019 20:02 > *To: *v8-users > *Subject: *[v8-users] Re: Building v8 shared library on windows > > > > FWI

[v8-users] Re: Building v8 shared library on windows

There are a couple of things I don't understand: -How can I use V8 with VS2019, if working DLLs can't be obtained? -Will the MSVC way ever be fixed? I cannot use precompiled DLLs if I don't know if I will be able to update them to a newer version of V8, that wouldn't be sustainable. Thank you ver

RE: [v8-users] Re: Building v8 shared library on windows

<mailto:v8-users@googlegroups.com> Subject: [v8-users] Re: Building v8 shared library on windows FWIW: I played around with the last night for a couple hours and got a release build working using a "component build" and MSVC. It was mostly moving some inline functions and adding s

RE: [v8-users] Re: Building v8 shared library on windows

:43 To: v8-users<mailto:v8-users@googlegroups.com> Subject: Re: [v8-users] Re: Building v8 shared library on windows Just the header file for the public V8 API (https://chromium.googlesource.com/v8/v8.git/+/refs/heads/master/include/v8.h#18<https://chromium.googlesource.com/v8/v8.git/+/refs/

[v8-users] Re: Building v8 shared library on windows

FWIW: I played around with the last night for a couple hours and got a release build working using a "component build" and MSVC. It was mostly moving some inline functions and adding some V8_EXPORT_PRIVATE statements (which effectively add the "__declspec(dllexport)" statements to expose functi

Re: [v8-users] Re: Building v8 shared library on windows

gest to V8 developers to keep all >> public V8 APIs w/o any STL stuff for the sake of better integration with >> different compilers, which with very high probability have different STL >> implementations than libc++. >> >> - Ivan >> >> >> >> &g

Re: [v8-users] Re: Building v8 shared library on windows

blic V8 APIs w/o any STL stuff for the sake of better integration with > different compilers, which with very high probability have different STL > implementations than libc++. > > - Ivan > > > > > > *From: *'Bill Ticehurst' via v8-users > *

Re: [v8-users] Re: Building v8 shared library on windows

7; via v8-users > *Sent: *Wednesday, December 18, 2019 20:22 > *To: *v8-users > *Subject: *[v8-users] Re: Building v8 shared library on windows > > > > I believe this is still mostly correct - (some filenames might be out of > date, but should give you a general starting p

RE: [v8-users] Re: Building v8 shared library on windows

a v8-users<mailto:v8-users@googlegroups.com> Sent: Wednesday, December 18, 2019 20:22 To: v8-users<mailto:v8-users@googlegroups.com> Subject: [v8-users] Re: Building v8 shared library on windows I believe this is still mostly correct - (some filenames might be out of date, but should give

[v8-users] Re: Building v8 shared library on windows

I believe this is still mostly correct - (some filenames might be out of date, but should give you a general starting point). If you're already building V8 successfully with MSVC, you should be able to skip down to the "Embedding V8 into a custom application" part. https://medium.com/angular-in

[v8-users] Re: Building v8 shared library on windows

I'm not clear on what is needed to fix this. The bug has been open quite a while (see https://bugs.chromium.org/p/v8/issues/detail?id=8791). On Tuesday, December 17, 2019 at 12:44:14 PM UTC-8, Ivan Pizhenko wrote: > > Hi Bill, so what needs to be fixed to get DLL build (i.e. > is_component_build

[v8-users] Re: Building v8 shared library on windows

Ok Bill Then I'll build it statically with "is_component_build = false". I don't really need them to be dynamic, I just need them to work. What file extension should I look for? .lib? Thank you -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- Yo

[v8-users] Re: Building v8 shared library on windows

Hi Bill, so what needs to be fixed to get DLL build (i.e. is_component_build=true) built successfully with MSVC compiler? I've recently run into the same linking issue with DLL build compiled using clang. And to say truth, it's weird that DLL build works only with clang. p.s. I cannot use prebu

[v8-users] Re: Building v8 shared library on windows

The v8 libraries from nuget can be used well with VC2017. Thats all i know. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this gro

[v8-users] Re: Building v8 shared library on windows

To be clear, NuGet is a Microsoft run package manager, but "Microsoft" doesn't offer any pre-built V8 binaries. A user account named "pmed" created/uploaded that package, not a Microsoft account. If you are building V8 in a default manner with Clang as it appears, then you can't link it with a

[v8-users] Re: Building v8 shared library on windows

Note that Microsoft also offers prebuild verrions of v8 via the package manager or direct to download. I.e. https://www.nuget.org/packages/v8-v140-x64/ click on "Download" at the right and rename the archive to zip. Works well for me. -- -- v8-users mailing list v8-users@googlegroups.com http:

[v8-users] Re: Building v8 shared library on windows

> > Nagendra, what do you mean with "using libc++ insead of stdlibc++ when > using the host_cpu toolchain"? I don't get it. > Right now I'll compile with "is_clang = true" and "use_custom_libcxx_for_host = true". Thank you both. -- -- v8-users mailing list v8-users@googlegroups.com http://gr

[v8-users] Re: Building v8 shared library on windows

Ok I'm still going to compile with "is_clang = true", but I'll also add Nagendra's "use_custom_libcxx_for_host = true". Don't expect me to disappear from this platform. Thank you very much -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You rec

[v8-users] Re: Building v8 shared library on windows

You can also try building , setting the gn argument use_custom_libcxx_for_host = true Argument overview: Use libc++ instead of stdlibc++ when using the host_cpu toolchain, even if use_custom_libcxx is false. This is useful for cross-compiles where a custom toolchain for the target_cpu has be

[v8-users] Re: Building v8 shared library on windows

> I'll try compiling with "is_clang = true" Shouldn't hurt, although my suspicion is since you didn't override it, it defaulted to true, due to these lines from "build/config/BUILDCONFIG.gn": is_clang = current_os != "linux" || (current_cpu != "s390x" && current_cpu != "s390" &&

[v8-users] Re: Building v8 shared library on windows

OP should also take a look at this thread https://groups.google.com/forum/#!topic/v8-users/Jb1VSouy2Z0 I'm facing the same linking issue on using v8 shared libs on CentOS 8 -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this messa

[v8-users] Re: Building v8 shared library on windows

While you wait for someone *much* more knowledgeable to reply... :-) I'm not brave enough to build on Windows, but presumably many things are similar. > I'm following the guide. More than one guide (or parts of guide) to follow! :-) Maybe you followed this one: https://v8.dev/docs/embed In wh

[v8-users] Re: Building v8 shared library on windows

Sorry for the late answer. I don't know if I'm building with clang or msvc. I'm following the guide. Meanwhile I managed to build dll files, but I can't make them work in a VS2019 project because of two errors: -the linker can't resolve external symbols for NewDefaultPlatform -Even if I comment ou

[v8-users] Re: Building v8 shared library on windows

Are you building with MSVC or Clang? The "component" build of V8 has some issues with MSVC, but I believe should just work if using Clang. Note: "component" build means a DLL build. Check that "is_component_build = true" in your output folder's args.gn file, and then you should see v8*.dll file

[v8-users] Re: Building V8 android ia32 on ubuntu 16.04.5

I don't know what's the proper way to specify a different Android NDK version, sorry. Maybe someone else might chime in with an advice? On Friday, December 21, 2018 at 9:35:14 AM UTC+1, ant...@coherent-labs.com wrote: > > Thank you. > I manage to make a build. > But I had some issues (because of

[v8-users] Re: Building V8 android ia32 on ubuntu 16.04.5

Thank you. I manage to make a build. But I had some issues (because of the "android-17" setting which I am using) and I had to replace the /third_party/android_ndk/sysroot/usr/include/ with the respective android-17 in e.g., *android-ndk-r10e\platforms\android-17\arch-arm\usr\include*, which is

[v8-users] Re: Building V8 android ia32 on ubuntu 16.04.5

Also, not sure what kind of platform are you targeting that runs Android on ia32. If you simply want to run/debug an arm version of V8 on your Ubuntu machine, you can create a simulator build by supplying the *v8_target_cpu* arg. For instance see the gn args

[v8-users] Re: Building V8 android ia32 on ubuntu 16.04.5

Hi, The correct value for *target_cpu* when you're targeting ia32 is "x86". You can obtain info on the valid values for it by using gn help target_cpu You can use the "gn help" with other args like *target_os*, or eventually list the available args by gn args --list Cheers, Maya On Thurs

Re: [v8-users] Re: Building V8 on Windows with Visual Studio 2017

"mainCRTStartup is where Windows tries to call to start a program. It is in the C runtime library ("CRT") and that is the thing that calls main() or winMain(). " So it's because of the wrong settings of those projects? I'm starting a new fresh sync of the v8 source and will try again as my curr

Re: [v8-users] Re: Building V8 on Windows with Visual Studio 2017

I'm building V8 static libs using VS2017 too and I'm having the same issue. Have you worked out any solution? On Monday, July 9, 2018 at 11:44:06 PM UTC+8, Mike Moening wrote: > > At the very end of the build I received this error: > > *C:\Dev\common\v8>ninja -C out.gn/x64.release

Re: [v8-users] Re: Building V8 on Windows with Visual Studio 2017

Did you ever come up with a solution? On Monday, July 9, 2018 at 10:48:27 AM UTC-5, Mike Moening wrote: > > Also the *v8_base.lib* or any other .lib files we not created. > > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this mes

Re: [v8-users] Re: Building V8 on Windows with Visual Studio 2017

Also the *v8_base.lib* or any other .lib files we not created. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop r

Re: [v8-users] Re: Building V8 on Windows with Visual Studio 2017

At the very end of the build I received this error: *C:\Dev\common\v8>ninja -C out.gn/x64.release* *ninja: Entering directory `out.gn/x64.release'* *[1/7] LINK cctest.exe cctest.exe.pdb* *FAILED: cctest.exe cctest.exe.pdb* *ninja -t msvc -e environment.x64 -- ../../third_party/llvm-build/Release+

Re: [v8-users] Re: Building V8 on Windows with Visual Studio 2017

I didn't see you post until now. I solved the issue running this: C:\Dev\common\v8\tools\clang\scripts>*python.bat update.py* Which brought down all the bin files I needed into *third_party/llvm-build* and now it's compiling! > > -- -- v8-users mailing list v8-users@googlegroups.com http://gr

Re: [v8-users] Re: Building V8 on Windows with Visual Studio 2017

See https://github.com/v8/v8/wiki/Using-Git. Since something seems messed up with your gclient install (which will fetch clang-cl.exe), try the steps in 'How to start' for a clean checkout. Hope that helps. On Tue, Jul 3, 2018 at 8:52 PM, Mike Moening wrote: > Oh and I've tried running: *gclient

[v8-users] Re: Building V8 on Windows with Visual Studio 2017

Oh and I've tried running: *gclient sync *from my v8 directory: C:\Dev\common\v8>gclient sync C:\Dev\common\.gclient_entries missing, .gclient file in parent directory C:\Dev\common might not be the file you want to use. and it doesn't seem to bring down *third_party/llvm-build* Should it?? What

[v8-users] Re: Building v8 as a static library generates build errors, but ptoduces usable libraries

On Monday, 7 May 2018 16:16:46 UTC-4, Steven An wrote: > > Ah OK. As others have discovered, you simply need to link in both > v8_base_0.lib and v8_base_1.lib and it works now. Great! > Yes, for most apps you will need all of them: icui18n.lib icuuc.lib v8_base_0.lib v8_base_1.lib v8_external_

[v8-users] Re: Building v8 as a static library generates build errors, but ptoduces usable libraries

Ah OK. As others have discovered, you simply need to link in both v8_base_0.lib and v8_base_1.lib and it works now. Great! On Monday, May 7, 2018 at 3:57:31 PM UTC-4, Steven An wrote: > > Hi all, > I'm getting similar errors on Windows, VS 2017, when building for static > link: > > [520/529] LIN

[v8-users] Re: Building v8 as a static library generates build errors, but ptoduces usable libraries

Hi all, I'm getting similar errors on Windows, VS 2017, when building for static link: [520/529] LINK cctest.exe cctest.exe.pdb FAILED: cctest.exe cctest.exe.pdb C:/Users/stevenan/gh/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../build/toolchain/win/tool_wrapper.py link-wrapper envi

Re: [v8-users] Re: Building v8 5.9 on Centos 6

GCC 4.8.4 definitely works, so 4.8.2 is probably fine too. On Fri, Sep 8, 2017 at 2:57 AM, Chris Hillery wrote: > Thanks for the reply, Jakob. As I mentioned, I do have gcc 4.8.2 already > running on Centos 6, which should be new enough to build v8 5.9, correct? > > -- > -- > v8-users mailing li

Re: [v8-users] Re: Building v8 5.9 on Centos 6

Thanks for the reply, Jakob. As I mentioned, I do have gcc 4.8.2 already running on Centos 6, which should be new enough to build v8 5.9, correct? -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscri

Re: [v8-users] Re: Building v8 5.9 on Centos 6

All old versions of all tools should still be available. However, it's possible that they won't solve your problem: e.g. when you use a compiler that's old enough to run on CentOS 6, then it will probably be too old to support the C++11 features that V8 uses nowadays. Your best bet is probably to

[v8-users] Re: Building v8 5.9 on Centos 6

The binary tools aren't in git; they're downloaded by various other build scripts. I have tried rolling depot_tools back to an earlier time, but most of the problematic tools (clang, binutils, sysroot) aren't actually from there; they're from other projects embedded in v8 source code. I've als

[v8-users] Re: Building v8 5.9 on Centos 6

It looks like it's a git repo, I would guess you be able to just check out the tools that were available at the same time as the version of V8 that you want to build? --Zac On Wednesday, September 6, 2017 at 10:27:12 PM UTC-7, Chris Hillery wrote: > > I've seen several earlier threads on varian

[v8-users] Re: Building V8 on windows

Figured out, i was missing few components from windows 10 SDK, reinstalled it from https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you ar

[v8-users] Re: Building V8 on windows

Rong Jie, I had the environment variable set to 0. Thank you on the pointer w.r.t. goma. I edited args.gn and set use_goma = false; which was true before. Now when i try to build, i get c:\tools\v8>ninja -C out.gn/mav8 ninja: Entering directory `out.gn/mav8' [1/1] Regenerating ninja files [29/

[v8-users] Re: Building V8 on windows

Thank you Rong Jie. I do have set it as you mentioned. (missed to call out before). Any other pointers? On Monday, April 24, 2017 at 7:33:27 PM UTC+5:30, Rong Jie wrote: > > You should set DEPOT_TOOLS_WIN_TOOLCHAIN=0 before running gn and ninja so > that goma is not used (only available for Goog

[v8-users] Re: Building V8 on windows

You should set DEPOT_TOOLS_WIN_TOOLCHAIN=0 before running gn and ninja so that goma is not used (only available for Googler) -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Grou

[v8-users] Re: Building v8 with Visual Studio 2015 on Windows 10

Yes. They're separate commands. Thanks, I didn't notice that. On Friday, 31 March 2017 04:09:44 UTC+5:30, james@lafargeholcim.com wrote: > > This is not correct: fetch v8git checkout branch-heads/4.8 > > Since one cannot fetch "v8git" I assume you meant two separate lines there: > > fetch v8

[v8-users] Re: Building v8 with Visual Studio 2015 on Windows 10

This is not correct: fetch v8git checkout branch-heads/4.8 Since one cannot fetch "v8git" I assume you meant two separate lines there: fetch v8 git checkout branch-heads/4.8 ;) On Sunday, March 5, 2017 at 12:56:15 AM UTC-5, Gautham B A wrote: > > Hi all, > > I was able to build v8 (branch 4.8)

[v8-users] Re: Building v8 with Visual Studio 2015 on Windows 10

Hi all, I was able to build v8 (branch 4.8) on Windows 10 using Visual Studio 2015. I followed these instructions - set DEPOT_TOOLS_WIN_TOOLCHAIN=0 set GYP_MSVS_VERSION=2015 set GYP_GENERATORS=msvs wget https://storage.googleapis.com/chrome-infra/depot_tools.zip -OutFile depot_tools.zip Expand-A

[v8-users] Re: Building V8 on FreeBSD

El martes, 4 de octubre de 2016, 10:57:18 (UTC-5), Jose Madrigal escribió: > > Hello !!! > > I been trying to build V8 on FreeBSD due the ports are not updated to the > recent version of v8 but I have struggled a lot. I wonder if someone > already build v8 on FreeBSD that could point me out in

Re: [v8-users] Re: Building V8 on FreeBSD

I have the same problem and running the command: python -u tools/mb/mb.py gen -f infra/mb/mb_config.pyl -m developer_default -b x64.release out.gn/x64.release I got this error: Writing """\ is_debug = false target_cpu = "x64" """ to /home/crugnola/Documents/git/public/v8/out.gn/x64.release/args.g

[v8-users] Re: Building v8

Hi all, I have the same problem on windows: I don't get the import .lib libraries for v8_libbase, v8_libplatform, etc... The building process only produces v8.dll.lib, icui18n.dll.lib and icuuc.dll.lib My setup is: - v8 head of 5.4 branch - Windows 10 - Visual Studio 2013 Any suggestions on ho

[v8-users] Re: Building v8

After finishing the ninja build step, I just ran: make native library=shared and the .so libs *eventually* appear in out/native/lib.target PS. I had no idea about the "is_component_build=true" method :) On Thursday, September 15, 2016 at 11:07:57 AM UTC-4, Travis Sharp wrote: > > I've followe

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

If you build for x87, mips (big endian), ppc, or s390, use gyp, the rest is on gn. On Tue, Oct 18, 2016 at 11:04 PM Zac Hansen wrote: > How do I find out what the current supported build process is for a > platform? I've been told "if gn doesn't work, use gyp, because it's > supported until gn

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

How do I find out what the current supported build process is for a platform? I've been told "if gn doesn't work, use gyp, because it's supported until gn works on a platform".. but when neither works, I don't know which to ask about how to use. Thank you for all your help. --Zac On Tue, Oct 1

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

I tried to fix this here but concluded it's "not supported": https://codereview.chromium.org/22382003/ On Tue, Oct 18, 2016 at 9:33 AM Zac Hansen wrote: > "component build" = dylib? > > It's always worked fine - but this error is new. > > Linking against the static version takes forever, so dyli

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

"component build" = dylib? It's always worked fine - but this error is new. Linking against the static version takes forever, so dylibs are the only way to go. On Tue, Oct 18, 2016 at 12:31 AM, Jochen Eisinger wrote: > I'm surprised that the component build with gyp on mac ever worked for > yo

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

I'm surprised that the component build with gyp on mac ever worked for you, it never did for me :-/ On Tue, Oct 18, 2016 at 5:32 AM Zac Hansen wrote: > manually copying the file into /usr/local/lib works. Someone said it > might have to do with the "install_name" being /usr/local/lib, but I do

[v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

manually copying the file into /usr/local/lib works. Someone said it might have to do with the "install_name" being /usr/local/lib, but I don't really understand what this means. Also, it seems broken that copying a file into /usr/local is required for part of the build. --Zac On Monday, Oc

[v8-users] Re: Building v8 on ubuntu 16.04

have you tried just building it from there? On Tuesday, October 11, 2016 at 9:00:39 AM UTC-7, nicktook wrote: > > I am trying to build v8 but it is failing on the 'fetch v8' command. This > is the output: > > Running: /usr/bin/python /home/bryan/v8/v8Oct2016/depot_tools/gclient.py > root > Runn

Re: [v8-users] Re: Building V8 on FreeBSD

If you run the mb.py command directly (python -u tools/mb/mb.py gen -f infra/mb/mb_config.pyl -m developer_default -b x64.release out.gn/x64.release) does it print a more verbose error message? On Tue, Oct 4, 2016 at 9:17 PM Jose Madrigal wrote: > I been trying follow the instructions shown in >

[v8-users] Re: Building V8 on FreeBSD

I been trying follow the instructions shown in https://github.com/v8/v8/wiki/Building%20with%20GN At the point where I must use: > tools/dev/v8gen.py x64.release raise a error: Traceback (most recent call last): File "tools/dev/v8gen.py", line 304, in sys.exit(gen.main()) File

Re: [v8-users] Re: Building V8 engine for Windows CE6-ARM target

V8 doesn't support WinCE, never has, so it is unlikely you'll find documentation on the subject. WinCE is rather old, so before trying anything to get V8 building on this target, you may want to ensure your CPU meets the minimum requirements: ARMv6 and VFPv2. Rodolph On Tue, 27 Sep 2016 at 14:57

[v8-users] Re: Building V8 engine for Windows CE6-ARM target

Hello, Any reply in this regard would be of great help. I want to know if we can build the V8 engine code on Win CE6 ARM target or not. /Avadhut. On Tuesday, September 27, 2016 at 12:33:56 PM UTC+5:30, Avadhut Bhangui wrote: > > Hello, > > I'm trying to build V8 engine for Win CE6-ARM target.

[v8-users] Re: Building V8 Libraries Help. (Repositories Offline?)

Hello All, Awesome, that is great news! Thank you guys for the quick answers, I really appreciate it! Thanks for the help, Allen On Tuesday, July 19, 2016 at 6:33:07 PM UTC-4, Allen Ng wrote: > > Hello all, > > I do not know if this is the right place for this but it can't hurt to > try! I a

[v8-users] Re: Building V8 Libraries Help. (Repositories Offline?)

Hi Allen, I'm with the IBM team supporting the S390 port of V8. Which version of V8 did you want to build? The building V8 libraries tutorial you mentioned was updated yesterday with the newer locations of make dependencies. However, they are for building older levels of V8 (3.14 / 3.28)

Re: [v8-users] Re: Building V8 Fails with MinGW-w64

On 1/24/2016 10:53 PM, Yang Guo wrote: Looks like you are trying to build V8 with a compiler that does not support C++11. Thank you for your reply. I am using gcc 5.3.0 and according to https://gcc.gnu.org/onlinedocs/gcc-5.3.0/gcc/Standards.html I need to set an option of -std=c++11 so I'll try

[v8-users] Re: Building V8 Fails with MinGW-w64

Looks like you are trying to build V8 with a compiler that does not support C++11. On Monday, January 25, 2016 at 4:58:46 AM UTC+1, ig...@lucee.org wrote: > > Hi, > > I'm trying to build v8 version 4.3.66 with MinGW-w64 and I'm getting > errors which I can not understand. > > It'd be greatly app

Re: [v8-users] Re: building V8: Getting error running python build\gyp_v8

Do you have multiple copies of Visual Studio installed? If so, set the GYP_MSVS_VERSION environment variable to "2013" and then run build\gyp_v8. Next, make sure that you are using the Visual Studio 2013 Developer Command Prompt and not PowerShell or an ordinary command prompt. I hit these erro

Re: [v8-users] Re: building V8: Getting error running python build\gyp_v8

> > > > > > *From:* gamert...@gmail.com [mailto:gamert...@gmail.com > ] > *Sent:* Wednesday, August 5, 2015 8:29 AM > *To:* v8-u...@googlegroups.com > *Subject:* RE: [v8-users] Re: building V8: Getting error running python > build\gyp_v8 > > > > Hi

RE: [v8-users] Re: building V8: Getting error running python build\gyp_v8

Is this expected? I remember this happened the first time as well. From: gamertag2...@gmail.com [mailto:gamertag2...@gmail.com] Sent: Wednesday, August 5, 2015 8:29 AM To: v8-users@googlegroups.com Subject: RE: [v8-users] Re: building V8: Getting error running python build\gyp_v8 Hi

RE: [v8-users] Re: building V8: Getting error running python build\gyp_v8

Behalf Of Michael Hablich Sent: Wednesday, August 5, 2015 12:22 AM To: v8-users Subject: [v8-users] Re: building V8: Getting error running python build\gyp_v8 I am confused: python build\gyp_v8 generates the project files. Do you get an error while running this command or actually building th

[v8-users] Re: building V8: Getting error running python build\gyp_v8

I am confused: python build\gyp_v8 generates the project files. Do you get an error while running this command or actually building the solution? Which VS version are you using (simultaneously)? There we recent threads on this group about building on Windows. Have you already checked them? O

[v8-users] Re: Building v8 on Windows with VS2013

I can confirm I ran into the same problems, with the same solutions as Michael Collins described. On Thursday, July 2, 2015 at 12:40:44 AM UTC-7, Michael Hablich wrote: > > Hi Michael, > > thanks for investigating. I will add these information to the wiki post. > What branch/commit have you buil

[v8-users] Re: Building v8 on Windows with VS2013

Hi Michael, thanks for investigating. I will add these information to the wiki post. What branch/commit have you build following your instructions? Cheers, Michael On Wednesday, July 1, 2015 at 8:07:28 PM UTC+2, Michael Collins wrote: > > In follow up to my question a couple of weeks ago, I fin

Re: [v8-users] Re: Building v8

See my response on the other thread. As far as I can see the documentation is correct. On Sun, Dec 16, 2012 at 4:29 PM, wrote: > I'm having the same exact problem. Everything was done by the book, and > everything was double checked. Is the guide in need of being updated? > Because the file tha

[v8-users] Re: Building v8

I'm having the same exact problem. Everything was done by the book, and everything was double checked. Is the guide in need of being updated? Because the file that it claims to require simply isn't there (build/gyp_v8/__main__py). This was after 2 successfull downloads of each item that they ca

[v8-users] Re: building v8.lib with vs2005 - error C2220 caused by warning C4244 on bignum.cc

Hi Søren, I was able to get the compilation to work by changing the compilation flags so that warnings were no longer treated as errors. However, the original data truncation warnings still remain. Is that something the folks at Google would consider a bug? -- Daryl Shockey -- v8-users mailing

Re: [v8-users] Re: building v8.lib with vs2005 - error C2220 caused by warning C4244 on bignum.cc

Hi, The compilation flags are defined in the SConstructs file, see http://code.google.com/p/v8/source/browse/branches/bleeding_edge/SConstruct?r=6302#323. Try to change these, and file a bug if there are compilation issues with Visual Studio 2005. Regards, Søren On Thu, Jan 13, 2011 at 18:47, ds

[v8-users] Re: building v8.lib with vs2005 - error C2220 caused by warning C4244 on bignum.cc

I'm getting this error too. This is the first time I've attempted to build V8 and it's the first time I've worked with scons, so I'm not really sure how to go about fixing this. I'm using Visual Studio 2005 on a Windows 7 box. In traditional C++ headers, I can disable the warning with a #pragma sta

[v8-users] Re: building V8 shared object on MinGW

Kory, I couldn't help but notice that the SO that you're trying to link is The Ruby Racer, and so this is probably not a V8 build problem. See comments below. On Jul 30, 6:54 pm, Korey wrote: > there are a couple threads from last year on getting V8 to compile on > mingw, steps I've taken so far

Re: [v8-users] Re: Building v8 for MIPs platform.

Hi Nilima - At this point I plan to start migrating our code forward to the latest google source next week. Depending on what bugs get either fixed or uncovered this week, that might get delayed by a bit. But I am hoping to start soon. I don't have any suggestion about the size. v8 aims for hi

Re: [v8-users] Re: Building v8 for MIPs platform.

Was able to get compiling for Mips after playing with some compilation flags. But still I do need to port for source code portion. One question, When you are planning to sync up with Google's v8 source code. Since now I can see there are some code in Google's v8 source code which is different than

Re: [v8-users] Re: Building v8 for MIPs platform.

On 16/07/2010 12:36, Nilima Chavan wrote: > Hi Paul, > > Thanks again. > I will definetly consider the option of porting this to mips Big-endian > architecture. > But only thing worrying me now is the size of v8 library which is around 5 > MB after removing debug option. > Such a big size is not s

Re: [v8-users] Re: Building v8 for MIPs platform.

Hi Paul, Thanks again. I will definetly consider the option of porting this to mips Big-endian architecture. But only thing worrying me now is the size of v8 library which is around 5 MB after removing debug option. Such a big size is not suitable for the embedded devices. Have you also seen the s

Re: [v8-users] Re: Building v8 for MIPs platform.

Hi Nilima - It is hard to estimate the time/complexity for this. There are a few known areas that require code-generation fixes for big-endian. Search for 'endian' in src/mips/codegen-mips.cc. Fixing those should take a few days or a week. But as I said before I do not think that v8 has ever b

Re: [v8-users] Re: Building v8 for MIPs platform.

Hi Paul, Now I am clear about the target thing. We were using the mips toolchain which was for Big endian to do the compilation. And as you have specified Big endian MIPs porting is not yet supported, we were getting compilation errors. After I used mips toolchain which was little endian, compilat

  1   2   >