Developer build?

[Asesh Shrestha]

I just went to chrome://version in our Chromium fork and this is what it's displaying:

WorkStream Browser

57.0.2987.110 (Developer Build) (64-bit)

When compiling our browser I have set it to build release version (is_debug = false in args.gn) as opposed to building debug version but despite that it's still showing developer build. Am I missing something? Isn't released version supposed to be optimized build which we can use for deployments? Or are there more optimized builds?

Thanks

[PhistucK]

You need to set OFFICIAL_BUILD compile-time flag in order to get a non-Developer Build, as far as I know.

☆PhistucK

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/5a82622e-a69d-4f48-96ab-36c4900f013a%40chromium.org.

[Asesh Shrestha]

According to this page: https://www.chromium.org/developers/gn-build-configuration : This build requires that you are a Googler with src-internal checked out so does that mean we are not licensed to use and distribute official builds?

Thanks

On Wednesday, April 5, 2017 at 5:05:33 PM UTC+5:45, PhistucK wrote:

You need to set OFFICIAL_BUILD compile-time flag in order to get a non-Developer Build, as far as I know.

☆PhistucK

On Wed, Apr 5, 2017 at 2:14 PM, Asesh Shrestha <asesh.s...@cloudfactory.com> wrote:

I just went to chrome://version in our Chromium fork and this is what it's displaying:

WorkStream Browser

57.0.2987.110 (Developer Build) (64-bit)

When compiling our browser I have set it to build release version (is_debug = false in args.gn) as opposed to building debug version but despite that it's still showing developer build. Am I missing something? Isn't released version supposed to be optimized build which we can use for deployments? Or are there more optimized builds?

Thanks

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Greg Thompson]

I think there have been efforts to decouple is_official_build=true from is_chrome_branded=true. Try setting it an see what happens. The intent is that is_official_build gives you higher levels of optimizations but doesn't dictate branding. Please file bugs if you find otherwise.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/52cb3451-2fae-4c08-850e-db0e34e14e11%40chromium.org.

[Asesh Shrestha]

So if I set is_official_build to true, will that define GOOGLE_CHROME_BUILD processor directive? If yes then we will have to make lots of changes. Thanks for replying

[Torne (Richard Coles)]

No, it will not; that's controlled by is_chrome_branded.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/5ce93bac-7ebf-4b71-9034-68b574f72544%40chromium.org.

[Asesh Shrestha]

Thanks a lot :)

On Wed, Apr 5, 2017 at 6:00 PM, Torne (Richard Coles) <to...@chromium.org> wrote:

No, it will not; that's controlled by is_chrome_branded.