1. 08 Jul, 2020 1 commit
  2. 27 Jun, 2020 1 commit
  3. 23 Jun, 2020 1 commit
  4. 08 Jun, 2020 1 commit
  5. 28 May, 2020 2 commits
  6. 03 Apr, 2020 1 commit
  7. 27 Mar, 2020 1 commit
  8. 26 Feb, 2020 1 commit
  9. 21 Feb, 2020 1 commit
  10. 03 Dec, 2019 1 commit
  11. 27 Nov, 2019 1 commit
  12. 26 Nov, 2019 1 commit
  13. 25 Jun, 2019 1 commit
    • Nirbheek Chauhan's avatar
      meson and glib: Fix quoting issues with c_args when cross-compiling · 3c264341
      Nirbheek Chauhan authored
      Use shlex.quote for escaping CFLAGS to be more accurate, and also fix
      Meson to correctly quote c_args obtained from the cross file when
      adding them to the compiler rules.
      
      This is already done correctly when adding c_args to the compile
      commands, so this patch is not needed in newer versions of meson and
      does not need to be upstreamed.
      
      Fixes #162
      Also reported at !210
      3c264341
  14. 07 Jun, 2019 1 commit
  15. 15 May, 2019 1 commit
  16. 17 Mar, 2019 1 commit
  17. 07 Mar, 2019 1 commit
    • Nirbheek Chauhan's avatar
      glib.recipe: Use python name not full path in tools · d2a52dc6
      Nirbheek Chauhan authored
      We don't want to hard-code the full path to the Python interpreter
      in the binary output of Cerbero because it might be different on the
      target system. Before:
      
       #!/usr/bin/env /Library/Frameworks/Python.framework/Versions/3.6/bin/python3
      
      Which could be /usr/local/bin/python3, for instance. After:
      
       #!/usr/bin/env python3
      d2a52dc6
  18. 21 Feb, 2019 1 commit
  19. 04 Feb, 2019 1 commit
  20. 14 Jan, 2019 1 commit
  21. 13 Jan, 2019 1 commit
  22. 12 Nov, 2018 1 commit
  23. 24 Oct, 2018 1 commit
  24. 19 Sep, 2018 1 commit
  25. 31 Aug, 2018 1 commit
  26. 29 Aug, 2018 1 commit
  27. 28 Aug, 2018 1 commit
  28. 17 Aug, 2018 1 commit
  29. 23 Jul, 2018 1 commit
  30. 22 Jul, 2018 1 commit
  31. 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
  32. 19 Jul, 2018 2 commits
  33. 14 Jun, 2018 1 commit
  34. 11 Jun, 2018 1 commit
  35. 27 May, 2018 1 commit
  36. 22 May, 2018 2 commits
    • Nirbheek Chauhan's avatar
      glib.recipe: Fix build failure when inside screen on macOS · dc3ff7d4
      Nirbheek Chauhan authored
      The locale is badly defined in that case and "C" is used as the fallback
      locale, which causes Python's open() to barf on utf-8
      dc3ff7d4
    • Nirbheek Chauhan's avatar
      Port glib and glib-networking recipes to meson · 5ff24813
      Nirbheek Chauhan authored
      Also, always use gnutls system trust for glib-networking. This is
      backported from latest master, and we should fix our gnutls config to
      work with this. Porting it in early so we have some time to deal with
      this before the next glib-networking stable release.
      
      Tested on fedora linux, cross-win32/64, cross-android-universal, darwin,
      cross-ios-universal, and windows/mingw.
      5ff24813
  37. 16 May, 2018 1 commit