1. 16 Mar, 2018 1 commit
  2. 13 Mar, 2018 1 commit
  3. 14 Feb, 2018 2 commits
    • Matthias Clasen's avatar
      3.22.28 · 463ee951
      Matthias Clasen authored
      463ee951
    • Carlos Garnacho's avatar
      modules: Add wayland IM implementation · e8bffe0c
      Carlos Garnacho authored
      This IM context implementation goes through the gtk-text-input protocol,
      leaving up to the compositor the actual interaction with IM engines. If
      the protocol is not offered by the compositor, GTK+ will fallback to the
      IMs as specified through GtkSettings.
      e8bffe0c
  4. 13 Feb, 2018 1 commit
  5. 02 Jan, 2018 1 commit
    • Ting-Wei Lan's avatar
      configure: Don't declare functions in AC_TRY_COMPILE and AC_LANG_PROGRAM · 31f7b553
      Ting-Wei Lan authored
      Both AC_TRY_COMPILE and AC_LANG_PROGRAM put code passed to their second
      arguments to the body of the main function. This means that we cannot
      and should not declare functions there, or we end up checking whether
      the compiler support nested functions instead of whether a compiler or
      linker flag is supported.
      
      GCC supports nested functions and tests succeed. Clang doesn't support
      nested functions, so tests fail and -fvisibility=hidden won't be used.
      This means that functions which are not intended to be used by other
      programs, such as gtk_menu_tracker*, gtk_action_observ*,
      gtk_menu_muxer_*, become global symbols with default visibility.
      
      GNOME Shell has a private library libgnome-shell-menu.so, which also has
      symbols gtk_menu_tracker*, gtk_action_observ*, gtk_menu_muxer_* that are
      intended to be used by GNOME Shell itself. When GNOME Shell still used
      Autotools build system, the executable gnome-shell explicitly linked to
      libgnome-shell-menu.so, so the linker loaded libgnome-shell-menu.so
      before libgtk-3.so.0 and GNOME Shell used correct symbols from its
      private library.
      
      However, after GNOME Shell switched to Meson build system, gnome-shell
      executable no longer lists libgnome-shell-menu.so as its dependency.
      Even if we adds it to the build file, it won't be listed in DT_NEEDED of
      gnome-shell because Meson uses -Wl,--as-needed by default. This causes
      the runtime linker to load libgtk-3.so.0 before libgnome-shell-menu.so
      and symbols gtk_menu_tracker*, gtk_action_observ*, gtk_menu_muxer_* are
      bound to libgtk-3.so.0 instead of libgnome-shell-menu.so. GNOME Shell
      hangs when opening more than one window because it uses functions from
      the wrong library.
      
      This problem is already fixed in OpenBSD ports. The article describing
      it can be found on OpenBSD Journal with this link:
      https://undeadly.org/cgi?action=article;sid=20170930133438
      
      https://bugzilla.gnome.org/show_bug.cgi?id=791943
      31f7b553
  6. 13 Nov, 2017 1 commit
  7. 07 Nov, 2017 1 commit
  8. 29 Oct, 2017 1 commit
  9. 04 Oct, 2017 2 commits
  10. 02 Oct, 2017 1 commit
  11. 11 Sep, 2017 1 commit
  12. 04 Sep, 2017 2 commits
  13. 25 Aug, 2017 1 commit
  14. 22 Aug, 2017 1 commit
  15. 14 Aug, 2017 1 commit
  16. 07 Aug, 2017 1 commit
  17. 02 Aug, 2017 1 commit
  18. 19 Jul, 2017 1 commit
  19. 20 Jun, 2017 1 commit
  20. 11 May, 2017 1 commit
  21. 10 May, 2017 2 commits
  22. 09 May, 2017 2 commits
  23. 08 Apr, 2017 1 commit
  24. 03 Apr, 2017 1 commit
  25. 19 Mar, 2017 1 commit
  26. 14 Mar, 2017 1 commit
  27. 27 Feb, 2017 1 commit
  28. 17 Feb, 2017 1 commit
    • Chun-wei Fan's avatar
      Visual Studio builds: Support Visual Studio 2017 · c6f0df26
      Chun-wei Fan authored
      Update the autotools scripts so that we can support Visual Studio 2017
      by copying the 2010 projects and updating items as needed to obtain
      the 2017 projects.
      
      Note that since the toolset version string changed for Visual Studio
      2017, so allow the use of a custom toolset version string, otherwise
      just generate the toolset version string as we did before.
      
      Also, note that Visual Studio 2017 aims to be compatible with 2015
      on the CRT level, so there should not be any problems using 2017-compiled
      binaries with 2015-compiled ones.
      c6f0df26
  29. 13 Feb, 2017 1 commit
  30. 16 Jan, 2017 1 commit
  31. 05 Jan, 2017 1 commit
  32. 04 Jan, 2017 1 commit
  33. 19 Dec, 2016 1 commit
  34. 09 Dec, 2016 1 commit
  35. 18 Nov, 2016 1 commit