diff options
author | Joyee Cheung <joyeec9h3@gmail.com> | 2019-11-26 13:30:28 +0800 |
---|---|---|
committer | Joyee Cheung <joyeec9h3@gmail.com> | 2019-12-03 17:30:44 +0800 |
commit | 8cf8eb16ac873c11a6b1051c3a71a91659d431e3 (patch) | |
tree | b003bd57ef919e77f2db0b5a29bf8fba108bacfd /lib | |
parent | 6fd289860190f80b616fdb126bb97ce3f8a0a1c7 (diff) | |
download | android-node-v8-8cf8eb16ac873c11a6b1051c3a71a91659d431e3.tar.gz android-node-v8-8cf8eb16ac873c11a6b1051c3a71a91659d431e3.tar.bz2 android-node-v8-8cf8eb16ac873c11a6b1051c3a71a91659d431e3.zip |
build: do not build mksnapshot and mkcodecache for --shared
To build mkcodecache and mksnapshot (they are executables),
we currently build libnode with unresolved symbols, then build
the two exectuables with src/node_snapshot_stub.cc and
src/node_code_cache_stub.cc. Each of them write a C++ file to
disk when being run. We then use the generated C++ files & libnode
(with unresolved symbols) to build the final Node executable.
However, if libnode itself is the final product, then we should
not build it with unresolved symbols.
https://github.com/nodejs/node/pull/28897 added the two stubs
for the libnode target when the --shared configure option is used,
but it did not get rid of the actions to build and run mksnapshot
and mkcodecache for --shared, so to get it working we also
need a patch to make sure --shared imply --without-node-code-cache
and --without-node-snapshot, until we actually fix the TODO so that
mksnapshot and mkcodecache do not use the libnode that way.
PR-URL: https://github.com/nodejs/node/pull/30647
Refs: https://github.com/nodejs/node/issues/28845
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: David Carlier <devnexen@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions