1. 29 Nov, 2017 4 commits
    • Emmanuele Bassi's avatar
      Do not overwrite variables · 53f2d79c
      Emmanuele Bassi authored
      We're using the same variable for two separate iterations, so we need to
      make sure that we're not overwriting its value.
      53f2d79c
    • Emmanuele Bassi's avatar
      Check for Ninja first · 4255b51d
      Emmanuele Bassi authored
      Some projects do not use Autotools, but still provide a Makefile. If we
      don't find a Ninja build rules file, let's fall back to the previous
      behaviour.
      4255b51d
    • Emmanuele Bassi's avatar
      Fix compiler script · 7480e84e
      Emmanuele Bassi authored
      Python does not help when it should.
      7480e84e
    • Emmanuele Bassi's avatar
      Support Meson natively · 70d8ae57
      Emmanuele Bassi authored
      The build API did not catch on outside of Autotools, and Autotools
      already conform to that API.
      
      Instead of filling up the build with downstream patches and dealing
      with projects breaking the build when moving to Meson, let's stop
      pretending other build systems do not exist.
      
      This change requires various modifications that have to land at the
      same time in order to avoid breaking the build:
      
       - we need to modify the wrapper script we use to build each
         component, so that it can detect Meson and invoke it, and
         Ninja, appropriately
       - we need to modify the manifest to drop global configuration
         options that only apply to Autotools, and which will make
         Meson choke
       - we need to turn configuration options we set using the
         Autotools syntax into ones that Meson understands; this also
         means taking default values encoded inside compatibility
         patches
      70d8ae57
  2. 10 Jul, 2017 1 commit
    • Emmanuele Bassi's avatar
      Do yet another attempt at a UTF-8 locale · 7f996d13
      Emmanuele Bassi authored
      We build inside a Yocto build root, and since Yocto does not ship with a
      patched GNU libc to provide a C.UTF-8 locale (like Fedora and Debian do)
      we need to use a valid locale otherwise we're going to break everything.
      
      The image we build defaults to en_US.UTF-8, so let's use the same locale
      during the build.
      
      At some point, with a newer version of Yocto and a newer GNU libc that
      solves this:
      
        https://sourceware.org/glibc/wiki/Proposals/C.UTF-8
      
      we're going to switch to C.UTF-8.
      7f996d13
  3. 24 Apr, 2017 2 commits
  4. 05 Apr, 2017 1 commit
  5. 01 Mar, 2017 2 commits
  6. 27 Feb, 2017 1 commit
    • Emmanuele Bassi's avatar
      Use a UTF-8 locale for the build environment · 58ced5f2
      Emmanuele Bassi authored
      It's 2017. As much as using a C locale is the correct choice, we're
      using Unicode in file names and build messages, these days, which means
      that we need to be able to write Unicode to the terminal and logs.
      58ced5f2
  7. 09 Oct, 2016 2 commits
  8. 21 Mar, 2016 1 commit
  9. 12 Feb, 2016 3 commits
  10. 11 Feb, 2016 1 commit
  11. 10 Feb, 2016 1 commit
  12. 28 Jan, 2016 1 commit
  13. 27 Jan, 2016 1 commit
  14. 30 Sep, 2015 2 commits
  15. 18 Sep, 2015 1 commit
  16. 11 Sep, 2015 2 commits
  17. 08 Sep, 2015 1 commit
  18. 13 Aug, 2015 6 commits
  19. 12 Aug, 2015 1 commit
  20. 15 Jun, 2015 1 commit
  21. 10 Jun, 2015 1 commit
  22. 01 Jun, 2015 1 commit
    • Jasper St. Pierre's avatar
      testbase: Fix source ID warning · 735b0e38
      Jasper St. Pierre authored
      This has been bugging me for a bit. Basically, the timeout already
      returns a false-y value, so the source_remove has always been
      invalid. Add an explicit return to timeout, and remove the explicit
      source_remove.
      735b0e38
  23. 30 Mar, 2015 1 commit
  24. 27 Mar, 2015 2 commits