Announcement

Collapse
No announcement yet.

FDBuild 0.1 Released To Make It Easier To Quickly Build Multiple Projects

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

  • FDBuild 0.1 Released To Make It Easier To Quickly Build Multiple Projects

    Phoronix: FDBuild 0.1 Released To Make It Easier To Quickly Build Multiple Projects

    Roman Gilg who is known for his work on the KWinFT compositor project has spent the past few years quietly developing FDBuild as a new tool for developers to easily pull, configure, and build multiple software projects via a single command. This week he released FDBuild 0.1 as the first public release of this handy utility...

    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
    What's the benefit over makepkg or cargo?

    Comment


    • #3
      Originally posted by geearf View Post
      What's the benefit over makepkg or cargo?
      or cmake?

      Comment


      • #4
        In comparison to cmake you can also build meson and autotools projects with fdbuild.

        Cargo is the Rust package manager, right? I assume with this one you can't build c or c++ projects, can you?

        I think makepkg is similar but FDBuild is simpler in setting up but you can still create folder trees with multiple projects.

        Depending on where you're in the tree all projects in this subtree are being built. In general FDBuild is more geared towards a fast developing workflow and not towards packaging.​​

        Comment


        • #5
          Its one layer above cargo/cmake etc...
          A long time ago, IDEs allowed having open multiple projects, and configuring build dependencies between them. All runtime dependencies were taken care of by the IDE setting runtime variables such as PATH/LD_LIBRARY_PATH and installing in a separate devel tree.
          Kdevelop still supports this masterfully.
          The setup was manual for every machine, that was a downside. And there was no automatic version control for dependencies.


          This is a replacement for that, when the most popular C++ IDE (CLion) very "helpfully" allows only one project per session, and has absolutely no concept of inter-project dependencies.

          If this project continues, it will end up implementing a basic package manager with only build capability.

          Comment


          • #6
            Originally posted by Serafean View Post
            the most popular C++ IDE (CLion) very "helpfully" allows only one project per session
            Works fine for me. Ctrl-Click the menu entry to open another project. Works the same for the whole suite.

            Comment


            • #7
              Looks a bit like a task runner. At least the example could be easily modeled with a taskfile.

              Comment


              • #8
                A meta-buildsystem-buildsystem! For more build in your buildsystems!

                Alternative suggestion: Make stupid buildsystems less stupid and make then build with `<buildsystem> build` or similar. Then, 'build x projects' is equivalent to a shell script with x lines simply calling the default build task on each directory. \o/

                (Still, cool project)

                Comment


                • #9
                  Originally posted by aksdb View Post
                  Looks a bit like a task runner. At least the example could be easily modeled with a taskfile.
                  Interesting project. It looks like a replacement of make files in a more modern syntax. I think a difference to FDBuild is that you would still need to formulate the different tasks per project with Task while with FDBuild you can simply use a template and plugin and you don't have to think about how the different build commands/tools work again.

                  Comment


                  • #10
                    Originally posted by Serafean View Post
                    Its one layer above cargo/cmake etc...
                    A long time ago, IDEs allowed having open multiple projects, and configuring build dependencies between them. All runtime dependencies were taken care of by the IDE setting runtime variables such as PATH/LD_LIBRARY_PATH and installing in a separate devel tree.
                    Kdevelop still supports this masterfully.
                    The setup was manual for every machine, that was a downside. And there was no automatic version control for dependencies.
                    Isn't that the whole point of Cargo, Conan and co, to manage dependencies and build? (Or a layer above makepkg.)

                    Comment

                    Working...
                    X