1. 17 Jan, 2013 - 1 commit
    • John Koleszar's avatar
      Don't include x86inc.asm on non-x86 targets · 23963021
      John Koleszar authored
      This file is currently unused, as the asm that depended on it has been
      disabled for the current roll into Chromium. It's expected that it
      will return in some form, so wrap it in an x86 check rather than
      deleting it. This extra file isn't really an issue with the libvpx
      build system, but affects the gyp builds since on ARM (android) it
      tries to do the ADS->GAS conversion on all .asm files reported in
      libvpx_srcs.txt.
      
      Change-Id: I080fbc22ab59fff41264ae230a48fa753594135b
      23963021
  2. 26 Dec, 2012 - 1 commit
  3. 05 Dec, 2012 - 2 commits
  4. 04 Dec, 2012 - 1 commit
  5. 03 Dec, 2012 - 2 commits
  6. 28 Nov, 2012 - 1 commit
  7. 16 Nov, 2012 - 3 commits
  8. 15 Nov, 2012 - 2 commits
    • John Koleszar's avatar
      support building vp8 and vp9 into a single lib · a9c7597a
      John Koleszar authored
      Change-Id: Ib8f8a66c9fd31e508cdc9caa662192f38433aa3d
      a9c7597a
    • John Koleszar's avatar
      make: flatten object file directories · b72373de
      John Koleszar authored
      Rather than building an object file directory heirarchy matching the
      source tree's layout, rename the object files so that the object
      file name contains the path in the source file tree. The intent here
      is to allow two files in different parts of the source tree to have
      the same name and still not collide when put into an ar archive.
      
      Change-Id: Id627737dc95ffc65b738501215f34a995148c5a2
      b72373de
  9. 01 Nov, 2012 - 1 commit
  10. 21 Aug, 2012 - 2 commits
  11. 15 Aug, 2012 - 1 commit
    • James Zern's avatar
      fix msvc configure · 97fd7c5e
      James Zern authored
      visual studio targets do not depend on executables, only the projects
      produced.
      tested with --target=x86-win32-vs9
      fixes:
      ...
      make[1]: *** No rule to make target `test_libvpx', needed by `.bins'.
      Stop.
      Makefile:17: recipe for target `.DEFAULT' failed
      
      Change-Id: I606ab32d5e26fee352f25c822e0f496eff165382
      97fd7c5e
  12. 09 Aug, 2012 - 1 commit
  13. 08 Aug, 2012 - 1 commit
  14. 26 Jul, 2012 - 1 commit
  15. 23 Jul, 2012 - 1 commit
  16. 29 Jun, 2012 - 1 commit
    • John Koleszar's avatar
      Build unit test driver from the default target · acd147c5
      John Koleszar authored
      We need an easy way to build the unit test driver without running the
      tests. This enables passing options like --gtest_filter to the
      executable, which can't be done very cleanly when running under
      `make test`.
      
      Fixed a number of compiler errors/warnings when building the tests
      in various configurations by Jenkins.
      
      Change-Id: I9198122600bcf02520688e5f052ab379f963b77b
      acd147c5
  17. 26 Jun, 2012 - 1 commit
  18. 21 Jun, 2012 - 1 commit
    • John Koleszar's avatar
      Add support for downloading test data · 00748632
      John Koleszar authored
      The commit introduces a make target 'testdata' that downloads the
      required test data from the WebM project website. The data will also
      be downloaded if invoking `make test` but is not a strict requirement
      for only building the test executable.
      
      The download directory is taken from the LIBVPX_TEST_DATA_PATH
      environment variable, or may be specified as part of the make command.
      If unset, it defaults to the current directory. It's expected that
      most developers will want to set this environment variable to a place
      outside their source/build trees, to avoid having to download the data
      more than once.
      
      To add test data file:
      
        1) add a line to test/test.mk:
      
            LIBVPX_TEST_DATA-yes += foo-bar-file.y4m
      
        2) add its sha1sum to the test/test-data.sha1 file in the following
           format:
      
            528cc88c821e5f5b133c2b40f9c8e3f22eaacc4c  foo-bar-file.y4m
      
        3) upload the file to the website
      
            $ gsutil cp foo-bar-file.y4m gs://downloads.webmproject.org/test_data/libvpx
      
      This implementation will check the integrity of the test data
      automatically if the `sha1sum` executable is available.
      
      Change-Id: If6910fe304bb3f5cdcc5cb9e5f9afa5be74720d2
      00748632
  19. 19 Jun, 2012 - 1 commit
  20. 15 Jun, 2012 - 1 commit
    • Rob Bradford's avatar
      Fix pkg-config file to pull in libm · 576629ba
      Rob Bradford authored
      vpx uses symbols in libm and thus we need to provide an indication to
      the user of libvpx that if they want to link against libvpx they must
      also link against libm.
      
      Change-Id: I31d4068bf7f6f5b1fd222bcdf9e6a1a92fb6696f
      576629ba
  21. 09 Jun, 2012 - 1 commit
  22. 01 Jun, 2012 - 1 commit
    • John Koleszar's avatar
      Fix MSVS builds for unit test changes · 7f63bfa6
      John Koleszar authored
      Update the Visual Studio builds to support the new monolithic unit
      test binary.
      
      Includes minor semi-cosmetic refactoring of solution.mk, as the
      %vpx.vcproj match is no longer appropriate given the test_libvpx
      target.
      
      Change-Id: I29e6e07c39e72b54a4b3eaca5b9b7877ef3fb134
      7f63bfa6
  23. 22 May, 2012 - 2 commits
    • John Koleszar's avatar
      Build unit tests monolithically · e82d261d
      John Koleszar authored
      Rework unit tests  to have a single executable rather than many, which
      should avoid pollution of the visual studio project namespace, improve
      build times, and make it easier to use the gtest test sharding system
      when we get these going on the continuous build cluster.
      
      Change-Id: If4c3e5d4b3515522869de6c89455c2a64697cca6
      e82d261d
    • John Koleszar's avatar
      configure: initial support for CXX, CXXFLAGS variables · 8631c1b8
      John Koleszar authored
      Use CXX rather than assuming g++ to invoke the compiler. Also introduce
      separate CXXFLAGS, as certain CFLAGS we enable by default cause warnings
      with g++.
      
      Change-Id: Ia2f40ef27c93e45c971d070cc58bdcde9da2ac7c
      8631c1b8
  24. 11 May, 2012 - 1 commit
  25. 04 May, 2012 - 1 commit
    • John Koleszar's avatar
      remove deprecated pre-v0.9.0 API · 2bf8fb58
      John Koleszar authored
      Remove a bunch of compatibility code dating back to before the initial
      libvpx release.
      
      Change-Id: Ie50b81e7d665955bec3d692cd6521c9583e85ca3
      2bf8fb58
  26. 02 May, 2012 - 1 commit
  27. 20 Apr, 2012 - 1 commit
  28. 16 Mar, 2012 - 1 commit
    • Johann's avatar
      darwin universal builds need BUILD_PFX · 56e8485c
      Johann authored
      Universal builds create subdirectories for each target. Without
      BUILD_PFX we only generated one vpx_rtcd.h instead of one for each.
      
      Change-Id: I1caed4e018c8865ffc8da15e434cae2b96154fb4
      56e8485c
  29. 14 Mar, 2012 - 1 commit
  30. 06 Mar, 2012 - 1 commit
    • Johann's avatar
      include CHANGELOG in CODEC_SRCS · 5d88a82a
      Johann authored
      build/make/version.sh requires CHANGELOG to generate vpx_version.h
      The file is already included when building the documentation. However,
      documentation is not build if doxygen/php are not present.
      
      This is necessary when using '--enable-install-srcs --enable-codec-srcs'
      and 'make dist'
      
      Change-Id: Icada883a056a4713d24934ea44e0f6969b68f9c2
      5d88a82a
  31. 17 Feb, 2012 - 1 commit
  32. 15 Feb, 2012 - 1 commit
  33. 30 Jan, 2012 - 1 commit
    • John Koleszar's avatar
      New RTCD implementation · a910049a
      John Koleszar authored
      This is a proof of concept RTCD implementation to replace the current
      system of nested includes, prototypes, INVOKE macros, etc. Currently
      only the decoder specific functions are implemented in the new system.
      Additional functions will be added in subsequent commits.
      
      Overview:
        RTCD "functions" are implemented as either a global function pointer
        or a macro (when only one eligible specialization available).
        Functions which have RTCD specializations are listed using a simple
        DSL identifying the function's base name, its prototype, and the
        architecture extensions that specializations are available for.
      
      Advantages over the old system:
        - No INVOKE macros. A call to an RTCD function looks like an ordinary
          function call.
        - No need to pass vtables around.
        - If there is only one eligible function to call, the function is
          called directly, rather than indirecting through a function pointer.
        - Supports the notion of "required" extensions, so in combination with
          the above, on x86_64 if the best function available is sse2 or lower
          it will be called directly, since all x86_64 platforms implement
          sse2.
        - Elides all references to functions which will never be called, which
          could reduce binary size. For example if sse2 is required and there
          are both mmx and sse2 implementations of a certain function, the
          code will have no link time references to the mmx code.
        - Significantly easier to add a new function, just one file to edit.
      
      Disadvantages:
        - Requires global writable data (though this is not a new requirement)
        - 1 new generated source file.
      
      Change-Id: Iae6edab65315f79c168485c96872641c5aa09d55
      a910049a