1. 17 Nov, 2015 1 commit
  2. 13 Nov, 2015 2 commits
  3. 12 Nov, 2015 1 commit
  4. 11 Nov, 2015 1 commit
  5. 06 Nov, 2015 2 commits
  6. 12 May, 2015 2 commits
  7. 24 Mar, 2015 2 commits
  8. 11 Mar, 2015 2 commits
  9. 04 Feb, 2015 3 commits
  10. 06 Nov, 2014 1 commit
  11. 25 Sep, 2014 1 commit
  12. 06 Jan, 2014 1 commit
  13. 23 Sep, 2013 1 commit
  14. 23 Aug, 2013 1 commit
  15. 28 Jun, 2013 1 commit
  16. 04 Jan, 2012 1 commit
    • Simon McVittie's avatar
      Revert all changes since a36d4918 · 5df8c3db
      Simon McVittie authored
      Someone seems to have merged part of master into 1.4. Again. Let's go
      back to the "last known good" point (the branch-point of some 1.4
      branches I had locally), then we can cherry-pick the changes that
      should have gone in.
  17. 28 Sep, 2011 1 commit
    • Simon McVittie's avatar
      Merge tests' cmake and autotools bus configuration · e9f0378b
      Simon McVittie authored
      In Unix, the tests listened on both debug-pipe (which is a socketpair,
      or a TCP emulation of socketpair on Windows) and a Unix socket.
      In the Windows port, the tests were hard-coded to listen on a particular
      port, which allowed the dispatch test to connect to that port, as long
      as no two tests ran simultaneously (which I don't think was ever guaranteed -
      make -j can violate this). That's valid out-of-process, and also
      fully-specified, so they only needed one <listen> directive, so the
      CMake input only had one.
      To make the tests work under CMake on Unix, there was a hack: the string
      substituted for the content of the <listen> directive contained
      </listen><listen> to get the other address in, which is pretty nasty.
      Instead of doing that, I've made both build systems, on both Unix and
      Windows, use both debug-pipe and a more normal transport (Unix or TCP).
      debug-pipe has a Windows implementation and it's used in
      dbus-spawn-win.c, so it'd better work. The use of debug-pipe is now
      hard-coded rather than being a configure parameter (there's no reason
      to vary it in different builds), and I used TEST_LISTEN as the name of the
      Unix/TCP address, because it's a "vague" address (no specific Unix path, no
      TCP port), that you can listen on but not connect to.
      This in turn means that we can merge the Autoconf .in and CMake .cmake
      files, similar to Bug #41033.
      You might wonder why I've kept debug-pipe. I did try to get rid of it, but
      it turns out that the tests in dispatch.c rely on
      dbus_connection_open_private() not blocking, and normal socket
      connections block on connect(). Until we fix that by adding an async
      version of dbus_connection_open_private(), it won't be safe to have a
      test like dispatch.c that "talks to itself", unless it uses a transport
      as trivial as debug-pipe in which neither end has to block on the other.
      Signed-off-by: default avatarSimon McVittie <simon.mcvittie@collabora.co.uk>
      Reviewed-by: Ralf Habacker's avatarRalf Habacker <ralf.habacker@freenet.de>
      Bug: https://bugs.freedesktop.org/show_bug.cgi?id=41222
  18. 05 Aug, 2011 1 commit
  19. 09 Jul, 2010 1 commit
  20. 03 May, 2010 1 commit
  21. 11 Apr, 2010 1 commit
    • Ralf Habacker's avatar
      Cmake support for cross plattform usable test files. · 0ed7d779
      Ralf Habacker authored
      Recent test configuration files contains 'unix:...'
      bus adresses which do not work on windows.
      For cross plattform usable test files the whole
      listen tag entry has to be set by the build system,
      which is available with a new build system variable
      named TEST_LISTEN.
      To have the client client side definition in sync,
      TEST_CONNECTION has been moved from c file into cmake
      build system.
  22. 27 Mar, 2010 1 commit
  23. 19 Mar, 2010 3 commits
  24. 20 Dec, 2009 1 commit
  25. 01 Dec, 2009 1 commit
  26. 30 Nov, 2009 1 commit
  27. 14 Jul, 2009 1 commit
  28. 10 Jul, 2009 1 commit
  29. 20 May, 2009 3 commits