[v8-users] Re: No libv8.a generated for either X64 or ARM64 build.

2016-09-28 Thread Nonny Mouse
In case anyone else would prefer to use static libraries in their own build, I have found it easiest to create all .a files as (thin archives) in the same directory, with cd to .../v8/v8/out/x64/obj and then: ar rcsDT libv8_base.a v8_base/*.o (repeated for each library directory) All

[v8-users] Re: No libv8.a generated for either X64 or ARM64 build.

2016-09-27 Thread Nonny Mouse
is greatly appreciated . . . On Monday, September 26, 2016 at 1:21:24 PM UTC-7, Nonny Mouse wrote: > > I'm trying to build V8 for both X64 and ARM64 (by cross compiling). Both > builds seem to run and complete without errors, but libv8.a, libplatform.a, > etc. are not generated for

[v8-users] No libv8.a generated for either X64 or ARM64 build.

2016-09-26 Thread Nonny Mouse
I'm trying to build V8 for both X64 and ARM64 (by cross compiling). Both builds seem to run and complete without errors, but libv8.a, libplatform.a, etc. are not generated for either build. However, other static libraries are successfully built (e.g. libgmock.a). Build machine is X64 running

[v8-users] GN cross build from X64 to ARM64

2016-09-12 Thread Nonny Mouse
I've been using V8 on X64 Linux for several years, but not previously building with GN. For the future, I want to use the same version of V8, under Linux, on both X64 and ARM64 (have a working development board with Ubuntu Linux up and running). After fetch(ing) the current source, I have no