debug builds should be component builds by default |
||
Issue descriptionStatic debug builds aren't really supported in Chromium (we don't have any builders that build them), and on some platforms (e.g., Windows), they flat out won't work. There has been discussion off and on about whether we should support them, and whether we should default to shared (which tends to be a better dev experience since it builds faster and takes less disk space, but is farther away from the configuration we ship). Historically, we couldn't easily change this in GYP because debug and release had to be either both static or both shared. However, in GN, there's no reason we can't have different defaults here.
,
Aug 1 2016
,
Aug 4 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5e90548f18cc7ce931c3fda659ebad2ebb9bc3f0 commit 5e90548f18cc7ce931c3fda659ebad2ebb9bc3f0 Author: dpranke <dpranke@chromium.org> Date: Thu Aug 04 01:19:55 2016 Make debug builds component builds by default. (Except on iOS, where component builds aren't supported). R=brettw@chromium.org BUG= 631537 Review-Url: https://codereview.chromium.org/2205573003 Cr-Commit-Position: refs/heads/master@{#409692} [modify] https://crrev.com/5e90548f18cc7ce931c3fda659ebad2ebb9bc3f0/build/config/BUILDCONFIG.gn
,
Aug 4 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by dpranke@chromium.org
, Jul 26 2016