Announcement

Collapse
No announcement yet.

SDL2 On Linux Now Prefers Wayland Over X11

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SDL2 On Linux Now Prefers Wayland Over X11

    Phoronix: SDL2 On Linux Now Prefers Wayland Over X11

    With today's SDL2 Git, Wayland is now preferred over X.Org/X11 by default without having to set the SDL video driver environment variable...

    https://www.phoronix.com/scan.php?pa...refers-Wayland

  • #2
    Hmmm... Dear ImGui doesn't work well on Wayland yet...

    Comment


    • #3
      Hopefully they'll Pipewire over Pulse for their audio next.

      Comment


      • #4
        Man, Im excited lets see what other wayland goodies we get this month

        Comment


        • #5
          I put libdecor and SDL in a ppa:

          https://launchpad.net/~ernstp/+archive/ubuntu/wayland

          For a Steam game you can set

          SDL_DYNAMIC_API=/usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 %command%

          to override SDL.

          Comment


          • #6
            Originally posted by Myownfriend View Post
            Hopefully they'll Pipewire over Pulse for their audio next.
            https://gitlab.freedesktop.org/pipew.../-/issues/1835

            Comment


            • #7
              Yeah, while most of Valve games (like L4D2 or TF2) don't work natively under Wayland, even through SDL_DYNÀMIC_API, and Valve isn't going to update those de facto abandoned titles.

              Comment


              • #8
                Originally posted by StarterX4 View Post
                Yeah, while most of Valve games (like L4D2 or TF2) don't work natively under Wayland, even through SDL_DYNÀMIC_API, and Valve isn't going to update those de facto abandoned titles.
                maybe they will support it in half-life 3 ?

                Comment


                • #9
                  Originally posted by Myownfriend View Post
                  Hopefully they'll Pipewire over Pulse for their audio next.
                  What benefit would it bring to the user? (Genuine question.) I guess if the old interface works just fine and is going to be well-supported in pipewire anyway, there is no point in writing a new audio backend.

                  Comment


                  • #10
                    Originally posted by er888kh View Post

                    What benefit would it bring to the user? (Genuine question.) I guess if the old interface works just fine and is going to be well-supported in pipewire anyway, there is no point in writing a new audio backend.
                    SDL2 already supports using Pipewire as an audio backend, it's just doesn't default to it if PW is available. By using the native backend it allows the application to use Pipewire without having to go through pipewire-pulse and it's always nice to avoid campatability layers when you can.

                    Comment

                    Working...
                    X