1. 17 Dec, 2018 6 commits
  2. 14 Dec, 2018 4 commits
  3. 13 Dec, 2018 1 commit
  4. 11 Dec, 2018 8 commits
  5. 10 Dec, 2018 2 commits
  6. 06 Dec, 2018 2 commits
    • Will Thompson's avatar
      gdbus-codegen: don't sort args in --interface-info-body · deafd725
      Will Thompson authored
      Previously, method and signal arguments were sorted by name, which
      (assuming you don't happen to give your arguments
      lexicographically-ordered names) means the generated signatures were
      incorrect when there is more than 1 argument.
      
      While sorting the methods and signals themselves (and properties, and
      annotations on all these) is fine, it's easiest to not sort anything.
      deafd725
    • Will Thompson's avatar
      gdbus-codegen: make --interface-info-{header,body} not crash · faa3c319
      Will Thompson authored
      Since 1217b1bc, LICENSE_STR has taken two
      parameters, not one. Without this change, running either mode fails
      with a traceback like:
      
          Traceback (most recent call last):
            File "../gdbus-codegen", line 55, in <module>
              sys.exit(codegen_main.codegen_main())
            File ".../codegen_main.py", line 294, in codegen_main
              gen.generate()
            File ".../codegen.py", line 896, in generate
              self.generate_body_preamble()
            File ".../codegen.py", line 682, in generate_body_preamble
              self.outfile.write(LICENSE_STR.format(config.VERSION))
          IndexError: tuple index out of range
      
      8916874e, which introduced these flags,
      was actually merged after that commit, but I assume it was written
      beforehand.
      faa3c319
  7. 05 Dec, 2018 2 commits
    • Chun-wei Fan's avatar
      gresources: Add a test with resources > 64kb · cd30faae
      Chun-wei Fan authored
      This is to ensure that the generated code is still compilable by the
      running compiler, and see whether we can read the things in there
      properly.
      
      See issue #1580.
      cd30faae
    • Chun-wei Fan's avatar
      glib-compile-resources: Fix code generation for MSVC builds · 4501807d
      Chun-wei Fan authored
      glib-compile-resources was updated to generate octal byte
      representation in a string, but unfortunately this breaks the build
      on Visual Studio when the generated string sequence exceeds 65535
      characters, which is the imposed limit on Visual Studio compilers.
      
      To make things work on Visual Studio builds and to not slow down things
      on other compilers, generate a code path for Visual Studio an array of
      octal byte representations, as well as a code path for other compilers
      that use the new string representation of octal values, and let the
      compiler take the appropriate code path when compiling the
      generated code.
      
      Fixes issue #1580.
      4501807d
  8. 26 Nov, 2018 3 commits
  9. 25 Nov, 2018 1 commit
  10. 23 Nov, 2018 9 commits
  11. 21 Nov, 2018 2 commits
    • Michael Catanzaro's avatar
      Deprecate TLS rehandshake APIs · 85f7d493
      Michael Catanzaro authored
      Allowing unsafe rehandshakes used to be required for web compatibility,
      but this is no longer a concern in 2018. So there should no longer be
      compatibility benefits to calling this function. All it does is make
      your TLS connection insecure.
      
      Also, rehandshaking no longer exists at all in TLS 1.3.
      
      At some point (maybe soon!) glib-networking will begin ignoring the
      rehandshake mode, so let's deprecate it now.
      85f7d493
    • Michael Catanzaro's avatar
      Update documentation of g_tls_connection_handshake() one last time · 2031e37d
      Michael Catanzaro authored
      Let's entirely deprecate calling this function for rehandshaking. The
      current documentation is OK, but guarantees defined behavior (to attempt
      a rehandshake) when TLS 1.2 is in use. But there's no way to force TLS
      1.2, and also no way to check which version of TLS is in use. I really
      should have deprecated use of this function for rehandshaking entirely
      last time I updated it.
      
      Fortunately, there should be no compatibility risk for existing code,
      because rehandshaking has no visible effects at the API level.
      2031e37d