Skip to content
  1. Dec 21, 2014
  2. Nov 25, 2014
    • Philip Chimento's avatar
      build: Use m4 directory for macros · 0f45dc03
      Philip Chimento authored
      Previously, ACLOCAL_AMFLAGS was set to ${ACLOCAL_FLAGS}. This caused
      problems when running libtoolize --force --copy as part of autoreconf.
      On JHBuild when ACLOCAL_FLAGS was set to the build tree's share/aclocal
      directory, libtoolize would actually remove the libtool macros from
      there.
      0f45dc03
  3. Nov 06, 2014
    • Philip Chimento's avatar
      build: Use -R instead of -rpath · 8c53b716
      Philip Chimento authored
      When linking with libtool, you are supposed to use -R, not -rpath. This
      caused a build failure on OSX due to two -rpath options being given in
      one invocation of ld, which libtool fixes when you use -R.
      8c53b716
    • Philip Chimento's avatar
      build: Don't error out on missing cairo-xlib.pc · a9723e10
      Philip Chimento authored
      When building on OSX, we would be using Cairo without XLib support, so
      instead of erroring out if pkg-config can't find cairo-xlib, print a
      warning. The X-based code will not be used anyway if Cairo hasn't
      detected XLib.
      a9723e10
  4. Oct 28, 2014
  5. Sep 29, 2014
  6. Sep 18, 2014
  7. Sep 01, 2014
  8. Aug 25, 2014
  9. Aug 23, 2014
  10. Aug 11, 2014
  11. Jul 30, 2014
  12. Jul 22, 2014
  13. Jul 17, 2014
  14. Jul 07, 2014
  15. Jul 03, 2014
  16. Jun 25, 2014
  17. Jun 15, 2014
  18. May 02, 2014
  19. Apr 12, 2014
  20. Apr 11, 2014
    • Giovanni Campagna's avatar
      Ratelimit RSS-triggered GCs · 791b1a33
      Giovanni Campagna authored
      When loading a lot of data in memory (for example in the shell
      opening the overview, which loads all the desktop files and icons)
      the RSS can increase a lot, so we would trigger GCs continously
      without any hope of freeing memory, so ratelimit full GCs to at
      most one every 5 frames.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=728048
      791b1a33
    • Lionel Landwerlin's avatar
      gi: arg: use instance's gtype rather than the introspection data · 6cfbeed1
      Lionel Landwerlin authored
      When converting a native object to it's JavaScript proxy, we want to
      be as precise as possible to map that native object.
      Right now we handle different kinds of proxy for native types :
            * GObject proxies
            * GBoxed proxies
            * GParam proxies
            * GError proxies
            * Function proxies
            * Unions proxies
            * GI proxies
            * Fundamental proxies
            * basic types
      
      The introspection data can provide information that helps us map a
      GType to one of the items listed above. But there is a case that is
      rather painful to deal with : interfaces.
      
      In GObject interfaces can be attached to different kind of GTypes
      (that includes GObjects and custom fundamental types and maybe more, I
      haven't checked all the twisted cases). Although there is a way to add
      a prerequisite for an interface, not all interface properly use this
      feature.
      
      In this particular case (native -> JS) we can use the native object's
      gtype to figure out the most appropriate proxy, which what this patch
      implements.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=727824
      6cfbeed1
    • Lionel Landwerlin's avatar
      installed-tests: fix deactivated GIMarshalling test suite · a6d342ba
      Lionel Landwerlin authored
      I believe when the installed test suite got created, the way JS files
      are loaded changed. That resulted in the window object being different
      from the scope of the test files, leaving that particular test suite
      disabled.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=728004
      a6d342ba
  21. Apr 10, 2014