Announcement

Collapse
No announcement yet.

Linux 5.11 Finally Flushes Out Its Qt4 Code For Configuring Kernel Builds UI

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

  • Linux 5.11 Finally Flushes Out Its Qt4 Code For Configuring Kernel Builds UI

    Phoronix: Linux 5.11 Finally Flushes Out Its Qt4 Code For Configuring Kernel Builds UI

    Linux 5.11's Kconfig build configuration updates are bringing some long overdue improvements to its "Qconf" Qt toolkit user interface option for configuring Linux kernel builds...

    http://www.phoronix.com/scan.php?pag...nfig-Drops-Qt4

  • #2
    Finally! Qt 4 is so obsolete by now...

    Comment


    • #3
      Originally posted by tildearrow View Post
      Finally! Qt 4 is so obsolete by now...
      Is there some data about the relative market share of all these "make config" variants?

      Comment


      • #4
        Correct mi if I am wrong but from my experience only the qt config version has a find option (under Ctrl + F)?
        That is why I always prefer the Qt version.

        Comment


        • #5
          What is this Qt support used for - configuring the Linux kernel for building from source? So does Linux ship with a copy of Qt and we actually use Qt to build the Linux kernel?

          Comment


          • #6
            menuconfig FTW

            Comment


            • #7
              Several options
              # make help
              Cleaning targets:
              clean - Remove most generated files but keep the config and
              enough build support to build external modules
              mrproper - Remove all generated files + config + various backup files
              distclean - mrproper + remove editor backup and patch files

              Configuration targets:
              config - Update current config utilising a line-oriented program
              nconfig - Update current config utilising a ncurses menu based program
              menuconfig - Update current config utilising a menu based program
              xconfig - Update current config utilising a Qt based front-end
              gconfig - Update current config utilising a GTK+ based front-end
              oldconfig - Update current config utilising a provided .config as base
              defconfig - New config with default from ARCH supplied defconfig
              ...

              Comment


              • #8
                Originally posted by atomsymbol View Post

                Is there some data about the relative market share of all these "make config" variants?
                Perhaps this?

                config 4%
                nconfig 1%
                menuconfig? 70%
                xconfig 5%
                gconfig 5%
                oldconfig 15%

                Comment


                • #9
                  Originally posted by dragonn View Post
                  Correct mi if I am wrong but from my experience only the qt config version has a find option (under Ctrl + F)?
                  That is why I always prefer the Qt version.
                  It's the / key (same as "search" for vim) for menuconfig, not sure if the behavior is entirely the same with the Qt version.

                  Comment


                  • #10
                    Heh. Last time I manually configured a kernel it was Qt3 bindings

                    Comment

                    Working...
                    X