1. 14 Jun, 2014 1 commit
  2. 27 May, 2014 2 commits
  3. 18 Mar, 2014 1 commit
    • Andrés G. Aragoneses's avatar
      build: linking against dbus-glib-1 is now mandatory (bgo#692374) · abdfd9c0
      Andrés G. Aragoneses authored
      The work-around for this bug was not applied successfully by some
      packagers because we didn't make the dependency mandatory. Now that
      gsettings branch is almost ready to be merged to master (which
      means this workaround would be reverted), it's good if we make sure
      that at least the last GConf-enabled versions don't suffer this bug.
  4. 31 Jan, 2014 1 commit
  5. 08 Jan, 2014 2 commits
    • Andrés G. Aragoneses's avatar
      build: enable tests by default if nunit dep is found (bgo#690010) · 1d486027
      Andrés G. Aragoneses authored
      Instead of disabling tests by default (which is not a good habit
      towards newcomers), or the too optimistic approach of enabling
      them by default, there can be something in between: enable them
      by default if the NUnit dependency is found (allowing the flag
      --disable-tests too), and disable them by default if they are
      not found (allowing --enable-tests flag, which would fail by
      informing the user about what is the dependency and version
    • Andrés G. Aragoneses's avatar
      build: fail if --enable-tests and no nunit found (bgo#664887) · 78d04025
      Andrés G. Aragoneses authored
      As tests are disabled by default, using the flag --enable-tests
      at configure time should fail (and not just warn) and stop the
      build, to let the developer know that the flag could not be
      applied successfully.
  6. 07 Jan, 2014 2 commits
  7. 06 Jan, 2014 1 commit
  8. 29 Dec, 2013 1 commit
    • Bertrand Lorentz's avatar
      WebBrowser: Depend on libsoup >= 2.42, drop libsoup-gnome dependency · 33f8055c
      Bertrand Lorentz authored
      Since 2.42, libsoup-gnome is deprecated and all features are now
      provided by libsoup itself, with saner defaults. So we now require
      version 2.42, which allows us to drop the dependency on libsoup-gnome.
      Note that we still use the GNOME proxy settings when available, as this
      is now done by default by libsoup itself.
  9. 21 Dec, 2013 1 commit
  10. 20 Dec, 2013 1 commit
    • Stephan Sundermann's avatar
      GStreamerSharp: update to work with new 0.99.0 version · 3897cd07
      Stephan Sundermann authored
      The new 0.99.0 version of this binding targets GStreamer 1.0. This
      has been an accomplishment that took many weeks, starting from the
      Gnome .NET 2013 Hackfest in Vienna.
      Contributions from:
       Stephan Sundermann,
       Olivier Dufour,
       Andres G. Aragoneses
  11. 19 Dec, 2013 1 commit
    • Andrés G. Aragoneses's avatar
      build: default to build just one media backend · af010792
      Andrés G. Aragoneses authored
      Unless explicitly required by the user at configure time, the build
      should default to only enable one media backend, not two at the same
      Banshee can run with more than one media backend, but this feature is
      mainly intended for the use case of having two backends with different
      capabilities. However, in this case we're talking about selecting the
      managed or the unmanaged backend, and both (should) have the same
      Before this patch, the user had to explicitly enable the managed
      backend and disable the native one if she wanted to run the managed
      one without loading the native one. This is now corrected: if the
      user doesn't supply any option, only the native backend is built,
      and if the user supplies the --enable-gst-sharp option, only the
      managed one is built.
  12. 19 Nov, 2013 1 commit
  13. 04 Nov, 2013 1 commit
    • Bertrand Lorentz's avatar
      build: Use notify-sharp-3.0 when present on the system · b81720da
      Bertrand Lorentz authored
      Now that notify-sharp has a 3.0 release that depends on GTK 3, we can
      use it and revert back to the same behavior we had in the GTK 2 world:
      use the appropriate system-installed notify-sharp if present, and if
      not, use our own internal copy.
      This removes the --with-system-notify-sharp configure option, which
      nobody should have been using anyway.
  14. 01 Nov, 2013 1 commit
    • Bertrand Lorentz's avatar
      build: Rework build configuration for GStreamer backends · 0d79eeeb
      Bertrand Lorentz authored
      Using a PLAYBACK_BACKEND variable in SUBDIRS is incorrect, as it
      always causes one of the backends to be omitted from the source tarball,
      thus breaking "make distcheck".
      The two GStreamer backends can now be built conditionnaly, with the
      appropriate --enable-gst-sharp and/or --disable-gst-native configure
      By default, only the native backend is built, as was the case before.
      You can choose to build both backends, or none if you want Banshee to be
      very silent...
      An indication whether the native backend will be built is added to the
      configure output, for clarity.
  15. 19 Oct, 2013 3 commits
    • Bertrand Lorentz's avatar
      Remove last remaining mentions of MeeGo · 98802325
      Bertrand Lorentz authored
    • Bertrand Lorentz's avatar
      Rename the MeeGo extension to MediaPanel and drop MeeGo integration · dc783f66
      Bertrand Lorentz authored
      Rename everything from MeeGo to MediaPanel, with the appropriate
      adjustments. All the MeeGo integration is also removed, so we can build
      this extension by default. But the extension is not active by default.
      The general idea for the MediaPanel extension is to provide a simple UI
      to quickly browse and play your media. A bit like the MiniMode, but
      less minimal. It is not specifically targetted  for netbooks, but it
      will probably be more interesting for smaller screens, and maybe touch
      devices ?
    • Andrés G. Aragoneses's avatar
      Backends: drop the Banshee.NowPlaying.X11 extension · e0269ed3
      Andrés G. Aragoneses authored
      This extension was causing a bug when using the Fullscreen
      functionality at video playback. It may have been useful
      in the old gtk2 days, but today fullscreen works well without
      it (tested with Ubuntu and Gnome3).
      This also gets us closer to the goal of having 0% unmanaged
      code in banshee.
  16. 16 Oct, 2013 3 commits
  17. 15 Oct, 2013 1 commit
    • Andrés G. Aragoneses's avatar
      configure: move GTK backend detection from libbanshee to bnpx11 macro · 663c4714
      Andrés G. Aragoneses authored
      The variables HAVE_X11, HAVE_QUARTZ, GRAPHIC_SUBSYSTEM_X11 and
      GRAPHICS_SUBSYSTEM_QUARTZ were not being used. The one which was
      being used (in the config summary) but not filled with any value,
      There was already some GTK backend detection in bnpx11 m4 macro so
      we move from libbanshee to this just the only bits needed to fill
      the value GRAPHICS_SUBSYSTEM, also because libbanshee will be soon
      just optional.
  18. 10 Oct, 2013 1 commit
  19. 08 Oct, 2013 1 commit
    • Andrés G. Aragoneses's avatar
      build: refactoring to remove dupe $DLL_MAP_VERIFIER_ASSEMBLY target · 8ec0bc42
      Andrés G. Aragoneses authored
      After the fix for bgo#691696 landed, the target $DLL_MAP_VERIFIER_ASSEMBLY
      is defined in two places. This commits avoids this, by making the Makefile
      from the build/ dir include the generic build.rules.mk like other Makefiles
      in the build already do.
      The only change in this commit that seems to not be related is the move of
      the 'if ENABLE_TESTS' block. The reason for it was to avoid this build
      failure which would happen if it's not moved:
        Running automake --gnu --add-missing --force --copy -Wno-portability -Wno-portability ...
        build/build.rules.mk:11: LINK must be set with `=' before using `+='
      No change of behaviour in this commit.
  20. 07 Oct, 2013 1 commit
  21. 22 Sep, 2013 1 commit
  22. 09 Sep, 2013 1 commit
  23. 10 Jul, 2013 2 commits
  24. 10 Jun, 2013 1 commit
  25. 21 Apr, 2013 3 commits
  26. 20 Apr, 2013 3 commits
  27. 07 Apr, 2013 1 commit
    • Hans Petter Jansson's avatar
      Avoid race when using GConf and DBus with threads (bgo#692374) · f9b90f3e
      Hans Petter Jansson authored
      GConf causes us to make indirect calls to libdbus from multiple threads,
      resulting in crashes if threads are not initialized explictly. As a
      workaround, we initialize dbus-glib for multithreading.
      This fixes adds an optional build-time dependency on dbus-glib, and will
      only be enabled if that dependency is satisfied.
      Some distros have addressed this issue by patching the underlying
      llibraries (gconf or gconf-sharp), so they don't have to enable that
      fix. But it should not conflict with those patches, as
      dbus_g_thread_init can be called multiple time, contrary to what the
      API documentation says.
      Signed-off-by: Bertrand Lorentz's avatarBertrand Lorentz <bertrand.lorentz@gmail.com>
  28. 01 Apr, 2013 1 commit