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...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

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

    Comment


    • #3
      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


      • #4
        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


        • #5
          menuconfig FTW

          Comment


          • #6
            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


            • #7
              Originally posted by atomsymbol

              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


              • #8
                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


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

                  Comment


                  • #10
                    Originally posted by atomsymbol

                    Is there some data about the relative market share of all these "make config" variants?
                    I know what you mean... I know it's a common backend, but it's insane how much effort goes into having multiple GUI options for something as low-level as configuring the kernel build. You'd think anyone who did kernel development or built kernels from source would prefer to just have something simple and command-line... something that didn't require having a graphical desktop installed, much less running. That's why I always favoured 'menuconfig' back in my LinuxFromScratch days.

                    Comment

                    Working...
                    X