1. 14 May, 2021 1 commit
  2. 11 May, 2020 1 commit
  3. 03 Apr, 2020 1 commit
    • Nirbheek Chauhan's avatar
      pkg-config.recipe: Always auto-detect the prefix · 0ce2435e
      Nirbheek Chauhan authored
      With this, the `prefix` variable in .pc files will be automatically
      detected based on the location of the .pc file. This allows for
      portable prefixes.
      
      This is the recommended configuration on Windows and macOS. We need to
      enable this since we ship pkg-config with the release binaries now.
      0ce2435e
  4. 05 Nov, 2019 1 commit
  5. 15 Oct, 2019 1 commit
  6. 04 Feb, 2019 1 commit
    • Nirbheek Chauhan's avatar
      licenses: Fix a couple of licenses and remove unused enums · 24fa8408
      Nirbheek Chauhan authored
      freetype: You have to pick between FTL and GPLv2
      frei0r-plugins: It's GPLv2+, not LGPL
      openssl: Obviously, OpenSSL not BSD
      harfbuzz: Actually BSD, not LGPLv2+
      lame: transitioned to LGPL2, no longer GPL
      nettle/gmp: licensed under all three licenses
      osx-framework: No license, just copying of files from other recipes
      gst-shell, vsintegration, etc: Match with gstreamer's license
      toolchain: All LGPLv2+, GPLv2+, or GPLv3+
      other recipes: verified by `diff -uw` on license
      
      Remove most unused license enums, except Proprietary
      24fa8408
  7. 19 Sep, 2018 1 commit
  8. 22 Jul, 2018 1 commit
  9. 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
  10. 08 Feb, 2018 1 commit
  11. 29 Jun, 2017 1 commit
    • Matthew Waters's avatar
      build-tools: update pkg-config to 0.19.2 · e3bf2ee5
      Matthew Waters authored
      Fixes build with newer gcc
      
      gdate.c: In function ‘g_date_strftime’:
      gdate.c:2497:7: error: format not a string literal, format string not checked [-Werror=format-nonliteral]
             tmplen = strftime (tmpbuf, tmpbufsize, locale_format, &tm);
             ^~~~~~
      cc1: some warnings being treated as errors
      make[6]: *** [Makefile:1387: libglib_2_0_la-gdate.lo] Error 1
      e3bf2ee5
  12. 16 Dec, 2016 1 commit
  13. 16 Oct, 2013 2 commits
  14. 30 Sep, 2013 1 commit
  15. 16 Nov, 2012 2 commits
  16. 26 Oct, 2012 1 commit
  17. 25 Oct, 2012 1 commit