eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

228
active users

#buildsystem

0 posts0 participants0 posts today
Replied in thread

@kkremitzki

In Fedora/RHEL land, there is mock which takes a .src.rpm file and creates a chroot or container on-the-fly with the target distro version and installs all the needed dependencies to do a clean build. The output (built .rpm packages) is then saved before the build environment is torn down.

I would expect this framework to be capable of creating a VM instance as an alternative, to have even greater separation between the main host and the builder image.

Mock is the main build component in the whole Fedora Koji and Copr stacks, and a very similar infrastructure is to build the the RHEL packages as well.

Announcing the new script-based build system

We began exploring options to improve the build system for all our projects that was first established around 2021, starting from the Nitrocid KS project. We had initialized the Nitrocid PPA packaging in 2020, then improved it quite a bit in 2021 with a new repository, which is archived now as part of our efforts in 2023 to make use of the Makefiles.

Since then, we’ve started increasing the consistency of our build system to the point that the Makefiles and the relevant build scripts have been introduced, with the latest changes being that we’ve finally introduced the tools submodule. This repository allows you to give your projects a build system powered by both the Batch scripts for Windows and the Bash scripts for Unix systems.

This repository is still not finished, yet, as we are trying to address remaining improvements to be put in place and to introduce a more extensive (and hopefully clear) documentation for using this submodule across many projects. Many Aptivi projects will use it to improve their build system and to save time writing long commands.

Using a single make command provided by an extensible standard Makefile template file (can be copied to each project individually) that will debut this August, we’ll be able to make this build system available to the public for every external project to use. For .NET projects, this Makefile will not interfere with the standard Visual Studio build process. As a reminder, Makefiles are not only for native projects written in C, but are also for all projects under all programming languages, even .NET and Node.js!

This build system is currently under development, but we are excited to announce that the final release of this build system will be released in the first half of August.

Build System Refinement

We are currently in the process of refining the build system so that developers can build our projects more efficiently than before. The build scripts will be updated so that they reflect what we plan to do to them, such as being able to be run from any working directory for complex build procedures.

This will save time for both the developers and for those who plan to contribute to our projects. The update to the build scripts will be rolled out gradually as we evaluate choices to make sure that those scripts meet our quality requirements. The development branches of Nitrocid and Terminaux are the testing grounds to develop the updated build scripts.

The GitHub workflows will also be updated to more accurately verify our work by introducing dry running to all the scripts. This way, we’d be able to deploy the release more efficiently without having to create errata releases for just one minor build issue. For example, Nitrocid 0.1.2.1 had to be released after we’d discovered that the NuGet packages for 0.1.2.0 were missing due to a failing step related to the Discord webhook.

We’ll apply the appropriate changes based on the impact, and we’ll make sure that the developer experience of contributing to our projects will be much better. Much, much better than before.

Photo by ThisisEngineering on Unsplash

Apple öffnet Swift Build für die Entwickler-Community
Apple hat einen weiteren Schritt in Richtung Open Source unternommen: Swift Build, die zentrale Build-Engine für Swift-Projekte, steht ab sofort als Open-Source-Software zur Verfügung. Damit erhalten
apfeltalk.de/magazin/news/appl
#News #Services #Apple #BuildSystem #Linux #llbuild #OpenSource #Softwareentwicklung #Swift #SwiftBuild #SwiftPackageManager #Windows #Xcode