Skip to content
Snippets Groups Projects
  1. Jun 16, 2023
  2. Jun 01, 2020
  3. Apr 03, 2019
  4. Nov 07, 2017
  5. Feb 15, 2017
    • Jean-Marc Valin's avatar
      Adding a unit test for LPC_inv_pred_gain() · 68688651
      Jean-Marc Valin authored
      It checks that no clearly unstable filter passes the LPC_inv_pred_gain()
      test. Also, this will make it possible to check assembly for correctness.
      
      Modified from an original patch from Linfeng Zhang <linfengz@google.com>.
      Verified
      68688651
  6. May 18, 2016
  7. May 17, 2016
  8. May 11, 2016
  9. May 20, 2013
    • Ron's avatar
      Add support for autoconf macros in m4/ · 50b395bf
      Ron authored
      Needed by commit 972a34ec.
      
      Use autoreconf in autogen.sh instead of the handwritten version,
      it's simpler, and also updates things that we weren't handling.
      
      Drop the hand-written INSTALL file.  Its information content was
      ~zero, and autotools wants to overwrite it with its own version,
      so don't fight that, just .gitignore it.
      50b395bf
  10. May 10, 2013
    • Ron's avatar
      More gitignorance · 113242ca
      Ron authored
      113242ca
    • Ron's avatar
      Fully automate version updating · 2f2f9d63
      Ron authored
      This one meets or exceeds the following requirements:
      
       - Version is checked/updated for every build action when in the git repo.
         Does not require the user to re- ./configure to get the correct version.
      
       - Version is not updated automatically when using exported tarball source.
         Avoids accidentally getting a wrong version from some other git repo in
         a parent directory of the source, and allows setting the correct version
         for distro package exports.
      
       - Automatic updating can be manually suppressed.
         For developers doing lots of change/rebuild cycles they don't plan to
         release, when they don't want a full rebuild triggered for every commit,
         and again for every change made immediately after a commit.
         The version will still always be updated if they do a `make dist`.
      
       - Does not require any manual updating of versions in the mainline git
         repo for each release aside from normal tagging.  The version is
         recorded in one file only, that is automatical...
      2f2f9d63
  11. Oct 11, 2012
  12. Aug 16, 2012
  13. Jul 30, 2012
  14. Jul 20, 2012
  15. Sep 14, 2011
  16. Sep 01, 2011
  17. Apr 28, 2011
  18. Jul 03, 2010
  19. Nov 30, 2007
Loading