Announcement

Collapse
No announcement yet.

Kodi HTPC Software Drops Wayland Support

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

  • Kodi HTPC Software Drops Wayland Support

    Phoronix: Kodi HTPC Software Drops Wayland Support

    The Kodi HTPC software formerly known as XBMC is -- at least temporarily -- dropping their Wayland support...

    http://www.phoronix.com/scan.php?pag...ayland-For-Now

  • #2
    Probably moving this to a separate branch would have been a smarter move. It's easy to do it later on, but just the branch being there would have been like an invitation for someone to pick it up and bring it back into shape.

    On the other hand, I'm pretty sure once Wayland implementations mature enough (i.e. they replace X by default in a couple of high profile distros), Kodi will be running on top of Wayland as well. So this little stunt won't really matter.

    Comment


    • #3
      Why is Kodi removing Boost library usage?

      Comment


      • #4
        Originally posted by fakenmc View Post
        Why is Kodi removing Boost library usage?
        Because much of boost in now part of C++11. https://en.wikipedia.org/wiki/Boost_...B_libraries%29

        Comment


        • #5
          Kodi/XBMC have also been trying to reduce the amount of third-party libraries its core code it dependent on for a few years now. Boost libraries are just one, SDL (Simple DirectMedia Layer), GLEW, and CXImage are others that Kodi depended on heavily before but have since been either dropped or dependecy for Kodi's core funtionallity have been reduced.

          Kodi project have grown so large that it became very hard to maintain and keep stable when it depends so much on third-parties. In addition Kodi is currently also in the process of migrating many other dependencies into binary addons to be able to upgrade them outside the normal release cycle.

          Even so, Kodi still depends on a lot of third-party libraries; just see:

          https://raw.githubusercontent.com/xb...s/README.linux

          Many of these would do better as binary addons instead of being built with the Kodi core.

          Comment


          • #6
            Originally posted by bug77 View Post

            Because much of boost in now part of C++11. https://en.wikipedia.org/wiki/Boost_...B_libraries%29

            Thanks. What is the future of the Boost libraries then?
            Last edited by fakenmc; 02-02-2016, 11:30 AM.

            Comment


            • #7
              Originally posted by fakenmc View Post


              Thanks. What is the future of the Boost libraries then?
              Oh, there's more to Boost than what was included in C++11. I'm guessing what was included was the bulk of what Kodi was using so it was easy to migrate away. Plus, Boost can now start to implement features that will go into the next C++ standard.

              Comment


              • #8
                Originally posted by bug77 View Post
                On the other hand, I'm pretty sure once Wayland implementations mature enough (i.e. they replace X by default in a couple of high profile distros), Kodi will be running on top of Wayland as well. So this little stunt won't really matter.
                Calling it a "stunt" seems uncharitable. They've removed a bunch of code that's currently unmaintained, not widely used, and apparently in pretty bad shape. And it's also clear from the discussion thread that Kodi does have developers who are willing to take on the job of cleaning up the code and getting it back into the main branch - indeed, it sounds like he's already making pretty good progress. What more could you ask for?

                Comment


                • #9
                  Originally posted by fakenmc View Post


                  Thanks. What is the future of the Boost libraries then?
                  To be experimental new C++ libraries, like they have always been.

                  Comment

                  Working...
                  X