Re: [v8-users] Building v8 without PIC

I'm afraid those flags are not configurable. You'll have to edit build/config/compiler/BUILD.gn (for -fPIC) and build/config/gcc/BUILD.gn and gni/v8.gni (for -pie) -- but none of the BUILD.gn files under src :-) Note that this is entirely independent of how you build V8; gm.py has nothing to do wi

Re: [v8-users] Building V8

Have you tried using linux on windows with WSL: https://docs.microsoft.com/en-us/windows/wsl/about ? On Tue, 26 Mar 2019 at 11:01, Marto Parts wrote: > Yeah I have also a 64 bit machine but it is Windows and i wasn’t able to > build it over there since the documentation is sparse and doesn’t wor

Re: [v8-users] Building V8

Yeah I have also a 64 bit machine but it is Windows and i wasn’t able to build it over there since the documentation is sparse and doesn’t work otherwise I will be happy to run it in the 64bit machine On Tue, 26 Mar 2019 at 15:19, Rodolph Perfetta wrote: > You can build a 32-bit v8 binary on a 6

Re: [v8-users] Building V8

You can build a 32-bit v8 binary on a 64-bit machine and the resulting binary will run on a 32-bit machine. If you need to build on a 32-bit machine, then it is more involved and not officially documented. As said earlier this will likely require you to install tools, update config and scripts. O

Re: [v8-users] Building V8

So long story short I can’t run v8 cause of 32 bit ? On Tue, 26 Mar 2019 at 00:27, Rodolph Perfetta wrote: > To use the bundled tools, you need a 64-bit machine. > > if this is not an option you could try installing all the dependencies > yourself (and disabling the use of bundled tools by speci

Re: [v8-users] Building V8

To use the bundled tools, you need a 64-bit machine. if this is not an option you could try installing all the dependencies yourself (and disabling the use of bundled tools by specifying is_clang=false and probably more), but I don't believe this is documented. On Mon, 25 Mar 2019 at 17:36, wrot

Re: [v8-users] Building v8 with Makefile

Thanks for details Jakob and Peter. > Node has been using Makefile mechanism. I am interested to use ninja > mechanism here and trying it out first. With use_sysroot = false, is it > possible to explicitly mention alternate sysroot path as part of ninja > build? Please let me know. Thanks.

Re: [v8-users] Building v8 with Makefile

Node has been built with yocto, correct? You may want to see see how the Node yocto recipe(s) work, and see if someone has already done the heavy-lifting for V8. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because

Re: [v8-users] Building v8 with Makefile

You can put: is_clang = false use_sysroot = false into args.gn to make the V8 build use your system toolchain and libraries instead of the bundled ones. On Mon, Nov 12, 2018 at 9:18 PM madana gopal wrote: > Hi, > > Also, v8 is using its own toolchain for arm,mips etc, and we have > toolchain

Re: [v8-users] Building v8 with Makefile

Hi, Also, v8 is using its own toolchain for arm,mips etc, and we have toolchain already present as part of our yocto build system.So, do we have any way to make v8 build to point to our own toolchain?. please clarify. Thanks. Regards, Madan -- -- v8-users mailing list v8-users@googlegroups

Re: [v8-users] Building v8 with Makefile

Thanks Jakob for the clarification. We will see the possibility and update. Regards, Madan -- -- 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 unsubscri

Re: [v8-users] Building v8 with Makefile

Ninja is the only officially supported build system for V8. I don't know the requirements of the yocto build system. If all you need is a wrapper, it should be very straightforward to create a two-liner Makefile that invokes the GN/ninja based build. If you need to replace GN/ninja entirely, you'

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

On Thursday, 3 May 2018 12:44:14 UTC-4, Ben Noordhuis wrote: > > V8 by default links statically against the bundled libc++ in > buildtools/third_party/libc++ but dynamically against libc, librt, > etc. > Hmm... seeing how `v8.h` includes `memory`, it could cause problems regardless of whethe

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

On Wed, May 2, 2018 at 11:27 PM, A.M. wrote: > On Saturday, 28 April 2018 05:30:17 UTC-4, Ben Noordhuis wrote: >> >> the CRT linking logic is effectively hard-coded in >> build/config/win/BUILD.gn; look for 'default_crt'. You could try >> sending a CL that adds a build flag to override the defaul

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

On Saturday, 28 April 2018 05:30:17 UTC-4, Ben Noordhuis wrote: > > the CRT linking logic is effectively hard-coded in > build/config/win/BUILD.gn; look for 'default_crt'. You could try > sending a CL that adds a build flag to override the default or simply > patch the file locally. > Ben, th

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

On Monday, 30 April 2018 10:16:10 UTC-4, Ben Noordhuis wrote: > Node.js doesn't use GN. It uses a monolithic GYP build that links > everything together with /MT. > Never had to look inside node-gyp/Node.lib before and was wondering how one of the apps I was working on links against the dynam

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

On Monday, 30 April 2018 10:16:10 UTC-4, Ben Noordhuis wrote: > > Node.js doesn't use GN. It uses a monolithic GYP build that links > everything together with /MT. > Interesting. Didn't know that. Thanks for pointing out. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.go

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

On Mon, Apr 30, 2018 at 3:25 PM, A.M. wrote: > Node.js is not suffering from this because it's using the component build, > which uses a CRT in a DLL Node.js doesn't use GN. It uses a monolithic GYP build that links everything together with /MT. (And yes, it's not without its downsides, too.)

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

> Dynamically linking to the CRT there doesn't gain you much Not sure what you mean. Linking in dynamic CRT gives you so much that one should even consider whether to even work with a statically-linked CRT for any large project. The biggest issue is the heap CRT uses - if a project uses multipl

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

On Sat, Apr 28, 2018 at 7:25 PM, A.M. wrote: > Thanks for responding, Ben. Your feedback is always appreciated. > >> but apropos (2), >> the CRT linking logic is effectively hard-coded in >> build/config/win/BUILD.gn; > > This is surprising - it makes the static build of v8 quite expensive and > e

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

Thanks for responding, Ben. Your feedback is always appreciated. > but apropos (2), > the CRT linking logic is effectively hard-coded in > build/config/win/BUILD.gn; This is surprising - it makes the static build of v8 quite expensive and error-prone to maintain for a multi-DLL project, given

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

On Sat, Apr 28, 2018 at 1:06 AM, A.M. wrote: > I have two questions related to building the v8 as a static library. > > 1. I'm building on Windows and the build fails very close to the end with > this output: > > ninja -C out.gn/x64.debug > ninja: Entering directory `out.gn/x64.debug' > [1/1] Rege

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

yeah, due to vacations, my CL to fix the gn error is still under review. Meanwhile, you can build on linux, that should work already now On Mon, Jan 2, 2017 at 9:12 PM Mindy DelliCarpini wrote: > Thanks again for the help Jochen...but still broken: > > *.gclient:* > solutions = [ > { > "ur

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

Thanks again for the help Jochen...but still broken: *.gclient:* solutions = [ { "url": "https://chromium.googlesource.com/v8/v8.git";, "managed": False, "name": "v8", "deps_file": "DEPS", "custom_deps": {}, }, ] target_os = ['android', 'mac'] *gclient sync* relevant logs

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

On Sat, Dec 24, 2016 at 9:10 PM Mindy DelliCarpini wrote: > In case the issue is this, I'm running El Capitan 10.11.6 > > On Saturday, December 24, 2016 at 12:04:00 PM UTC-8, Mindy DelliCarpini > wrote: > > Ok so did this to the .gclient file 1 directory up: > solutions = [ > { > "url": "ht

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

In case the issue is this, I'm running El Capitan 10.11.6 On Saturday, December 24, 2016 at 12:04:00 PM UTC-8, Mindy DelliCarpini wrote: > > Ok so did this to the .gclient file 1 directory up: > solutions = [ > { > "url": "https://chromium.googlesource.com/v8/v8.git";, > "managed": Fals

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

Ok so did this to the .gclient file 1 directory up: solutions = [ { "url": "https://chromium.googlesource.com/v8/v8.git";, "managed": False, "name": "v8", "deps_file": "DEPS", "custom_deps": {}, "target_os" : ['android', 'mac'] }, ] Then: gclient sync Then tools/dev/v8gen.

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

hey, to build for android, you should add target_os = "android" and target_cpu = "arm". you'll also have to add target_os = ['android', 'mac'] to your .gclient file (which should be one level up from your v8 checkout), so gclient sync will download the android specific deps hth -jochen On Thu,

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

I don't know if the --ide option can be used for building V8. We don't officially support it. The stackoverflow link you provided contains also the answer we officially support: http://stackoverflow.com/a/39550343 Could you try building with ninja and see if it works for you? Of course, if you

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

Or: D:\chromium\v8>gn gen --help | grep -A10 ide= --ide= Generate files for an IDE. Currently supported values: "eclipse" - Eclipse CDT settings file. "vs" - Visual Studio project/solution files. (default Visual Studio version: 2015) "vs2013" - Visual Studio

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

http://stackoverflow.com/questions/38674676/building-and-linking-v8-in-visual-studio And it is in in the gn help: D:\chromium\v8>gn gen --help | grep ide gn gen [] GN optionally generates files for IDE. Possibilities for --ide= Override default sln file name ("all"). Solution file is

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

Please refer to the authors of the gn --ide=vs extension. I don't know what this is supposed to be doing. V8 officially only supports building with ninja. E.g. gn gen v5.4/x64.release ninja -C v5.4/x64.release d8 -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/gr

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

Take a look at how I built V8 5.4.500.43: https://github.com/phpv8/v8js/issues/272#issuecomment-262848754 -- -- 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

Re: [v8-users] Building V8 libs for Android on Windows 10

Jochen I have the latest g++ packages installed . However I discovered that all components of the V8 package did not download. The command "gclient sync --with_branch_heads" seems to fail with this message: .. Downloading /home/sanjit/V8Dev/v8/third_party/binutils/Linux_x64/binutils.t

Re: [v8-users] Building V8 libs for Android on Windows 10

Looks like you might need to install the g++ package? On Mon, Nov 7, 2016 at 12:39 PM Trekkie Ufo wrote: > Hi, managed to install everything on Ubuntu Linux and fired off a V8 build > for Android. > > (1) gn gen out.gn/foo --args='is_debug=false target_cpu="arm64" > v8_target_cpu="arm64" use_gom

Re: [v8-users] Building V8 libs for Android on Windows 10

Hi, managed to install everything on Ubuntu Linux and fired off a V8 build for Android. (1) gn gen out.gn/foo --args='is_debug=false target_cpu="arm64" v8_target_cpu="arm64" use_goma=false target_os = "android" is_component_build = true ' (2) ninja -C out.gn/foo I keep getting errors like the

Re: [v8-users] Building V8 libs for Android on Windows 10

Ah thanks Jochen ! Got Ubuntu running in a Virtual box and making good progress. Sanjit On Monday, 7 November 2016 07:35:35 UTC, Jochen Eisinger wrote: > > Hi, > > we currently only support building for Android on a Linux or a Mac host. > > best > -jochen > > On Sun, Nov 6, 2016 at 2:37 PM Tr

Re: [v8-users] Building V8 libs for Android on Windows 10

Hi, we currently only support building for Android on a Linux or a Mac host. best -jochen On Sun, Nov 6, 2016 at 2:37 PM Trekkie Ufo wrote: > Hi > I am trying to build V8 for use in a plugin I am developing for the Unreal > Engine 4. My aim is to run the project on the Google Daydream VR platf

Re: [v8-users] Building v8

I had to manually create the .a file. I will see if I can dig up the script I used to generate it. On Mon, Oct 17, 2016 at 7:19 AM, Temuri Imnaishvili wrote: > I've tried that. > > What I need in order to compile v8js is libv8_libplatform.a alongside its > .so. > > I can still get everything I n

Re: [v8-users] Building v8

I've tried that. What I need in order to compile v8js is libv8_libplatform.a alongside its .so. I can still get everything I need if I compile off 5.1.x branch with gyp. Then I'd do this and all would be fine: echo -e "create /usr/lib/libv8_libplatform.a\naddlib out/native/obj.target/tools/gy

Re: [v8-users] Building v8

support for compiling libplatform as a shared library landed a few days ago. If you compile with the gn flag is_component_build = true, you should get a shared library On Sat, Oct 15, 2016 at 10:06 PM Temuri Imnaishvili wrote: > Jochen, > > Facing the same problem. Can you provide us with help o

Re: [v8-users] Building v8

Jochen, Facing the same problem. Can you provide us with help on compiling it correctly? Thanks! On Tuesday, 20 September 2016 03:25:21 UTC-4, Jochen Eisinger wrote: > > If you want to build v8 with shared libraries, set the gn arg > is_component_build=true > > Yes, we intend to update the emb

Re: [v8-users] Building v8 with gn.

I figured out how to build with gyp now. Would still be nice to know how to link libv8_libplatform.lib and libv8_libbase.lib with the gn approach. Thanks. On Sunday, October 2, 2016 at 3:12:02 PM UTC-7, Jane Chen wrote: > > I specified "is_component_build=true" on 5.3-lkgr. I do get libv8.so,

Re: [v8-users] Building v8 with gn.

I specified "is_component_build=true" on 5.3-lkgr. I do get libv8.so, but I don't get libv8_libplatform.a or libv8_libbase.a. This is not a problem for me on Linux, since I could still build with gyp. But on Windows, I only seem to be able to build using gn now, and I need a way to generate

Re: [v8-users] Building v8 with gn.

On Thu, Sep 22, 2016 at 1:22 AM Jane Chen wrote: > Trying to build v8 5.3-lkgr with gn for embedding use. > > When I build with GYP, I need to set "-Dv8_use_external_startup_data=0". > Is there an equivalent setting flag for gn? > the equivalent gn setting is v8_use_external_startup_data = false

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

That'd be with set GYP_GENERATORS=msvs But I'm afraid we dropped official support for this a while back. Why not build with ninja? E.g. gyp_generator like you specified and then build with: ninja -C out\Release on x64 platforms might require: ninja -C out\Release_x64 On Wednesday, September 21

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

Thanks for the reply Jochen, How do I specify the msvs gyp generator? On Wednesday, 21 September 2016 10:54:39 UTC+2, Jochen Eisinger wrote: > > If you want to build with MSVS, you need the msvs gyp generator. > msvs-ninja only supports browsing the project, not building it > > On Tue, Sep 20, 20

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

If you want to build with MSVS, you need the msvs gyp generator. msvs-ninja only supports browsing the project, not building it On Tue, Sep 20, 2016 at 10:04 AM Pieter wrote: > > I have been struggling for a couple of days to get the correct > incantations to get a build of v8 working on windows

Re: [v8-users] Building v8

If you want to build v8 with shared libraries, set the gn arg is_component_build=true Yes, we intend to update the embedder guide. Contributions or bug reports are always welcome! On Fri, Sep 16, 2016 at 7:43 PM Furious Scissors wrote: > Ok - i'll try and give that a shot. Are there any plans o

Re: [v8-users] Building v8

Ok - i'll try and give that a shot. Are there any plans on upgrading the Embedded Guide to something more recent than v4.8? If I work this out - would I be able to contribute to the wiki to update it for everyone else? On Thursday, September 15, 2016 at 10:11:01 PM UTC-7, Jochen Eisinger wrote:

Re: [v8-users] Building v8

Hi, Is there an option to build a shared version of libplatform? I'm upgrading a project I'm working on from v8 5.3 (with static linking) to 5.4 (with dynamic linking), and I use libplatform. I used to link against libv8_libplatform.a, but now I cannot find an option in gn that automatically g

Re: [v8-users] Building v8

by default, we build thin archives which are suitable for static linking against other apps, and yes, you will need the .o files around for that. If you'd rather have shared libraries (.so files), set the gn arg is_component_build = true br -jochen On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp w

Re: [v8-users] Building v8 with a networking stack

chromium's implementation is here: https://cs.chromium.org/chromium/src/net/proxy/proxy_resolver_v8.cc?rcl=1472733616&l=703 On Fri, Sep 2, 2016 at 3:53 AM Nick Chambers wrote: > Hello everyone! I have successfully built v8, however I have run into a > snag. Essentially what I am after is the sma

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

On Wed, Jul 20, 2016 at 8:59 AM, Jochen Eisinger wrote: > Please reach out to IBM team. The svn server referenced in that > documentation doesn't exist anymore, however, the s390(x) port is meanwhile > (completely?) upstream, so just following the regular v8 build instructions > might work? I've

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

On Wed, Jul 20, 2016 at 12:33 AM, 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 am currently trying to build V8 Libraries following this tutorial, > Building V8 Libraries Tutorial. I am trying to build these on a s390x Ubuntu > Doc

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

Please reach out to IBM team. The svn server referenced in that documentation doesn't exist anymore, however, the s390(x) port is meanwhile (completely?) upstream, so just following the regular v8 build instructions might work? On Wed, Jul 20, 2016 at 12:33 AM Allen Ng wrote: > Hello all, > > I

Re: [v8-users] Building V8 without natives_blob.bin and snapshot_blob.bin

It works, thank you! W dniu wtorek, 28 czerwca 2016 16:33:20 UTC+2 użytkownik Ben Noordhuis napisał: > > On Tue, Jun 28, 2016 at 3:55 PM, Dawid Skurzok > wrote: > > I have problems with building V8 without external data files. I have > asked > > same question on SO but with no success. I thin

Re: [v8-users] Building V8 without natives_blob.bin and snapshot_blob.bin

On Tue, Jun 28, 2016 at 3:55 PM, Dawid Skurzok wrote: > I have problems with building V8 without external data files. I have asked > same question on SO but with no success. I think I'm missing something > simple, I don't know much of GYP. > > I already build V8 and its working correctly, but bina

Re: [v8-users] Building v8 in an lxc container

Added the "o" flag to the extract line here: https://github.com/v8/v8/blob/5749d710bc73ef40f9b9e8b94ec290e0412d3f57/third_party/binutils/download.py#L91 and that worked, but then ran into another snag, similar to this one: https://bbs.archlinux.org/viewtopic.php?id=209871 Bailed on the build from

Re: [v8-users] Building V8 Older versions

Yeap, I completely understand. This is for the test purpose and I got few dependencies which requires me to use this version. I see programs used to compile with this version now fail to compile with newer versions, and can't change/modify these programs. Thanks, Hitesh On Thu, Feb 11, 2016 at 3

Re: [v8-users] Building V8 Older versions

3.9.24, are you sure? That's a daily development snapshot from almost 4 years ago! I'd strongly advise against using it for anything, as it is probably full of bugs, including security vulnerabilities. I wouldn't be surprised if it didn't even compile any more with modern compilers, as toolchains t

Re: [v8-users] Building v8 using Visual Studio 2015

I followed https://chromium.googlesource.com/v8/v8/+/master/docs/building_with_gyp.md 1. Install Visual Studio 2015 Enterprise (Visual Studio 2013 Ultimate is also installed if that matters). 2. Download and unpack depot_tools to C:\depot_tools 3. cd to C:\depot_tools 4. gclient sync 5. fetch

Re: [v8-users] Building v8 using Visual Studio 2015

Are you building & debugging with the Visual Studio IDE? Using a Visual Studio solution (.sln) file? I'm still on VS2013 and would LOVE to be able to use the IDE over DOS ninja commands. Can you point me to those instructions on how to make this happen? Thanks a lot! -- -- v8-users mailing l

Re: [v8-users] Building v8 using Visual Studio 2015

I was only able to get V8 to build with VS2015 by editing build/standalone.gypi as Michael Collins posted. At this time, is V8 tested to work with MSVS 2015? Is there a plan to switch soon? Thanks, Michael On Monday, July 27, 2015 at 9:54:01 AM UTC-7, Jochen Eisinger wrote: > > I landed some co

Re: [v8-users] Building V8 on Mac OS X

On Fri, Sep 25, 2015 at 5:54 PM, Bradley Slavik wrote: > Dear V8 users group, > > I am looking for information about building V8 on Mac OS X. A few months > ago when I researched it, it appeared that GYP was necessary to build V8. > GYP required old Python 2 instead of Python 3 to be installed. S

Re: [v8-users] Building v8 with Visual Studio 2012

Thank you so much for your reply. - Purusothaman A On Mon, Aug 10, 2015 at 3:17 PM, Ben Noordhuis wrote: > On Mon, Aug 10, 2015 at 8:34 AM, Purusothaman A > wrote: > > Hi All, > > > > I am new to this group and I like to integrate google v8 with my project. > > > > Tried many times to build so

Re: [v8-users] Building v8 with Visual Studio 2012

On Mon, Aug 10, 2015 at 8:34 AM, Purusothaman A wrote: > Hi All, > > I am new to this group and I like to integrate google v8 with my project. > > Tried many times to build source with VS 2012, but its giving so many > compilation errors. > > Is there some step by step procedure to compile v8 sour

Re: [v8-users] Building v8 using Visual Studio 2015

I landed some config changes to make v8 compile with MSVS 2015, however, I haven't ran tests yet. Since we don't have MSVS 2015 builders yet, that configuration might break, however, eventually, we'll switch to MSVS 2015, just not yet now. best -jochen On Thu, Jul 23, 2015 at 5:19 PM Michael Col

Re: [v8-users] Building V8 with higher heap size

On Wed, Aug 13, 2014 at 9:54 PM, Sridhar wrote: > Hi Ben, > > Thanks for quick response, No that doesn't seem to work. I have tried > recompiling node (0.10.30) with changes that caustik suggested.. > (Or) may be I am failing to understand if the heap is what I set when > starting node. > > I'm s

Re: [v8-users] Building V8 with higher heap size

Hi Ben, Thanks for quick response, No that doesn't seem to work. I have tried recompiling node (0.10.30) with changes that caustik suggested.. (Or) may be I am failing to understand if the heap is what I set when starting node. I'm starting node with the following options. ../bin/node --max_o

Re: [v8-users] Building V8 with higher heap size

On Tue, Aug 12, 2014 at 9:02 PM, Sridhar wrote: > Hi All, > > I am new to nodejs and V8, I am trying to build V8 with increased heap for > server side usage of V8. In V8 source ( heap.cc) it is mentioned you can set > this as build environment to build with higher heap. > Can someone please point

Re: [v8-users] Building V8 for ARM64 in MSVC2012

Thank Sven and Rodolph for the suggestions. Indeed, lots of constants ending with "UL" or "L" need to be changed for Windows build which assumes 32-bit for "long". In fact, it would be better to use "ULL" and "LL", which guarantees 64-bit on both LP64 and LLP64 systems. The bitwidth for "long" is

Re: [v8-users] Building V8 for ARM64 in MSVC2012

There is nothing fundamentally preventing an LLP64 system to build/run arm64 but it was never tested hence not supported. Some re-factoring is probably required (don't forget constants). As Sven said, patches welcome. On 8 August 2014 07:21, Sven Panne wrote: > On Thu, Aug 7, 2014 at 11:50 PM,

Re: [v8-users] Building V8 for ARM64 in MSVC2012

On Thu, Aug 7, 2014 at 11:50 PM, Prince Wall wrote: > [...] However, from [v8]\src\arm64\constants-arm64.h, it says "Assert that > this is an LP64 system" and uses type "long" a lot, assuming it is 64-bit. > However, Windows x64 is LLP64 system and has "long" as 32-bit. Does this > mean that we

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

Thanks for help again. I didn't run into more problems until now. It seems, that /proc/cpuinfo changed since kernel 3.9.3 for the ARM. Am Dienstag, 22. Juli 2014 16:34:18 UTC+2 schrieb Rodolph Perfetta: > > I sounds like auto detection is failing again, override it: --noenable-mls > should do it

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

I sounds like auto detection is failing again, override it: --noenable-mls should do it. I can't push a patch right now so keep reporting any issues. Thanks, Rodolph. On 22 July 2014 15:08, Dirk Grabbert wrote: > Ok, I'm able to start the example shell right now. But I got the next > problem.

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

Ok, I'm able to start the example shell right now. But I got the next problem. Trying to run a js-script brings up an illegal instruction caused by "mls". I think it's generated by the JIT, right? The script I'm trying to run is a "port" of the dhrystone test (source: http://jsperf.com/pystone

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

Actually, Rodolph just pointed out that running: d8 --help | head -n 2 will output the same information as v8::internal::CpuFeatures::PrintFeatures/PrintTarget, so you should be able to do this instead of the gdb commands I suggested in the last message. Cheers, Ross On 21 July 2014 17:30, Ross

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

Hi Dirk, The stack trace looks like the movw is being emitted in generated code. Could you try again with a debug build of V8 which includes r22512 ( https://codereview.chromium.org/402923002/) - this should fail with an ASSERT error if V8 tries to emit a movw instruction on an armv6 target. If

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

Here is a screenshot of gdb. Cheers, Dirk. Am Freitag, 18. Juli 2014 17:37:13 UTC+2 schrieb Ross McIlroy: > > I don't have an armv6 device to test on here, but I tried with a simulator

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

Great thx for your respond. I'm using the version from git (currently "9ac5e7f"), but I've also tried older versions. I've dumped the shell and all the other created object files, didn't find any movw instruction there. I don't know why it crashs caused by this instruction neither where it come

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

I don't have an armv6 device to test on here, but I tried with a simulator build with added asserts in Assembler::movw/movt to ensure that they aren't emitted when targeting armv6 and these asserts didn't trigger, so I'm not sure where the movw instruction is being emitted. Could you let me know t

Re: [v8-users] Building v8 for Android, ARM binary sizes

On Wed, Oct 23, 2013 at 1:12 PM, Pris Matic wrote: > Hi, > > I built v8 for Android three different ways and the file sizes for the > resulting binaries seemed a little 'off' compared to a value I got from the > site of a mobile development framework (Appcelerator) that embeds v8 into > their And

Re: [v8-users] Building v8 for ARMv5

V8 requires hardware floating point. Regards, Rodolph. On 28 August 2013 14:53, wrote: > I'm trying to use version 3.20.16 of v8 under an ARM926ej-s (ARMv5) board, > where /proc/cpuinfo shows the following information: > > # cat /proc/cpuinfo > Processor : ARM926EJ-S rev 5 (v5l) > BogoMIPS :

Re: [v8-users] Building v8

Yes, I lose gyp_v8. When I updated: svn co http://gyp.googlecode.com/svn/trunk build/gyp. I succesfully compiled v8. Thank you, Jakob. On Sat, Dec 1, 2012 at 6:25 PM, Maksim Lukyanchenko > > wrote: > >> I'm trying to compile V8 on Win7 for VS2010: >> >> svn co http://gyp.googlecode.com/svn/t

Re: [v8-users] Building v8

On Sat, Dec 1, 2012 at 6:25 PM, Maksim Lukyanchenko < maksim.lukyanche...@gmail.com> wrote: > I'm trying to compile V8 on Win7 for VS2010: > > svn co http://gyp.googlecode.com/svn/trunk build/gyp > > svn co http://src.chromium.org/svn/trunk/tools/third_party/python_26 > third_party/python_26 > >

Re: [v8-users] Building v8 as a static library (libv8.a) using GYP build?

Thanks Jakob, that makes sense. I've confirmed that by linking to those libraries it works. I may have been thrown off initially by the fact that the .a files are buried so deep in the build output, basically had to grep. I did look at the d8 build before, but it of course just says v8.gyp is a

Re: [v8-users] Building v8 as a static library (libv8.a) using GYP build?

On Mon, Mar 5, 2012 at 14:23, Bryan White wrote: > > Yep, that seems to be the case, and it is sufficient for all clients of > V8 > > that I know of. > > I don't know what you definition of 'client' is in this context, Projects depending on V8. > but I > for one use the static libv8 and would

Re: [v8-users] Building v8 as a static library (libv8.a) using GYP build?

> Yep, that seems to be the case, and it is sufficient for all clients of V8 > that I know of. I don't know what you definition of 'client' is in this context, but I for one use the static libv8 and would be very concerned if the option to build this was dropped. > There's no need to explicitly s

Re: [v8-users] Building v8 as a static library (libv8.a) using GYP build?

(inline) On Sat, Mar 3, 2012 at 07:21, Jeff Rogers wrote: > I was wondering if it is possible to build v8 as a static library > (libv8.a) on Mac or Linux using the GYP build? Looking at the gyp files, it > seems like the new build system will only build shell executables and > smaller component

Re: [v8-users] Building V8 under CentOS 5.5

Try the strictaliasing=off flag. Out of interest, what does "g++ --version" print? On Thu, Jan 26, 2012 at 17:24, Alex Paransky wrote: > I am trying to build lastest from Master with V8, but failing at the > first step of building V8: > >cat /etc/redhat-release > > CentOS release 5.5 (Final) >

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

The MIPS port isn't done. It doesn't work. Den 8. jul. 2010 14.12 skrev Nilima Chavan : > When I am trying to build v8 for MIP platform, I am getting following > errors: > $ scons simulator=mips > > In file included from src/virtual-frame.h:41, > from src/virtual-frame-inl.h:31,