Updates:
Cc: [email protected]
Comment #1 on issue 4101 by [email protected]: Switch default build
tool to ninja - under the hood
https://code.google.com/p/v8/issues/detail?id=4101
I'm not entirely sure if what we want can be done with gyp and ninja. Has
somebody better ideas than the below?
Letting ninja build into different directories is easy:
GYP_GENERATOR_FLAGS="output_dir=out/ia32" ...
GYP_GENERATOR_FLAGS="output_dir=out/x64" ...
ninja -C out/ia32/Release d8
ninja -C out/x64/Release d8
Naively, it looks like we have to call ninja sequentially for all the
cross-products of architecture and build config. Ideally we'd be able to
run _one_ ninja command on e.g. all Release configs and then let ninja
parallelize out/ia32/Release, out/x64/Release, etc, like make does it.
---
I tried to construct a build.ninja file in out that has subninja commands
to the out/ia32/Release/build.ninja, but then the directories aren't
fitting as the main working dir would be "out" but the paths in the
subninja files are relative to e.g. out/ia32/Release.
---
A different way would be to hard-code gyp configuration cross-products like
Release_ia32, Release_x64, etc that inherit from Release_Base and ia32_Base
or Release_Base and x64_Base. But also here, I don't know how to build all
the Release_* configs with one command.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
