Use new os_posix define in ffmpeg.gyp

ffmpeg.gyp

 # Copyright (c) 2011 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # There's a couple key GYP variables that control how FFmpeg is built:
 #   ffmpeg_branding
 #     Controls whether we build the Chromium or Google Chrome version of
 #     FFmpeg.  The Google Chrome version contains additional codecs.
 #     Typical values are Chromium, Chrome, ChromiumOS, and ChromeOS.
 #   use_system_ffmpeg
 #     When set to non-zero will build Chromium against the system FFmpeg
 #     headers via pkg-config.  When Chromium is launched it will assume that
 #     FFmpeg is present in the system library path.  Default value is 0.
 #   build_ffmpegsumo
 #     When set to zero will build Chromium against the patched ffmpegsumo
 #     headers, but not build ffmpegsumo itself.  Users are expected to build
 #     and provide their own version of ffmpegsumo.  Default value is 1.
 #
 # TODO(ihf): Define these variables and use them.
 # LIBAVCODEC_VERSION_MAJOR=53
 # LIBAVFORMAT_VERSION_MAJOR=53
 # LIBAVUTIL_VERSION_MAJOR=51
 
 {
   'target_defaults': {
     'conditions': [
-      ['OS!="linux" and OS!="freebsd" and OS!="openbsd" and OS!="solaris"', {
+      ['os_posix != 1 or OS == "mac" or OS == "openbsd"', {

[scherkus (not reviewing), 2011/11/23 01:22:54]

nit: no spaces around operators (!=, ==, etc..)

[ruben, 2011/11/23 01:36:15]

I was told otherwise by estade here:

http://codereview.chromium.org/7011032/#msg5

Both idioms are currently used, with your idiom used more often.  I honestly
don't care about the spacing, just following what I was told.

[scherkus (not reviewing), 2011/11/23 01:46:25]

estade@ made a comment about consistency, which would apply here but in reverse
:)

currently the rest of this file has no spaces -- you would be introducing a
mixture which would forever cause confusion among future developers

sorry to nit about this stuff  :\

[ruben, 2011/11/23 02:17:14]

If you follow that thread a couple comments down, he said Chromium should be
using the python style guidelines and asked that I use spaces for new patches. 
Chromium is already inconsistent on this spacing issue, nothing short of a
automated spacing commit will change that.
 
No problem, I just want to be consistent also.  All my patches after estade
asked were committed with spaces.  If you still don't want spaces in this one,
let me know and I'll take them out.

         'sources/': [['exclude', '/linux/']]
       }],
       ['OS!="mac"', {'sources/': [['exclude', '/mac/']]}],
       ['OS!="win"', {'sources/': [['exclude', '/win/']]}],
+      ['OS!="openbsd"', {'sources/': [['exclude', '/openbsd/']]}],
     ],
     'variables': {
       # Since we are not often debugging FFmpeg, and performance is
       # unacceptable without optimization, freeze the optimizations to -O2.
       # If someone really wants -O1 , they can change these in their checkout.
       # If you want -O0, see the Gotchas in README.Chromium for why that
       # won't work.
       'debug_optimize': '2',
       'mac_debug_optimization': '2',
     },
@@ skipping 111 matching lines @@
                     '-mfpu=vfpv3-d16',
                   ],
                 }],
                 ['arm_neon==1', {
                   'cflags': [
                     '-mfpu=neon',
                   ],
                 }],
               ],
             }],
-            ['OS=="linux" or OS=="freebsd" or OS=="openbsd" or OS=="solaris"', {
+            ['os_posix == 1 and OS != "mac"', {
               'defines': [
                 '_ISOC99_SOURCE',
                 '_LARGEFILE_SOURCE',
                 # BUG(ihf): ffmpeg compiles with this define. But according to
                 # ajwong: I wouldn't change _FILE_OFFSET_BITS.  That's a scary change
                 # cause it affects the default length of off_t, and fpos_t,
                 # which can cause strange problems if the loading code doesn't
                 # have it set and you start passing FILE*s or file descriptors
                 # between symbol contexts.
                 # '_FILE_OFFSET_BITS=64',
@@ skipping 45 matching lines @@
                       '-DARCH_X86_64',
                       '-m', 'amd64',
                       '-DPIC',
                       # The next two lines are needed to enable AVX assembly.
                       '-Iconfig/<(ffmpeg_branding)/<(os_config)/<(ffmpeg_config)',
                       '-Pconfig.asm',
                     ],
                   }],
                 ],
               },
-            }],  # OS=="linux" or OS=="freebsd" or OS=="openbsd" or OS=="solaris"
+            }],  # os_posix == 1 and OS != "mac"
             ['OS=="openbsd"', {
               # OpenBSD's gcc (4.2.1) does not support this flag
               'cflags!': [
                 '-fno-signed-zeros',
               ],
             }],
             ['OS=="mac"', {
               'conditions': [
                 ['mac_breakpad==1', {
                   'variables': {
@@ skipping 292 matching lines @@
       ],  # conditions
     },
   ],  # targets
 }
 
 # Local Variables:
 # tab-width:2
 # indent-tabs-mode:nil
 # End:
 # vim: set expandtab tabstop=2 shiftwidth=2: