如何建造自己的V8叉

发布于 2025-02-04 04:11:19 字数 357 浏览 2 评论 0原文

我有自己的V8叉子,想构建它。 但是,gngclient不断失败,并告诉我我需要在结帐中。

$> git clone <ownRepository>
$> gn gen out/build
gn.py: Could not find checkout in any parent of the current path.
This must be run inside a checkout.
``

How can I build my own fork? `fetch` does not seem to accept custom repositories.

I have my own fork of v8 and would like to build it.
However, gn and gclient keep failing and telling me that I need to be inside a checkout.

gt; git clone <ownRepository>
gt; gn gen out/build
gn.py: Could not find checkout in any parent of the current path.
This must be run inside a checkout.
``

How can I build my own fork? `fetch` does not seem to accept custom repositories.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

狠疯拽 2025-02-11 04:11:19

V8 GIT存储库(或它的叉子)根本不包含建筑所需的一切;特别是它错过了第三方依赖性并共享构建配置逻辑。官方构建工具/工作流的目的是设置所有这些。因此,最简单的前进路径可能是获得常规的V8结帐(使用Fetch v8),然后用自己的自己替换v8目录。确保版本匹配(至少大约)。

替代方法是找出什么fetch v8gclient Syncgclient runhooks do,然后手工做所有这些 - 完全可能,由于它们都是脚本和完全开源的,但这是很多工作,而且没有很多有趣,所以我不建议这样做。

The V8 git repository (or a fork of it) simply doesn't contain everything that's required for building; in particular it misses third-party dependencies and shared build configuration logic. The purpose of the official build tools/workflow is to set all that up. So the easiest path forward for you is probably to get a regular V8 checkout (using fetch v8), and then replacing the v8 directory in there with your own. Make sure that the versions match (at least approximately).

The alternative is to figure out what fetch v8, gclient sync and gclient runhooks do, and doing all of that by hand -- totally possible, as they're all just scripts and entirely open source, but it's a lot of work and not much fun, so I wouldn't recommend that.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文