Chromium build stable version

[Marquis]

The build of Chromium from source code works well.

But, if i try the stable version, i get a build error like that:

D:\...\src>git checkout 56.0.2924.87

Checking out files: 100% (97933/97933), done.

Note: checking out '56.0.2924.87'.

You are in 'detached HEAD' state. You can look around, make experimental

changes and commit them, and you can discard any commits you make in this

state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may

do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at b169b9a... Publish DEPS for Chromium 56.0.2924.87

D:\...\src>gn gen out3\Default32 "--args=target_cpu=\"x86\" is_official_build=false is_debug=false is_chrome_branded=false"

ERROR at //build/config/BUILDCONFIG.gn:134:15: Reading a variable defined in the same declare_args() call.

If you need to set the value of one arg based on another, put

them in two separate declare_args() calls, one after the other.

  is_debug = !is_official_build

              ^----------------

[Primiano Tucci]

you need gclient sync --with_branch_heads. Rught now you are in an inconsistent checkout state (main project vs subprojects)

Instruction here: https://www.chromium.org/developers/how-tos/get-the-code/working-with-release-branches

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Ryan Hamilton]

But those instructions say:

Note: it is usually NOT possible to sync and build a release branch (i.e. with consistent third_party DEPS); refer to the internal documentation (go/ChromeReleaseBranches) for that. The instructions below show how to check out a release branch only for a specific project (e.g. src.git).

​So even using --with_branch_heads, it's unlikely that building chrome will work.​

[Torne (Richard Coles)]

That's not a problem here; it's possible to build release *tags* just fine (specific version numbers like the 56.0.2924.87 the original poster is using). The thing you can't build is the tip of a release *branch* (e.g. branch-heads/2924).

[Primiano Tucci]

Yup branch != tag as torne@ explained above.

I personally used the checkout xx.yy.ww.zz && gclient sync --with_branch_heads workflow from a pure upstream checkout several times and always worked for me (but also last time I tried was ~6 months ago or so)

[Ryan Hamilton]

Whoa! I had no idea. Thanks! That's awesome.

[Bhatt Bhai]

I did 

git checkout tags/x.x.x.x ,after checking 

git log, moved to 2nd ,3rd and 4th commit, by git checkout 3423dsf344(some commit sha)

Still I get this error,

_________________________________________________________________

ERROR at //build/config/BUILDCONFIG.gn:134:15: Reading a variable defined in the

 same declare_args() call.

If you need to set the value of one arg based on another, put

them in two separate declare_args() calls, one after the other.

  is_debug = !is_official_build

              ^----------------

_________________________________________________________________

 

and I also fired gn args out\release. I was able to build from master.

[Chintan Bhatt]