build2 Reviews and Details

Social recommendations and mentions

• C++ Papercuts

  As the name suggests, this wraps the whatever build system that the dependency is using rather than replacing it with Meson. Say if you depend on Boost and Qt, you will end up using both Boost Build and CMake in addition to Meson (most likely there will be a couple of more build systems if you are also building Boost's and Qt's own dependencies such as ICU). This has two major drawbacks: 1. The build in... - Source: Hacker News / almost 3 years ago

• Sharing Saturday #472

  Which reminds me that I could package libtcode for build2 as that's what I'm using for MEGASTRUCTURES. I already packaged ENTT and fmt before and it's available on the OSS repository so it might be quite easy to do if libtcod dont have too many dependencies. Source: about 3 years ago

• Sharing Saturday #469

  After build2 devs added a missing feature that was preventing me from correctly running the python scripts from godot-cpp that generates the C++ bindings (the build2 devs were actually hitting similar issues and I was lucky to reach it while they were working on a solution), I managed to complete a working version of the build2 package of godot-cpp. As a reminder, godot-cpp is the library you need to use that... Source: about 3 years ago

• Sharing Saturday #467

  The first step is to do some scaffolding to easily build my C++ model from Prototype 1 as a Godot Extension, which also implies building godot-cpp which can be done with Scons or CMake easily as their scripts are provided, but I actually want to use build2 which is what I like to use these days in my own projects in C++. I could build godot-cpp in CMake and then link to it using my project under build2 but I kind... Source: about 3 years ago

• CPP, C++ Pain Points from the results of the 2023 Annual C++ Developer Survey reviewed

  On the subject of the difficulties with setting up a CI pipeline, I want to give a shout-out to Build2, which is incredible in this regard. Source: over 3 years ago

• Current Issues with the Qt Project – From the Outside Looking In

  > Qt should create a vanilla c++ package and tooling manager like Rusts cargo for dependencies and tools (and make semantic versioning mandatory). [...] Make the tool open source with vanilla c++ (aka non Qt projects), only so it can become the de facto standard. Or just use one that is already working: https://build2.org (bonus point: also gets rid of CMake). There are even "Qt classic" packages for both Qt5 and... - Source: Hacker News / over 3 years ago

• Introducing Bld: A New Pure Java Build System

  People starting with gradle didn't expect it to become as complex as maven, it has to "fix" the same issues. Google invented bazel because they where annoyed by cMake like everyone. It became another monster, so other decided to try it anew: build2. That is just the order of things. Source: over 3 years ago

• Sharing Saturday #460

  Godot's GDExtension system got a bit more documentation so I browsed the docs and some code in the last few weeks. I can see how to set it up with my build system + package manager (build2 and I see how it works and the limitations etc. To me it looks good, the only thing I'm wondering is if there is any way to automate the build of the non-godot code from Godot, like having an extension that will execute some... Source: over 3 years ago

• Stop Comparing Rust to Old C++

  If it takes off, maybe build2. It's fairly usable now, though it doesn't have as many packages as I'd like. Source: over 3 years ago

• Fish (shell) porting to Rust from C++

  > Cmake is the de-facto option and is an ancient horrible mess that feels like a miracle if it works at all. What's left? There is build2[1], which tries to approximate Cargo's experience for C/C++ projects while providing more depth, especially in the build system (unfortunately the "build by convention" ship has sailed for C/C++ so there needs to be some flexibility). As some indication of the project's... - Source: Hacker News / over 3 years ago

• OSD600 Lab 10

  I originally planned to use build2, but I found it to be much more complex than I expected. There was plenty of documentation to read for build2. The main documentation was all about the setup process, but there were also documentation pages for building, testing, and package management. - Source: dev.to / over 3 years ago

• The Helios Microkernel: Written in Hare

  One tool (actually a build toolchain) that you may want to check then is build2: https://build2.org. - Source: Hacker News / about 4 years ago

• Xmake v2.6.4 released, Improve a lot of package management features

  There is also build2 which looks like it does the same as XMake. It does have an integrated CI system you can use for free but not that many packages compared to Vcpkg. Its configuration is in an ugly DSL and is imperative. Source: over 4 years ago

• On Building 30K Debian Packages

  Or you could try a package repository for one of the C/C++ package managers. For example, for build2[1] we currently have ~300 packages[2] which you can all build in a uniform way. [1] https://build2.org. - Source: Hacker News / over 4 years ago

• Finland's prisons are tough

  Build2: https://build2.org/ It's a package manager and build system all in one. Source: over 5 years ago

• Is Mingw dead?

  And if you are looking for a build system that allows you to use the standard clang driver (rather than the clang-cl wrapper), build2 does that. We build the entire package repository with Clang on Windows: https://cppget.org/?builds=&cf=windows_10-clang_*. Source: over 5 years ago