mirror of
https://github.com/morgan9e/systemd
synced 2026-04-14 08:25:20 +09:00
a527f70a41
The rule is changed from "put in basic unless there's a reason not to" to "put in shared unless there's a reason not to", to match the change done in previous commit. This minimizes libbasic. See previous commit for the reasons why this is useful. Previously, the guideline was based on whether the files in question use "publicly exported APIs". This distinction is not particularly relevant. Let's consider all other programs we compile: most of them use "publicly exported APIs", usually linking to libsystemd-shared.so for the actual code. But those programs are not forced to be in src/basic, and the distinction whether they happen to use 'sd-*.h' or not is of no importance. The same is true for files in src/shared/. If we didn't have publicly exported shared objects, we'd put everything in libsystemd-shared.so. So let's only move things out of it that we need to. Previous guideline was not "wrong", in the sense that it created *a* split that was functional (no code in src/shared was required in the publicly exported shared objects), but it put more files in basic/ then necessary. Not much changes in practice, because (as previous commit shows), moving files between libbasic.a and libsystemd-shared.so mostly just changes compilation order. The list of components which cannot use libsystemd-shared.so is adjusted.
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.