I'm on a mac indeed. I tried a comparable build on my Linux machine:
➜ node git:(master) ls -l
./out/Release/obj.target/deps/v8/src/libv8_base.a ./out/Release/node
-rwxr-x--- 1 ofrobots eng 37422880 Feb 7 16:57 ./out/Release/node
-rw-r- 1 ofrobots eng 2533998 Feb 7 16:57
Jakob, I'm glad to hear that your v8_base is only 29M for you. The .o files
in my obj/v8_base are large
> du -sh obj/v8_base
1.1G obj/v8_base
Could this have something to do with libcpp_is_static?
Ali, are you on macintosh? Maybe this is only a problem on OSX. And I also
find that my resulting
My local node `master` branch build (V8 6.4.388-40) does have a large
libv8_base.a, but the final binary is small. Maybe the compilers are
putting more stuff in there that the linker strips out.
❯ ls -l ./out/Release/libv8_base.a
-rw-r--r-- 1 ofrobots eng 1269949240 Feb 7 08:14
That does indeed seem very large. On Linux with a current checkout (and
without v8_static_library=true), my out/x64.release/obj/v8_base directory
with all the .o files is only 29MB.
Unfortunately, I have no idea what might be causing the difference in your
case. Do any *.o files stand out as very
Hi,
I've noticed that the build size in the latest V8 releases is very large.
For example, on 6.5.257, I get
-rw-r--r-- 1 rld staff 1.1G Feb 7 18:49 out/v8build/obj//libv8_base.a
It's similarly large on 6.6.164. I'm experiencing this on OSX and here is
the configuration I'm using:
