1. 23 Mar, 2019 1 commit
  2. 28 Jan, 2019 1 commit
  3. 05 Oct, 2018 1 commit
    • Emmanuele Bassi's avatar
      Set all auto-features as enabled with Meson · 13e5b3c5
      Emmanuele Bassi authored
      Meson added "auto features", i.e. options that can have a tri-state
      "auto/enable/disable" value. Auto-builders, like Continuous, should only
      ever rely on explicit configuration option, in order to increase the
      likelihood of a reproducible build; for this use case, Meson allows to
      automatically set all auto-features to the "enable" state. This means
      that, for any Meson-based module, any feature detection that uses an
      auto-feature will either succeed or fail because of a missing
      dependency, and it's up to us to enable or disable the feature
      explicitly in the module's "config-opts" key.
  4. 07 Jun, 2018 1 commit
    • Emmanuele Bassi's avatar
      Disable downloading subprojects with Meson · 85ca2448
      Emmanuele Bassi authored
      Meson allows downloading wrapped subprojects, but since we're building
      everything inside a sandbox with no networking support we cannot ever
      allow downloads happening at configuration time — as they'll fail
  5. 01 Dec, 2017 2 commits
  6. 29 Nov, 2017 10 commits
    • Emmanuele Bassi's avatar
      Provide fallback values for CC and CXX · 1fe570f3
      Emmanuele Bassi authored
      If CC and CXX are unset, distutils will fail miserably and use the C
      compiler that was used to build it — which, in the case of Continuous,
      is the C compiler used inside the Yocto base, and which tries to access
      the system includes outside of the sandbox.
      Let's fall back to 'gcc' and 'g++' until the glorious day when we can
      take distutils and dump it in a very dark and deep pit.
    • Emmanuele Bassi's avatar
      Add more debugging messages · af5542d9
      Emmanuele Bassi authored
    • Emmanuele Bassi's avatar
      Log the compiler in use · 1e3f4a6c
      Emmanuele Bassi authored
      This is mostly for debugging distutils and ninja picking up the wrong
      compiler, and thus the wrong set of headers.
    • Emmanuele Bassi's avatar
      Ensure we pass the correct environment to ninja · b28c5a50
      Emmanuele Bassi authored
      When using make, we pass variables as arguments; for ninja, we need to
      put those variables into the environment.
    • Emmanuele Bassi's avatar
      Remove trailing colon · 7da1a688
      Emmanuele Bassi authored
    • Emmanuele Bassi's avatar
      Allow forcing autotools for components with mixed builds · c5b7de2c
      Emmanuele Bassi authored
      If a component has a mixed Autotools and Meson builds, allow selecting
      the Autotools build, in case the Meson one is still experimental.
    • 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.
    • 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
    • Emmanuele Bassi's avatar
      Fix compiler script · 7480e84e
      Emmanuele Bassi authored
      Python does not help when it should.
    • 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
  7. 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:
      we're going to switch to C.UTF-8.
  8. 24 Apr, 2017 2 commits
  9. 05 Apr, 2017 1 commit
  10. 01 Mar, 2017 2 commits
  11. 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.
  12. 09 Oct, 2016 2 commits
  13. 21 Mar, 2016 1 commit
  14. 12 Feb, 2016 3 commits
  15. 11 Feb, 2016 1 commit
  16. 10 Feb, 2016 1 commit
  17. 28 Jan, 2016 1 commit
  18. 27 Jan, 2016 1 commit
  19. 30 Sep, 2015 2 commits
  20. 18 Sep, 2015 1 commit
  21. 11 Sep, 2015 2 commits
  22. 08 Sep, 2015 1 commit
  23. 13 Aug, 2015 1 commit