1. 05 Aug, 2015 1 commit
  2. 05 Jun, 2015 1 commit
    • James Zern's avatar
      vs/armv7: use -oldit armasm flag · 5908e0b6
      James Zern authored
      this quiets warnings from armv6 code [1].
      from msdn [2]:
      -oldit
      Generate ARMv7-style IT blocks. By default, ARMv8-compatible IT blocks
      are generated.
      
      a new configuration would be needed for armv8 in any case as the neon
      assembly is being built, so removing this should be harmless
      
      [1] A4509: This form of conditional instruction is deprecated
      [2] https://msdn.microsoft.com/en-us/library/hh873189.aspx
      
      Change-Id: I4c3b838b52a87401c6daecd83d22ab148ed7c5d9
      5908e0b6
  3. 07 Nov, 2014 1 commit
    • Johann's avatar
      Remove asm offset dependencies · 6eec73a7
      Johann authored
      The obj_int_extract code is no longer worth maintaining. It creates
      significant issues when adapting for different build systems and no
      longer offers as significant of a performance benefit due to
      improvements in intrinsics.
      
      Source files will remain until the various third-party builds are updated.
      
      The neon fast quantizer has been moved to intrinsics. The armv6 version
      has been removed because so few remaining targets require it.
      
      Compilers and processors have improved significantly since the
      pack_tokens code was written. The assembly is no longer faster than the
      C code.
      
      pack_tokens were the only optimizations for the armv5te targets so the targets
      will be removed after the test infrastructure has been updated.
      
      BUG=710
      
      Change-Id: Ic785b167cd9f95eeff31c7c76b7b736c07fb30eb
      6eec73a7
  4. 22 Aug, 2014 1 commit
    • James Zern's avatar
      gen_msvs_(vcx)proj.sh: set yasm format explicitly · c5795d8f
      James Zern authored
      use win32/win64 instead of $(PlatformName) (Win32/x64) for compatibility
      with yasm 1.3.0. both format types were available since at least 0.8.0
      
      BUG=843
      
      Change-Id: I7917620490d0663b118ff08b96d1e5dbccba3703
      c5795d8f
  5. 16 Jun, 2014 1 commit
    • James Zern's avatar
      gen_msvs_proj: fix in tree configure under cygwin · 0a049261
      James Zern authored
      strip trailing '/' from paths, this is later converted to '\' which
      causes execution errors for obj_int_extract/yasm. vs10+ wasn't affected
      by this issue, but make the same change for consistency.
      
      gen_msvs_proj:
      + add missing '"' to obj_int_extract call
        unlike gen_msvs_vcproj, the block is duplicated
        missed in: 1e3d9b9e build/msvs: fix builds in source dirs with spaces
      
      Change-Id: I76208e6cdc66dc5a0a7ffa8aa1edbefe31e4b130
      0a049261
  6. 07 Jun, 2014 1 commit
  7. 03 Jun, 2014 1 commit
  8. 02 Jun, 2014 1 commit
    • James Zern's avatar
      build/msvs: fix builds in source dirs with spaces · 1e3d9b9e
      James Zern authored
      ...when configured below the path containing spaces. configuring outside
      the path containing spaces still won't work due to issues with the
      makefiles, e.g.,
      /path with spaces/git
      /path with spaces/build1
      /build2
      configure/make in build1 will work, build2 will not
      
      Change-Id: Ie4a1f313596d7457cadd67476ac1dbd3273ad46e
      1e3d9b9e
  9. 05 May, 2014 1 commit
    • Martin Storsjo's avatar
      Fix building for arm with Visual Studio 2013 · 65f13afd
      Martin Storsjo authored
      The microsoft build tools explicitly disallow building for arm in
      the "desktop" target configuration; one has to target "Windows
      Store" apps (aka WinRT/Metro) or Windows Phone. In Visual Studio
      2012, one could just pick the v110_wp80 toolset which made the
      vcxproj files buildable. In Visual Studio 2013, picking the v120_wp81
      toolset isn't enough - one has to configure the vcxproj files
      as an "AppContainerApplication". This has the implication that
      you can't just build a plain .exe (such as the examples) - an .exe
      project would need to have an AppxManifest file. Therefore we can
      only build the library itself.
      
      If loaded into Visual Studio for Windows (the Windows Store/Phone
      version of Visual Studio, not the Desktop one), the obj_int_extract
      project is omitted since it's treated as incompatible. Building
      from the command line with msbuild works fine though.
      
      The armv7-win32-vs12 target was added as part of a638bdf4 even
      though actual use of it hadn't been tested.
      
      Change-Id: Iee8088252cf790317aeb6b417d29058225f1f629
      65f13afd
  10. 24 Apr, 2014 1 commit
  11. 23 Apr, 2014 1 commit
  12. 03 Apr, 2014 1 commit
  13. 08 Mar, 2014 1 commit
    • James Zern's avatar
      gen_msvs_vcxproj.sh: add --enable-werror option · 37c60d82
      James Zern authored
      translates to TreatWarningAsError (/WX)
      setting this via the CL environment variable is not possible due to the
      /WX- default which is used on the command line
      
      Change-Id: I0b42a9d3ca9eba6af82c25b8e434baa2fcb00156
      37c60d82
  14. 21 Feb, 2014 1 commit
    • Tom Finegan's avatar
      obj_int_extract.bat: Pass obj_int_extract.exe path to obj_int_extract.bat. · 1d3ca088
      Tom Finegan authored
      - Update the vcxproj generator to pass the path to the batch file.
      - Update the batch file the take the path to obj_int_extract.exe as arg
        2.
      
      Fixes this warning:
      warning MSB8012: TargetPath does not match Linker's OutputFile property
      value.
      
      Change-Id: I5825f1d1d79f370aeb295bbd2aeb08b22c0e73ab
      1d3ca088
  15. 20 Feb, 2014 2 commits
  16. 12 Feb, 2014 1 commit
    • Tom Finegan's avatar
      gen_msvs_vcxproj.sh: Add /arch:AVX for files using AVX. · 7836e3a5
      Tom Finegan authored
      Turns on AVX when the final characters of .c and .cc file names preceding the
      .c and .cc file extension contain the substrings avx or avx2. This silences
      many MSVC warnings issued during compilation files that use AVX.
      
      Change-Id: I82bda394af7a688679abab2a50dd7e10b3cb0c7a
      7836e3a5
  17. 21 Nov, 2013 1 commit
  18. 14 Nov, 2013 1 commit
  19. 21 May, 2013 3 commits
    • Martin Storsjo's avatar
      Add support for armv7-win32-vs11 · ad484fc6
      Martin Storsjo authored
      The arm assembly files are named .s after conversion, to reuse
      as much of the existing makefile infrastructure for conversion to
      gas format as possible. Within the generated visual studio project,
      only the converted assembly sources are available, which might not
      be optimal for actually developing it, but is acceptable for
      just building the library.
      
      Multithreading is disabled since the traditional win32 threading
      functions aren't available on WinRT/Windows Phone 8.
      
      Building of vpx itself and the examples succeed, while building the
      tests fail due to them using functions not available in the
      windows store/windows phone API subsets - therefore the unit tests
      are disabled.
      
      This works for building in Visual Studio Express 2012 for Windows
      Phone, while Visual Studio Express 2012 for Windows 8 (for
      "Windows Store" apps) seems to reject the vcxproj files due to
      not supporting "classic style native application or managed
      projects". The built static library should be compatible with that
      platform though.
      
      Change-Id: Idcd7eca60bfaaaeb09392a9cd7a02e4a670e3b30
      ad484fc6
    • Martin Storsjo's avatar
      gen_msvs_sln: Support producing versions 10 and 11, handle vcxproj files · cbc8089a
      Martin Storsjo authored
      Change-Id: I3c23a2ce383d9291a823d2be7364608ce0e01570
      cbc8089a
    • Martin Storsjo's avatar
      Add a new script for producing vcxproj files · 56666f07
      Martin Storsjo authored
      Change-Id: If02a7b85f417b9693dcdab73573fc13f67e17016
      56666f07