1. 18 Jan, 2019 1 commit
  2. 14 Jan, 2019 1 commit
  3. 13 Jan, 2019 1 commit
  4. 14 Dec, 2018 1 commit
  5. 13 Dec, 2018 1 commit
  6. 08 Dec, 2018 1 commit
    • Nicolas Dufresne's avatar
      ninja: Don't rely on the shebang · a8b5b66b
      Nicolas Dufresne authored
      The configure script supports python3, but the shebang points to python.
      This increase the amount of system setup required, so simply inforce
      using python3.
      a8b5b66b
  7. 05 Dec, 2018 1 commit
  8. 14 Nov, 2018 1 commit
    • Nirbheek Chauhan's avatar
      orc.recipe: Port to meson · 775d3198
      Nirbheek Chauhan authored
      Do the same for the build-tools recipe too. Starting with the next
      release, we can start using the tarball. Need master for the latest
      meson build file fixes.
      775d3198
  9. 12 Nov, 2018 2 commits
  10. 10 Nov, 2018 1 commit
  11. 29 Oct, 2018 1 commit
  12. 28 Oct, 2018 1 commit
  13. 24 Oct, 2018 1 commit
  14. 16 Oct, 2018 1 commit
    • Matthew Waters's avatar
      bootstrap: always build glib-tools when targetting non-linux · e2849eeb
      Matthew Waters authored
      Fixes out of date glib tools throwing errors.
      
      /usr/bin/glib-genmarshal --prefix _gdk_pixbuf_marshal --output gdk-pixbuf/gdk-pixbuf-marshal.h --pragma-once --header ../gdk-pixbuf/gdk-pixbuf-marshal.list
      FAILED: gdk-pixbuf/gdk-pixbuf-marshal.h
      /usr/bin/glib-genmarshal --prefix _gdk_pixbuf_marshal --output gdk-pixbuf/gdk-pixbuf-marshal.h --pragma-once --header ../gdk-pixbuf/gdk-pixbuf-marshal.list
      
      (process:12337): GLib-Genmarshal-WARNING **: failed to open "--output": No such file or directory
      
      (process:12337): GLib-Genmarshal-WARNING **: failed to open "gdk-pixbuf/gdk-pixbuf-marshal.h": No such file or directory
      
      (process:12337): GLib-Genmarshal-WARNING **: failed to open "--pragma-once": No such file or directory
      
      ...
      e2849eeb
  15. 02 Oct, 2018 1 commit
  16. 20 Sep, 2018 1 commit
  17. 19 Sep, 2018 1 commit
  18. 30 Aug, 2018 2 commits
  19. 29 Aug, 2018 2 commits
  20. 17 Aug, 2018 3 commits
  21. 10 Aug, 2018 1 commit
  22. 07 Aug, 2018 3 commits
  23. 22 Jul, 2018 2 commits
  24. 21 Jul, 2018 1 commit
    • Nirbheek Chauhan's avatar
      cerbero: Rework environment modification in recipes · 7462b065
      Nirbheek Chauhan authored
      
      
      Environment variable modification in a recipe used to be done with:
      
        self.append_env, self.prepend_env, or self.new_env
      
      All of these were dictionaries of {string:string} mappings, which
      means that if a recipe wanted to, say, append to `CFLAGS` from
      multiple places within the recipe (f.ex., `glib.recipe`), you had to
      carefully juggle `=` and `+=` in recipes, which was error-prone
      (f.ex., `gstreamer-1.0.recipe` `variants.nodebug` was broken).
      
      Now that we also conditionally use `self.append_env['CFLAGS']` in
      `cerbero/build/build.py` for bitcode support with make-based build
      systems, it's impossible to get this right in recipes. This was
      causing the cross-ios-universal builds to fail on recipes that
      directly set `self.append_env['CFLAGS'] = 'foo'` such as pixman.
      
      The dictionaries have now been replaced with the following functions:
      
        self.append_env(varname, value1, value2, ..., sep=separator)
        self.prepend_env(varname, value1, value2, ..., sep=separator)
        self.set_env(varname, value1, value2, ..., sep=separator)
      
      The separator is used to join value1, value2, etc and also while
      appending/prepending to the value in the env. It is optional, and
      defaults to ` ` (space).
      
      Most often the usage is very simple to translate:
      
        self.append_env['CFLAGS'] = ' -funroll-loops '
        =>
        self.append_env('CFLAGS', '-funroll-loops')
      
      If values are omitted with `self.set_env()`, the variable is unset:
      
        self.new_env['MAKEFLAGS'] = None
        =>
        self.set_env('MAKEFLAGS')
      
      An important intended feature is that multiple calls to these
      functions all take effect sequentially at build time for each build
      step. So, you can call append and prepend multiple times on the same
      variable, and the values will be appended and prepended in that order
      to the value at build time.
      
      Note that if you call `self.set_env()` on a variable, the variable will,
      of course, be set to that value and previous append/prepend
      declarations will be overriden.
      Reviewed-by: default avatarJan Schmidt <jan@centricular.com>
      7462b065
  25. 05 Jul, 2018 1 commit
  26. 30 Jun, 2018 1 commit
  27. 28 Jun, 2018 1 commit
  28. 20 Jun, 2018 1 commit
  29. 07 Jun, 2018 1 commit
  30. 24 May, 2018 2 commits
  31. 22 May, 2018 1 commit