1. 17 Nov, 2010 - 1 commit
    • John Koleszar's avatar
      vp8_set_maps: remove hard-coded width/height · 7ee516d2
      John Koleszar authored
      The example for disabling the active map used a hard-coded 320x240
      resolution, rather than using what was passed on the command line.
      
      Fixes #218
      
      Change-Id: I3aed713e8aa7fcbf18dfbffd57f142b5cd9ee492
      7ee516d2
  2. 28 Oct, 2010 - 2 commits
    • Timothy B. Terriberry's avatar
      Eliminate more warnings. · 97b766a4
      Timothy B. Terriberry authored
      This eliminates a large set of warnings exposed by the Mozilla build
       system (Use of C++ comments in ISO C90 source, commas at the end of
       enum lists, a couple incomplete initializers, and signed/unsigned
       comparisons).
      It also eliminates many (but not all) of the warnings expose by newer
       GCC versions and _FORTIFY_SOURCE (e.g., calling fread and fwrite
       without checking the return values).
      There are a few spurious warnings left on my system:
      
      ../vp8/encoder/encodemb.c:274:9: warning: 'sz' may be used
       uninitialized in this function
      gcc seems to be unable to figure out that the value shortcut doesn't
       change between the two if blocks that test it here.
      
      ../vp8/encoder/onyx_if.c:5314:5: warning: comparison of unsigned
       expression >= 0 is always true
      ../vp8/encoder/onyx_if.c:5319:5: warning: comparison of unsigned
       expression >= 0 is always true
      This is true, so far as it goes, but it's comparing against an enum,
       and the C standard does not mandate that enums be unsigned, so the
       checks can't be removed.
      
      Change-Id: Iead6cd561a2afaa3d801fd63f1d8d58953da7426
      97b766a4
    • Timothy B. Terriberry's avatar
      Eliminate more warnings. · c4d7e5e6
      Timothy B. Terriberry authored
      This eliminates a large set of warnings exposed by the Mozilla build
       system (Use of C++ comments in ISO C90 source, commas at the end of
       enum lists, a couple incomplete initializers, and signed/unsigned
       comparisons).
      It also eliminates many (but not all) of the warnings expose by newer
       GCC versions and _FORTIFY_SOURCE (e.g., calling fread and fwrite
       without checking the return values).
      There are a few spurious warnings left on my system:
      
      ../vp8/encoder/encodemb.c:274:9: warning: 'sz' may be used
       uninitialized in this function
      gcc seems to be unable to figure out that the value shortcut doesn't
       change between the two if blocks that test it here.
      
      ../vp8/encoder/onyx_if.c:5314:5: warning: comparison of unsigned
       expression >= 0 is always true
      ../vp8/encoder/onyx_if.c:5319:5: warning: comparison of unsigned
       expression >= 0 is always true
      This is true, so far as it goes, but it's comparing against an enum, and the C
       standard does not mandate that enums be unsigned, so the checks can't be
       removed.
      
      Change-Id: Iaf689ae3e3d0ddc5ade00faa474debe73b8d3395
      c4d7e5e6
  3. 09 Sep, 2010 - 1 commit
  4. 18 Jun, 2010 - 1 commit
    • John Koleszar's avatar
      cosmetics: trim trailing whitespace · 94c52e4d
      John Koleszar authored
      When the license headers were updated, they accidentally contained
      trailing whitespace, so unfortunately we have to touch all the files
      again.
      
      Change-Id: I236c05fade06589e417179c0444cb39b09e4200d
      94c52e4d
  5. 14 Jun, 2010 - 1 commit
  6. 04 Jun, 2010 - 1 commit
  7. 25 May, 2010 - 2 commits
    • John Koleszar's avatar
      examples: use I420 input for encoders · 6b76e3fb
      John Koleszar authored
      The output of simple_decoder, as well as the default format for the
      ivf{enc,dec} tools, is I420. The encoder examples are changed to default
      to I420 as well. This is desirable because passing the output of
      simple_encoder to simple_decoder would otherwise have the chroma planes
      flipped, which is unexpected.
      
      Change-Id: I9d4f10ace594a54a7fc4f9a1f9187365c01fd638
      6b76e3fb
    • John Koleszar's avatar
      install includes in DIST_DIR/include/vpx, move vpx_codec/ to vpx/ · b7492341
      John Koleszar authored
      This renames the vpx_codec/ directory to vpx/, to allow applications
      to more consistently reference these includes with the vpx/ prefix.
      This allows the includes to be installed in /usr/local/include/vpx
      rather than polluting the system includes directory with an
      excessive number of includes.
      
      Change-Id: I7b0652a20543d93f38f421c60b0bbccde4d61b4f
      b7492341
  8. 21 May, 2010 - 2 commits
    • James Zern's avatar
      Put img_fmt in the vpx namespace · 6cd4a10e
      James Zern authored
      Avoid an potential name clashes and match other external types.
      s/IMG_FMT/VPX_$&/g
      s/img_fmt/vpx_$&/g
      
      Change-Id: Ia7ad5bbb6424416b37e71e5f5eb1eca31c3c707f
      6cd4a10e
    • John Koleszar's avatar
      configure: remove HAVE_CONFIG_H · 1df0314e
      John Koleszar authored
      This doesn't play well with autotools, and the preprocessor magic is
      confusing and unhelpful in the vp8-only context.
      
      Change-Id: I2fcb57e6eb7876ecb58509da608dc21f26077ff1
      1df0314e
  9. 18 May, 2010 - 1 commit