[英]How to build a specific version of Chromium?
I want to build the latest stable version of Chromium ( 62.0.3202.84
at the time of writing, see OmahaProxy ). 我想构建最新的稳定版Chromium(
62.0.3202.84
本文时为62.0.3202.84 ,参见OmahaProxy )。
The build instructions work just fine for the current development version. 构建指令适用于当前的开发版本。
From this question , the Brave wiki and some other sources, the instructions to fetch and build a specific version seem to be pretty clear : 从这个问题 , 勇敢的维基和其他一些来源,获取和构建特定版本的说明似乎非常清楚:
git fetch origin 62.0.3202.84
git checkout -b my_stable_branch FETCH_HEAD
# hooks and dependencies if needed, commits, compilation...
However, this does not seem to work for me. 然而,这似乎并没有为我工作。 When I create a branch for
FETCH_HEAD
, a quick git log
shows that I have the latest commits from master
. 当我为
FETCH_HEAD
创建一个分支时,一个快速的git log
显示我有来自master
的最新提交。
What am I misunderstanding ? 我有什么误会?
EDIT : 编辑 :
If I do the steps from Asesh's answer from master
, it runs “successfully” but I still end up building master
instead of what I want. 如果我做的步骤从Asesh的回答从
master
,它运行“成功”,但我还是落得建筑master
,而不是我想要的。
If I first create a branch from a specific tag (as specified in the Chromium documentation ), like 62.0.3202.84
, or even if I just check it out without branching, gclient sync --with_branch_heads
fails giving me the following error : 如果我首先从特定标记创建一个分支(如Chromium文档中所指定的 ),如
62.0.3202.84
,或者即使我只是在没有分支的情况下检查它, gclient sync --with_branch_heads
无法给出以下错误:
Error: Command 'git checkout --quiet 6e4c388c0117fe408b66fbede91081fb1018c5fe' returned non-zero exit status 128 in /path/to/chromium/src/media/cdm/api
fatal: reference is not a tree: 6e4c388c0117fe408b66fbede91081fb1018c5fe
I successfully compiled version 3239, so I understand the problem was a bad reference in 3202's DEPS
file. 我成功编译了版本3239,所以我理解这个问题在3202的
DEPS
文件中是一个错误的引用。 (which is quite weird...) (这很奇怪......)
Hence the following steps are actually correct: 因此,以下步骤实际上是正确的:
git checkout -b your_branch xx.x.xxxx.xx
gclient sync
EDIT 2018-07-02: According to this page , starting from version 3420, it should be possible to correctly sync dependencies. 编辑2018-07-02:根据此页面 ,从版本3420开始,应该可以正确地同步依赖项。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.