I've noticed something odd in compiling today's HEAD
(d5e66a70c379a425f2c4d1a713dd8eed4b3274eb) on a 32-bit Ubuntu machine
that I don't see on my 64-bit Ubuntu machine. I have to force build
system to use gcc/g++ by doing
CXX=g++ CC=gcc make ia32.release
Is there a better way of doing this?
This is resolved for me now. Must have been a temporary issue on my
VPS in getting to the Google Storage.
On Sat, Apr 25, 2015 at 9:52 AM, Louis Santillan wrote:
> Still failing on
> gs://chromium-clang-format/7219213d084db0ea8eaed8f4291814f4f46fad3a
>
>
>
> On Sat, Apr 25, 2015 at 2:49 AM, Jako
>"it negatively impacts Chrome's shutdown time."
This. This is something I had to learn time and again about V8. You are not
working on Chrome, so the API will not be modified for you.
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You receiv
On Mon, May 4, 2015 at 8:19 AM, Second Datke wrote:
> Some background information:
>
> I'm working on a V8-C++ binding library. I know I'm reinventing the wheel,
> but there is some tiny divergence in my objectives: It's not for Web,
> Node.js, etc. It's actually for a game. I'm trying using V8 as
JavaScript is a truly higher-order language. Scope and life time are
entirely separate concepts in such a language. The end of a scope has no
direct implication on the life time of objects bound to variables in that
scope. Only garbage collection can figure out whether an object is dead,
and run it
Hello,
Revision of my earlier post.
I have downloaded V8 branch 4.4.9
Compile hello_world.cpp
g++ -std=c++11 -I. hello_world.cpp -o hello_world -Wl,--start-group
out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase,snapshot,libplatform},third_party/icu/libicu{uc,i18n,data}}.a
-Wl,--end-g
