MacViews: Get chrome/browser/ui/views/frame to compile

build/common.gypi

Index: build/common.gypi
diff --git a/build/common.gypi b/build/common.gypi
index 1c19ffa3aaeb107a0d4ec6c5b114f66215f2ab20..9ead643138caf7ffe7ef5bd3a2cf8310faf60535 100644
--- a/build/common.gypi
+++ b/build/common.gypi
@@ -1503,6 +1503,9 @@
     'ozone_platform_ozonex%': 0,
     'ozone_platform_test%': 0,
 
+    # Whether the browser is non-native (using Views Toolkit) on Mac.

[sky, 2014/11/05 22:44:25]

Do we really need the ability to change this independent of toolkit_views? I'm
wondering if you can instead use toolkit_views always?

[Andre, 2014/11/05 23:27:04]

We would like the standard Mac build to include toolkit_views=1 so that we can
avoid MacViews build regression. At link time, the views code get pruned because
they are not referenced and the Cocoa code runs as before. This means that we
need another flag to select linking the views browser instead of the Cocoa one
(for development only for now).

+    'mac_views_browser%': 0,

[sky, 2014/11/05 22:44:25]

Can you key off toolkit_views instead of another define?

+
     'conditions': [
       ['buildtype=="Official"', {
         # Continue to embed build meta data in Official builds, basically the