1. 27 Oct, 2020 9 commits
  2. 26 Oct, 2020 2 commits
  3. 21 Oct, 2020 2 commits
  4. 19 Oct, 2020 2 commits
  5. 16 Oct, 2020 3 commits
  6. 01 Oct, 2020 1 commit
  7. 30 Sep, 2020 2 commits
  8. 16 Sep, 2020 11 commits
  9. 15 Sep, 2020 1 commit
    • Manuel Stoeckl's avatar
      compositor: avoid setting WAYLAND_DISPLAY=wayland-0 · ae69381b
      Manuel Stoeckl authored
      This commit alters the way that Weston picks a Wayland display socket
      name. Instead of using wl_display_add_socket_auto to look for the first
      available name in wayland-0, wayland-1, .... to wayland-32, the code now
      checks names wayland-1, wayland-2, .... up to wayland-32.
      
      This change is a workaround for a suboptimal behavior of
      libwayland-client. If a client program calls wl_display_connect(NULL) and
      the WAYLAND_DISPLAY environment variable is not set, then the program will
      by default try to connect to 'wayland-0'. This is a problem when a
      computer has a running Wayland compositor but is being accessed in some
      other fashion, such as through an X session on a different virtual
      terminal, over ssh, etc. Client programs launched through those means may
      attempt to connect to an unrelated compositor. Changing libwayland
      behavior to remove the default would also work, but a) libraries have
      stronger backward compatibility expectations b) that would likely break
      more people's setups than just changing Weston would.
      Signed-off-by: default avatarManuel Stoeckl <code@mstoeckl.com>
      ae69381b
  10. 09 Sep, 2020 1 commit
    • Denys Dmytriyenko's avatar
      tests: include fcntl.h for open(), O_RDWR, O_CLOEXEC and O_CREAT · b10c0e84
      Denys Dmytriyenko authored
      musl libc (unlike glibc) requires explicitly incuding fcntl.h to define open(),
      O_RDWR, O_CLOEXEC and O_CREAT. Otherwise the build fails with the errors:
      
      | ../weston-9.0.0/tests/weston-test-fixture-compositor.c: In function 'wait_for_lock':
      | ../weston-9.0.0/tests/weston-test-fixture-compositor.c:135:7: warning: implicit declaration of function 'open'; did you mean 'popen'? [-Wimplicit-function-declaration]
      |   135 |  fd = open(lock_path, O_RDWR | O_CLOEXEC | O_CREAT, 00700);
      |       |       ^~~~
      |       |       popen
      | ../weston-9.0.0/tests/weston-test-fixture-compositor.c:135:23: error: 'O_RDWR' undeclared (first use in this function)
      |   135 |  fd = open(lock_path, O_RDWR | O_CLOEXEC | O_CREAT, 00700);
      |       |                       ^~~~~~
      | ../weston-9.0.0/tests/weston-test-fixture-compositor.c:135:23: note: each undeclared identifier is reported only once for each function it appears in
      | ../weston-9.0.0/tests/weston-test-fixture-compositor.c:135:32: error: 'O_CLOEXEC' undeclared (first use in this function)
      |   135 |  fd = open(lock_path, O_RDWR | O_CLOEXEC | O_CREAT, 00700);
      |       |                                ^~~~~~~~~
      | ../weston-9.0.0/tests/weston-test-fixture-compositor.c:135:44: error: 'O_CREAT' undeclared (first use in this function)
      |   135 |  fd = open(lock_path, O_RDWR | O_CLOEXEC | O_CREAT, 00700);
      |       |                                            ^~~~~~~
      Signed-off-by: default avatarDenys Dmytriyenko <denys@ti.com>
      b10c0e84
  11. 08 Sep, 2020 1 commit
  12. 07 Sep, 2020 4 commits
  13. 05 Sep, 2020 1 commit
    • Igor Matheus Andrade Torrente's avatar
      tests: Add a way to write a Weston.ini inside the test · ad41a885
      Igor Matheus Andrade Torrente authored
      Currently doesn't exist a standard way to write a weston.ini inside a test.
      
      Here, two new functions `weston_ini_setup` and `cfgln` are introduced to
      help the test writer to write a weston.ini file and load it to the test.
      And `internal-screenshot-test` is converted to use the new method of write
      a weston.ini. This conversion serves as example and initial API test.
      
      The tester needs to call `weston_test_harness_execute_as_client` or
      `weston_test_harness_execute_as_plugin` in the same way as before.
      The `weston_ini_setup` will fill the setup->config_file with the
      correct path to the weston.ini file.
      
      The main design goal is to avoid pre-made or build-made weston.ini(s)
      and keep the test as self-contained as possible.
      
      Closes:#410Signed-off-by: default avatarIgor Matheus Andrade Torrente <igormtorrente@gmail.com>
      ad41a885