Integrates libjpeg-turbo into Chromium (Chromium side)...

build/common.gypi

Index: build/common.gypi
===================================================================
--- build/common.gypi	(revision 67381)
+++ build/common.gypi	(working copy)
@@ -140,6 +140,9 @@
       # Remoting compilation is enabled by default. Set to 0 to disable.
       'remoting%': 1,
 
+      # Use libjpeg-turbo instead of libjpeg.
+      'libjpeg_turbo%': 0,
+
       'library%': '<(library)',
 
       # Variable 'component' is for cases where we would like to build some
@@ -169,6 +172,7 @@
     'sysroot%': '<(sysroot)',
     'disable_sse2%': '<(disable_sse2)',
     'remoting%': '<(remoting)',
+    'libjpeg_turbo%': '<(libjpeg_turbo)',

[Mark Mentovai, 2010/11/29 19:14:17]

You may not need the variables-in-variables hack for the libjpeg_turbo.

Well, you don’t need it in this particular changelist as it stands right now.
You should be able to get away with getting rid of the definition of
libjpeg_turbo above and just making this one 'libjpeg_turbo%': 0. However, if
you can successfully implement my other suggestion about putting a
libjpeg_gyp_path variable into this file, you most likely will need to keep this
variables-in-variables hack.

[Hironori Bono, 2010/11/30 09:28:09]

Thank you for your comment. As written here, I need a variables-in-variables
hack for 'libjpeg_gyp_path'. Therefore, I removed this "libjpeg_turbo" hack and
added a "libjpeg_gyp_path" back.

     'library%': '<(library)',
     'component%': '<(component)',