Announcement

Collapse
No announcement yet.

The Qt Company Decides To Deprecate The Qbs Build System, Will Focus On CMake & QMake

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

  • The Qt Company Decides To Deprecate The Qbs Build System, Will Focus On CMake & QMake

    Phoronix: The Qt Company Decides To Deprecate The Qbs Build System, Will Focus On CMake & QMake

    While Qt's Qbs build system was once planned as the default build system for Qt6 and shaping up to be the de facto successor to QMake, there is a change of course with The Qt Company now announcing they are deprecating this custom build system...

    http://www.phoronix.com/scan.php?pag...Future-Not-Qbs

  • #2
    Good decision

    Comment


    • #3
      Originally posted by cen1 View Post
      Good decision
      Indeed. QMake is ideal for simple Qt-projects and CMake is ideal for complex projects. There is no need for Qbs.

      Comment


      • #4
        But, but, .... freedom of choice! A'la Devuan. We need maintenance hell and duplication of all efforts, coz that what the FLOSS zealots thrive on!!

        Comment


        • #5
          Surprised they didn't jump on the Meson bandwagon, it's multi-platform like CMake. Maybe Python3 was too big a dependency?

          Comment


          • #6
            Originally posted by FireBurn View Post
            Surprised they didn't jump on the Meson bandwagon, it's multi-platform like CMake. Maybe Python3 was too big a dependency?
            Does Meson allow reusable scripts/plugins now? When I tried you had to push everything in the upstream project vs creating some re-usable CMake scripts for say ARM Cortex development.
            Its not really usable in that regard, unless upstream caters for your needs.

            No good support in IDEs or package managers like conan either.

            Comment


            • #7
              Originally posted by FireBurn View Post
              Surprised they didn't jump on the Meson bandwagon, it's multi-platform like CMake. Maybe Python3 was too big a dependency?
              so many things depend on python tho.

              Comment


              • #8
                Originally posted by tzui View Post

                Indeed. QMake is ideal for simple Qt-projects and CMake is ideal for complex projects. There is no need for Qbs.
                I've always said that if your project has needs not covered by a million other projects out there, you should be looking at your project (and its setup) first.
                When build tools developed on the shoulders of decades' worth of knowledge don't do what you need (or aren't easily patched to do it), you're probably doing something wrong.

                Comment


                • #9
                  Originally posted by cj.wijtmans View Post

                  so many things depend on python tho.
                  That's a moronically stupid reason to do something that stupid.

                  Comment


                  • #10
                    Originally posted by cj.wijtmans View Post

                    so many things depend on python tho.
                    And Qt already has python build dependencies. The real problem was that meson just didn't cut it when it was looked at, and that CMake is the de-facto standard among Qt users.

                    Comment

                    Working...
                    X