# Build System Published articles for Build System. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Fixed release schedule scrapped (old schedule restored) DevFeed: [Fixed release schedule scrapped (old schedule restored)]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T16:33:13.815653Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [releases](), [audit](), [builds](), [ci](), [coreboot](), [Linux]() Tags: [article](), [audit](), [bios](), [build-system](), [canoeboot](), [ci](), [coreboot](), [free-software](), [libre](), [libreboot](), [linux](), [news](), [opensource](), [releases](), [uefi]() ### AI overview Libreboot has abandoned its fixed annual release schedule after skipping the June 2026 release and deciding to skip December 2026. The next release is expected sometime in 2027. The project is also considering automated build and release testing, potentially through CI and regular snapshot builds, while continuing an audit and simplification of its build system. ### Source excerpt Article: Fixed release schedule scrapped (old schedule restored) Web link: https://libreboot.org/news/resolutions.html ## Libreboot 20231021 released! DevFeed: [Libreboot 20231021 released!]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [Hardware](), [boot](), [configuration](), [x86]() Tags: [article](), [asus](), [bios](), [boot](), [build-system](), [canoeboot](), [configuration](), [coreboot](), [free-software](), [hardware](), [libre](), [libreboot](), [opensource](), [release](), [uefi](), [workstation](), [x86]() ### AI overview Libreboot 20231021 is presented as a new testing release of Libreboot, with build-system improvements and the re-addition of three ASUS boards: KFSN4-DRE, KCMA-D8, and KGPE-D16. The release provides boot firmware for supported x86 and ARM machines and includes coreboot-based firmware support for the listed boards. ### Source excerpt Article: Libreboot 20231021 released! Web link: https://libreboot.org/news/libreboot20231021.html ## Libreboot Build System Audit 6 DevFeed: [Libreboot Build System Audit 6]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [audit](), [POSIX](), [Shell](), [Code](), [releases]() Tags: [audit](), [bios](), [build-system](), [canoeboot](), [code](), [coreboot](), [free-software](), [libre](), [libreboot](), [opensource](), [release](), [return](), [shell](), [uefi]() ### AI overview This article reports on the sixth audit of Libreboot's lbmk build system. It describes code cleanup, bug fixes, feature changes, and a reduction from 1,482 to 1,109 lines of shell script, a 25% decrease, between the Libreboot 20240612 release and the 19 July 2024 revision. ### Source excerpt Article: Libreboot Build System Audit 6 Web link: https://libreboot.org/news/audit6.html ## What level of Software Freedom does Libreboot give me? DevFeed: [What level of Software Freedom does Libreboot give me?]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [Software](), [boot](), [releases](), [Documentation](), [make]() Tags: [amd](), [article](), [bios](), [build-system](), [canoeboot](), [coreboot](), [firmware](), [free-software](), [grub](), [guides](), [installation](), [intel](), [libre](), [libreboot](), [news](), [opensource](), [releases](), [software](), [uefi](), [version]() ### AI overview The article explains how Libreboot's software-freedom policy is implemented in practice, including the licensing status of its components. It also notes a recent release with fixes and updated component revisions, and outlines planned board additions and documentation improvements. ### Source excerpt Article: What level of Software Freedom does Libreboot give me? Web link: https://libreboot.org/news/freedom.html ## Libreboot 20220710 released! DevFeed: [Libreboot 20220710 released!]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [releases](), [coreboot](), [Linux]() Tags: [article](), [bios](), [build-system](), [canoeboot](), [coreboot](), [documentation](), [free-software](), [gcc](), [hardware](), [libre](), [libreboot](), [linux](), [opensource](), [release](), [releases](), [scripts](), [security](), [speed](), [testing](), [uefi](), [upgrade](), [usb](), [version]() ### AI overview Libreboot 20220710 is a stable bug-fix release relative to version 20211122. It adds documentation snapshots and fixes or improves GRUB boot performance, laptop compatibility, build behavior, USB keyboard support, coreboot configuration, and related tooling. No new boards or major features were added. ### Source excerpt Article: Libreboot 20220710 released! Web link: https://libreboot.org/news/libreboot20220710.html ## Libreboot 20210522 released! DevFeed: [Libreboot 20210522 released!]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [releases](), [coreboot](), [boot](), [x86](), [Linux]() Tags: [bios](), [boot](), [build-system](), [canoeboot](), [coreboot](), [firmware](), [free-software](), [libre](), [libreboot](), [linux](), [opensource](), [release](), [uefi](), [update](), [x86]() ### AI overview Libreboot 20210522 is a testing release of the free boot firmware, released on 22 May 2021. It focuses on build-system changes and updates to coreboot 4.14, with support and testing status varying across hardware platforms. ### Source excerpt Article: Libreboot 20210522 released! Web link: https://libreboot.org/news/libreboot20210522.html ## Libreboot Build System Audit 4 DevFeed: [Libreboot Build System Audit 4]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [audit](), [Shell](), [Code](), [coding style](), [Open Source]() Tags: [article](), [audit](), [bios](), [build](), [build-system](), [canoeboot](), [coding-style](), [complexity](), [coreboot](), [free-software](), [libre](), [libreboot](), [opensource](), [patches](), [uefi]() ### AI overview This article reviews the fourth audit of the Libreboot build system, lbmk, covering code cleanup, generalization, new features, and bug fixes. It reports a reduction from 1,744 to 1,618 shell-script SLOC and a corresponding 7.22% decrease in complexity, while functionality increased. ### Source excerpt Article: Libreboot Build System Audit 4 Web link: https://libreboot.org/news/audit4.html ## Libreboot build system audit plus next-release plans DevFeed: [Libreboot build system audit plus next-release plans]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [Shell](), [releases](), [C]() Tags: [audit](), [bios](), [build-system](), [c](), [canoeboot](), [coreboot](), [free-software](), [libre](), [libreboot](), [opensource](), [release](), [shell](), [testing](), [uefi]() ### AI overview Libreboot reports that more than 200 changes have been made to its lbmk automated build system since the previous release. The article describes an audit, extensive testing, cleanup, and ongoing work toward a future release. ### Source excerpt Article: Libreboot build system audit plus next-release plans Web link: https://libreboot.org/news/audit.html ## Libreboot Build System Audit 3 DevFeed: [Libreboot Build System Audit 3]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [audit](), [maintenance](), [Error Handling](), [Shell]() Tags: [audit](), [audits](), [bios](), [bug](), [build-system](), [canoeboot](), [complexity](), [coreboot](), [efficiency](), [error-handling](), [free-software](), [integrity](), [libre](), [libreboot](), [opensource](), [safety](), [threading](), [uefi]() ### AI overview This article reports on Libreboot Build System Audit 3, focusing on the lbmk build system. It describes improved error handling, bug fixes, efficiency improvements, reduced complexity, stronger vendor-file integrity checks, and broader use of multithreading. The audit reduced the build system from 2,644 to 1,744 shell-script source lines compared with the previous audit, without reducing functionality. ### Source excerpt Article: Libreboot Build System Audit 3 Web link: https://libreboot.org/news/audit3.html ## Babel in Khan Academy's i18n Toolchain DevFeed: [Babel in Khan Academy's i18n Toolchain]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-22T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Babel](), [Internationalization (i18n)](), [toolchain](), [es6](), [JavaScript](), [Parser](), [Universal Syntax Tree.](), [Open Source]() Tags: [api](), [architecture](), [babel](), [build](), [build-system](), [code](), [engineering](), [es6](), [eslint](), [frontend](), [javascript](), [news](), [plugin](), [source](), [structure](), [syntax](), [tests](), [toolchain](), [types](), [web-frontend](), [workflow]() ### AI overview Khan Academy describes switching its ES6 and JSX frontend compilation from jstransform to Babel. The article explains a custom Babel plugin for preserving the project's internationalization behavior and discusses matching generated output, line numbers, whitespace, and the existing build chain. ### Source excerpt By Kevin Barabash We've been using ES6 (along with JSX) for sometime at Khan Academy. Right now, we're ... Read more ## BeOS-Inspired Haiku Now Supports Changing Audio Outputs Live, Other Improvements DevFeed: [BeOS-Inspired Haiku Now Supports Changing Audio Outputs Live, Other Improvements]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-11T00:55:29Z Content type: news Language: en Sources: [Phoronix]() Topics: [Operating system](), [USB](), [cpu]() Tags: [2026](), [architectures](), [audio](), [build-system](), [cpu](), [desktop-linux](), [development](), [kernel](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [os](), [phoronix](), [phoronix-test-suite](), [power-management](), [release](), [report](), [ubuntu-benchmarks](), [ubuntu-hardware](), [update](), [usb]() ### AI overview Haiku's August 2026 development report describes live audio-output switching, automatic stopping of inactive outputs, continued Bluetooth and USB audio work, power-management improvements, CPU feature-detection updates, kernel fixes, build-system updates, and progress on PowerPC and ARM64 support. ### Source excerpt In addition to August bringing the long-awaited Haiku R1 Beta 6 release, there was also a lot of development progress on this BeOS-inspired operating system too during the course of the past month... ## VoIP, VPN, and the Build System Behind Them DevFeed: [VoIP, VPN, and the Build System Behind Them]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-04T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Virtual Private Network](), [cross-platform](), [API](), [iOS](), [Android](), [Java](), [Framework](), [Extension]() Tags: [android](), [apis](), [build](), [build-system](), [extension](), [integration](), [java](), [native](), [packages](), [platform](), [signing](), [vpn]() ### AI overview Codename One adds native call-management and VPN APIs for iOS and Android. Its builders generate the required platform services, frameworks, permissions, delegates, and separately signed extension targets based on the Java packages an application uses. ### Source excerpt Codename One adds native call management and VPN APIs, while its builders generate the platform services, frameworks, permissions, and extension plumbing only when an application uses them. ## ESP-IDF: Propagating compiler flags to ExternalProject builds DevFeed: [ESP-IDF: Propagating compiler flags to ExternalProject builds]() Original publisher: [Read original article]() Author: John Lee Published: 2026-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [CMake](), [Compiler]() Tags: [blog](), [build](), [build-system](), [cmake](), [compiler](), [compiler-flags](), [esp-idf]() ### AI overview This ESP-IDF post explains why compiler options driven by Kconfig and components do not automatically propagate to ExternalProject_Add() builds. It describes using response files tied to the appropriate build context to keep compiler flags aligned between the outer and nested CMake projects. ### Source excerpt When an ESP-IDF project uses ExternalProject_Add(), compiler options driven by Kconfig and components do not flow into the nested build on their own. This post walks through why that happens and how to keep the outer and inner CMake worlds aligned. ## Squashing Docker images with Buildx DevFeed: [Squashing Docker images with Buildx]() Original publisher: [Read original article]() Author: Tom Published: 2025-12-24T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [docker images](), [Dockerfile](), [Caching]() Tags: [best-practices](), [build](), [build-system](), [caching](), [devops](), [docker](), [docker-buildx](), [docker-image-optimization](), [docker-images](), [docker-layer-management](), [dockerfile-best-practices](), [linux](), [squash-docker-image]() ### AI overview This tutorial explains how to create smaller Docker images with Buildx by rebuilding the final filesystem state into a new image, removing intermediate layers. It also discusses the trade-off: this approach can prevent reuse of base-image layer caching, while selectively copying files follows a builder-pattern alternative. ### Source excerpt Learn how to squash Docker images using Buildx to create smaller, more efficient images by consolidating layers. ## Manage multiple ESP-IDF build configurations with ease DevFeed: [Manage multiple ESP-IDF build configurations with ease]() Original publisher: [Read original article]() Author: John Lee Published: 2025-12-05T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [configuration](), [CMake](), [Command-line interface](), [Testing]() Tags: [blog](), [build-system](), [cmake](), [command-line](), [configuration](), [esp-idf](), [how-to](), [sdkconfig]() ### AI overview This tutorial explains how ESP-IDF v6.0 build configuration presets simplify switching among development, production, and testing builds. It covers reusable JSON-based settings, CMake Presets support, and separate build directories for parallel configuration management. ### Source excerpt Tired of juggling complex command-line arguments with endless idf.py flags? ESP-IDF v6.0 introduces a new feature, letting you switch between multiple build configuration. Learn how to structure your project, isolate sdkconfig files, and migrate from ad-hoc commands to clean, declarative builds. ## Porting a library to an ESP-IDF component DevFeed: [Porting a library to an ESP-IDF component]() Original publisher: [Read original article]() Author: John Lee Published: 2025-10-20T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Library](), [Testing](), [ide](), [Code](), [Hardware](), [Template](), [GitHub]() Tags: [app](), [blog](), [build](), [build-system](), [code](), [component](), [esp-idf](), [esp-idf-component](), [esp-idf-extension-for-vs-code](), [esp32-c3](), [esp32c3](), [github](), [hardware](), [how-to](), [porting](), [repo](), [testing]() ### AI overview This tutorial explains how to port an external library into a reusable ESP-IDF component. Using tinyexpr, it covers obtaining the source code, creating a test project and component, configuring the build system, resolving compatibility issues, and testing on an ESP32-C3 board. ### Source excerpt This article shows how to port an external library into an ESP-IDF project by converting it into a reusable component. Using tinyexpr as an example, it covers obtaining the source code, creating a new project, building a component, configuring the build system, and testing on hardware. ## Gradle Best Practices - A Path to Build Happiness DevFeed: [Gradle Best Practices - A Path to Build Happiness]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2025-05-01T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Google](), [Tooling]() Tags: [best-practices](), [build-system](), [developer](), [gradle](), [jetbrains]() ### AI overview Gradle, Google, and JetBrains formed a working group to define best practices for structuring and configuring Gradle builds. The initiative responds to developer difficulties caused by Gradle's flexibility, including build instability, suboptimal solutions, and maintenance challenges. ### Source excerpt Gradle Build Tool, also known as Gradle, is a highly flexible and extensible build system. It supports multiple ways to structure and configure builds, making it incredibly powerful--but also somewhat daunting, especially for teams just getting started. Even experienced developers and tooling providers sometimes struggle with Gradle's complexity. We've heard this loud and clear from the community and also in our recent Developer Survey. Whether it's setting up a build from scratch, improving performance, or avoiding pitfalls, teams often find themselves searching for clear guidance on the best way to do things. That's why we partnered with JetBrains and Google to create the Gradle Best Practices guide--an essential resource to help teams build with confidence and settle debates over the proper way to use Gradle. How This Initiative Started This effort began during a Gradle, Google, and JetBrains Summit in Fall 2024, where teams from each company meet annually to align on product roadmaps and discuss the future of the ecosystem. These summits have been pivotal in shaping major initiatives--Declarative Gradle emerged from one of these discussions, and Kotlin itself has been deeply influenced by them. At the 2024 Summit, a key question emerged: Beyond new features, how can we improve the Gradle experience today? The answer was clear: we need to establish best practices. While it's easy to focus on exciting new Gradle features, existing build setups often lack clear guidance. The Gradle teams at Google, JetBrains, and Gradle recognized that developers frequently struggle with too many ways to do the same thing--leading to suboptimal solutions, build instability, and maintenance headaches. This realization led to the formation of a dedicated working group, with representatives from all three companies. Over the past months, we've been meeting weekly to define best practices that provide firm foundations and help teams avoid future problems. Why Best Practices Matter Gradle's ## Sphinx + Bazel: the good, the bad, and the ugly DevFeed: [Sphinx + Bazel: the good, the bad, and the ugly]() Original publisher: [Read original article]() Published: 2025-03-25T00:00:00Z Content type: opinion Language: en Sources: [technicalwriting.dev]() Topics: [bazel](), [Documentation](), [Software Engineering](), [Development]() Tags: [bazel](), [build-system](), [documentation](), [shell-script](), [software-engineering](), [sphinx]() ### AI overview An experienced technical writer discusses the strengths and weaknesses of managing Sphinx documentation projects with Bazel. The article explains how Bazel can orchestrate Sphinx workflows and describes reported maintenance and development-environment benefits, while helping readers decide whether it fits their project. ### Source excerpt Strengths and weaknesses of orchestrating Sphinx projects with Bazel. ## Orchestrate Sphinx projects with Bazel DevFeed: [Orchestrate Sphinx projects with Bazel]() Original publisher: [Read original article]() Published: 2025-03-25T00:00:00Z Content type: tutorial Language: en Sources: [technicalwriting.dev]() Topics: [bazel](), [Tutorial](), [Documentation](), [GitHub](), [GitHub Pages](), [Bash](), [Linux](), [Extension](), [Template]() Tags: [bash](), [bazel](), [build-system](), [docs](), [extension](), [github](), [github-pages](), [linux](), [repository](), [sphinx](), [tutorial]() ### AI overview An end-to-end tutorial on managing a Sphinx project with Bazel, including setup, documentation builds, local preview, extensions, and deployment to GitHub Pages. ### Source excerpt An end-to-end tutorial on managing a Sphinx project with Bazel. ## How we accidentally built a better build system for OCaml DevFeed: [How we accidentally built a better build system for OCaml]() Original publisher: [Read original article]() Author: Andrey Mokhov Published: 2025-01-24T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [OCaml](), [toolchain](), [Compiler](), [cross-platform]() Tags: [build-system](), [compiler](), [ocaml](), [open-source](), [portable](), [speed]() ### AI overview Jane Street describes how dissatisfaction with OMake led to Jenga, then to the simpler cross-platform Jbuilder tool. Although Jbuilder was initially intended as a compatibility shim, its speed, portability, and hackability made it popular and led to its evolution into Dune. ### Source excerpt A "build system" is one of the most important tools in a developer's toolbox. Roughly, it figures out how to create runnable programs from a bunch of different source files by calling out to the compiler, setting up and executing test suites, and so on. Because you interact with it daily, above all it has to be fast - but it also has to be flexible. ## Agnostic Build System: Powertrain build DevFeed: [Agnostic Build System: Powertrain build]() Original publisher: [Read original article]() Author: Johannes Foufas Published: 2024-06-18T09:48:37Z Content type: release Language: en Sources: [Volvo Cars Engineering - Medium]() Topics: [Embedded Software Dev](), [Python](), [GitHub Actions](), [JSON](), [Testing]() Tags: [automotive](), [automotive-software](), [autosar](), [build-system](), [c-coding](), [continuous-integration](), [embedded](), [json](), [python](), [release](), [testing]() ### AI overview The article announces Volvo Cars' Powertrain Build project, a Python-based build system for automotive embedded software. It supports moving source code between POSIX-based and legacy embedded ECU targets, Software in the Loop testing, and continuous integration through Zuul. It also describes JSON-based project, base, and unit configuration files, unit tests, and HTML documentation. ### Source excerpt Powering Volvo Cars' Software Builds We are thrilled to announce the release of the Volvo Cars Powertrain Build project, now available on OpenDev! As a build system tailored for embedded software development using DSpace Target Link or Mathworks Embedded coder, this project is set to improve the way we as automotive embedded engineers handle our code bases. The idea is to make it easy to move between different targets, enable Software in the Loop (SIL) testing, and streamline our continuous integration (CI) processes. Powertrain build offers to efficiently move embedded source code between different embedded targets, both Posix based and old school embedded ECU's. This build system does what AUTOSAR never did, and is a tool that prepares us for the future of the car OS. Check out the article below to learn more about AUTOSAR: The reality of AUTOSAR and the way forward Our Powertrain Build project is designed to work harmoniously with the Zuul CI system. This ensures that all code changes are automatically tested and validated, providing continuous feedback to developers and maintaining the integrity of our codebase. What is it? The build system is written in Python for ease of use and flexibility, and these are the build options. py -3.10 pybuild.wrapper --build ABC_123 Projects are defined in .json using Project, base and Unit configs. The project config file contains project specific configuration settings and references to other configuration files. The base config file shares the same structure as the project config file and can be used for non project-specific configuration settings and default values, these could for instance be diagnostic core dummy file names. The units config file contains information about included software units and scheduling rasters. The software units are executed in the order they are defined within each time raster definition. { "SampleTimes": { "VcExt10ms": 0.01 }, "VcExt10ms": [ "VcDebug", "VcCarCfg", ] } Schedulers are not include ## Nonsensical Maven is still a Gradle problem DevFeed: [Nonsensical Maven is still a Gradle problem]() Original publisher: [Read original article]() Published: 2024-03-28T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Maven](), [Gradle]() Tags: [build-system](), [dependencies](), [dependency](), [jvm]() ### AI overview The article argues that Maven's default dependency resolution strategy is problematic for libraries built with Gradle. It explains dependency graphs and contrasts Gradle's default preference for newer versions with Maven's "nearest definition" rule, where declaration order can cause an older transitive dependency to win. ### Source excerpt There was a time when I used Maven heavily, but today all the libraries I work on build with Gradle. Even though I'm publishing with Gradle, consumers can use Gradle, Maven, Bazel, jars in libs/ (but please don't), or anything else. That's a huge JVM ecosystem win! In general, I don't have to think about what build system someone is using. I'm not here to debate subjective pros and cons of one versus any other. There is one notable exception, however. Maven's dependency resolution strategy is objectively bonkers. And if we want to support Maven consumers, we need to think about it. If you already are familiar with the concept of dependency resolution, you can skip to the nonsense. Dependency resolution primer Chances are your build system of choice (or a separate dependency resolver tool) gives you a declarative way to describe your dependencies. At build time, those declarations are resolved to .jars which can be put on the compiler classpath. Sometimes we call this a dependency tree, but it's actually a dependency graph, as separate nodes can converge back to something common to both. Project (build.gradle) ├── A │ └── B │ └── C v1.0 └── D └── C v1.0 If library B and library D agree on the version of library C, then that is the .jar version which is used. If they disagree on versions, some policy needs to decide the appropriate single version to use. Pop quiz: If library B wants version 1.1 of library C, and library D wants version 1.0 of library C, which single version of C should we use? Project (build.gradle) ├── A │ └── B │ └── C v1.1 └── D └── C v1.0 This is not a trick question. Hopefully the answer feels obvious: you use the newer version, 1.1. That version is probably compatible with 1.0, so it's safe for both library B and library D to use. We can't know for sure, to be clear, but it's a safe choice. This behavior is the default in many dependency resolvers, including the one inside Gradle. The nonsense When building with Maven, given two dependencies who ## Amper: a new way to configure Gradle projects? DevFeed: [Amper: a new way to configure Gradle projects?]() Original publisher: [Read original article]() Author: Gustavo Fão Valvassori Published: 2023-12-08T12:05:34Z Content type: tutorial Language: en Sources: [Touchlab]() Topics: [Gradle](), [Kotlin Multiplatform](), [configuration](), [YAML](), [IntelliJ IDEA](), [Groovy](), [Kotlin]() Tags: [build-system](), [coding](), [community](), [configuration](), [declarative](), [development](), [engineering](), [experimental](), [gradle](), [ide](), [inclusive](), [intellij-idea](), [kotlin-multiplatform](), [software](), [yaml]() ### AI overview The article introduces Amper, an experimental Gradle plugin for configuring Kotlin Multiplatform projects with YAML instead of Groovy or Kotlin configuration code. It explains the declarative approach, required IDE or plugin setup, module.yaml configuration, and changes to project structure. ### Source excerpt Earlier this month, Kotlin Multiplatform went stable. And just a couple of weeks later, they announced a new tool to help with one of the biggest issues we have, configuration. Currently, KMP projects use Gradle as a Build System, and we must agree that it's a great tool. But the complexity around it for new users is a big issue. Amper is a tool to help you configure your projects using a markup language. The main goal is to replace the Groovy/Kotlin programming language with something that can enforce a declarative approach. With a declarative paradigm, you can only declare what needs to be done without implementing it. If you already have experience with Maven, it may be familiar to you. Please note that the tool is in the early stages of development, and its goal is to validate the idea before putting more effort into it. With that in mind, be aware that syntax, language, and other things may change in the future, and it's a very experimental tool. How does it work? According to the docs, Amper is implemented as a Gradle plugin and uses YAML for its project configuration format. In other words, it's still a Gradle environment, but it will use an additional YAML file to configure the project. To be able to use it, you need one of the following environments: Use one of the following IDEs: IntelliJ IDEA 2023.3 or newer and the Amper Plugin; or Fleet 1.26 or newer; Use the Amper build plugin to enable it: In your settings.gradle.kts, add this plugin: id("org.jetbrains.amper.settings.plugin").version("0.1.1") When you open a project with the Amper Plugin in the IDE, it will look for the module.yaml file. This file will contain the configuration for the module (library or application), dependencies, and other project configurations (like the Java version). Also worth noting that it also changes the project architecture. Instead of having a directory for your source set artifacts, you will have multiple src directories. In other words, your commonMain/src/kotlin will be ## Amper: a new way to configure Gradle projects? - Gustavo Fão Valvassori DevFeed: [Amper: a new way to configure Gradle projects? - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2023-12-07T00:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [multiplatform](), [configuration](), [Gradle](), [jetbrains](), [YAML](), [IntelliJ IDEA]() Tags: [build-system](), [build-tools](), [configuration](), [declarative](), [gradle](), [jetbrains](), [kmp](), [kotlin](), [kotlin-multiplatform]() ### AI overview This article introduces Amper, an experimental JetBrains tool for configuring Kotlin Multiplatform projects through a declarative markup approach instead of Groovy or Kotlin build scripts. It remains within a Gradle environment while using an additional YAML file, and its syntax and capabilities may change. ### Source excerpt If you ask any KMP developer what's the biggest pain point on it, they will probably say "configuration". Amper is a new tool developed by JetBrains to help developers configure projects without all the complexity of Gradle. [Next page]()