Migrating to Cargo/Make for builds #2731
Replies: 1 comment 7 replies
-
Yesterday, I started working on the meson -> cargo migration for Arch Linux and CachyOS. Here is the result for the -git version https://github.com/sched-ext/scx-scheds-packaging-arch/blob/master/PKGBUILD Main observations:
-> build:
-> check
The build logs refer to the tagged version 1.0.15, not the -git version, and I saw them for the first time. Meson never displayed them.
The only visible drawback of cargo is the need to manually repackage configurations such as scx_loader in a .spec or PKGBUILD file, because there is no automation like meson. However, compared to the problems mentioned above, this is not a deal breaker for me. We can use a simple makefile to repackage it or do it manually when compiling. I performed the build with cargo (the tests concerned both the tagged version and the -git version) both classically on a “working system” and clean chroot (pkgctl build from Arch Linux). The above PKGBUILD worked in both cases. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently we present a Meson interface for builds/installation/some testing. We're migrating away from this towards a simpler Cargo/Make build system, and this will take place over the next several releases.
The plan is as follows:
-Dallow_deprecated_meson=true
is provided, forcing packagers to take action but not immediately blocking them.This discussion is the right place to complain about these changes :)
We're cutting a lot of features (deliberately) by moving away from Meson towards a build system that is simpler to maintain and has fewer knobs for upstream (reducing the matrix). This is deliberate. But we still need distributions to be able to package sched_ext. Let us know what's missing and we can work out the best way to support your needs.
Beta Was this translation helpful? Give feedback.
All reactions