Announcement

Collapse
No announcement yet.

Wayland Adds Meson Build System Support

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

  • Wayland Adds Meson Build System Support

    Phoronix: Wayland Adds Meson Build System Support

    While Wayland's Weston reference compositor has been using the Meson build system for about the past year, only this week did Wayland itself see Meson support introduced...

    http://www.phoronix.com/scan.php?pag...ds-Meson-Build

  • #2
    Makes a lot of sense. Meson is the only sane option.

    Comment


    • #3
      Originally posted by 144Hz View Post
      Makes a lot of sense. Meson is the only sane option.
      no, it's not. relying on bloated trash like python and ninja is no good.

      Comment


      • #4
        Originally posted by Redfoxmoon View Post

        no, it's not. relying on bloated trash like python and ninja is no good.
        So what would be a better option then?

        Comment


        • #5
          Originally posted by caligula View Post

          So what would be a better option then?
          inb4 this user suggests the custom set of bash scripts they have developed

          Comment


          • #6
            Originally posted by Redfoxmoon View Post

            no, it's not. relying on bloated trash like python and ninja is no good.
            but the "bloated trash" is faster than autotools, and surely that's not a bloated mess...

            Comment


            • #7
              Originally posted by boxie View Post

              but the "bloated trash" is faster than autotools, and surely that's not a bloated mess...
              And to top it off, Ninja is only a 4mb binary.

              Any build machine which cannot afford to spare that 4mb does not't deserve to be called a build machine. Even budget x64 computers have more than enough storage to house that measly 4mb for Ninja.

              Comment


              • #8
                Originally posted by Sonadow View Post

                And to top it off, Ninja is only a 4mb binary.

                Any build machine which cannot afford to spare that 4mb does not't deserve to be called a build machine. Even budget x64 computers have more than enough storage to house that measly 4mb for Ninja.
                oh man, you gotta watch what you're saying - that's how the bloat gets in! 4MB, why, in my day that was an entire operating system - AND WE LIKED IT :P

                (p.s. that was all sarcasm, in case any of it came across serious)

                Comment


                • #9
                  Originally posted by Sonadow View Post

                  And to top it off, Ninja is only a 4mb binary.

                  Any build machine which cannot afford to spare that 4mb does not't deserve to be called a build machine. Even budget x64 computers have more than enough storage to house that measly 4mb for Ninja.
                  To be fair, Ninja depends on Python which provides a non-trivial amount of runtime code. For example, on Arch Linux Python3 package is 152 MB in size.

                  Comment


                  • #10
                    Originally posted by caligula View Post

                    To be fair, Ninja depends on Python which provides a non-trivial amount of runtime code. For example, on Arch Linux Python3 package is 152 MB in size.
                    Python is already a near defacto requirement on a modern desktop Linux system since a number of tools and utilities depend on it. No distribution ships a desktop installation without Python already included as part of the base install.

                    Adding 4mb to an already large base install hardly counts as bloat.

                    Comment

                    Working...
                    X