21 matching pages, found in 53 ms

Ask StyxWritten on your GPU machine; takes a few seconds the first time.

  1. mkosi.systemd.iohttps://mkosi.systemd.io › building-rpms-from-source
    More about mkosi.systemd.io
    Building RPMs from source with mkosi

    … place from the upstream sources. Because --build-in-place configures _builddir to the current working directory, we change directory to the upstream sources before invoking rpmbuild . Again, _sourcedir has to point to …

    0 points
  2. systemd.iohttps://systemd.io › CODE_QUALITY
    More about systemd.io
    Code Quality Tools

    Code Quality Tools The systemd project has a number of code quality tools set up in the source tree and on the github infrastructure. Here’s an incomprehensive list of the available functionality …

    0 points
  3. systemd.iohttps://systemd.io › ARCHITECTURE
    More about systemd.io
    systemd Repository Architecture

    The systemd Repository Architecture Code Map This document provides a high-level overview of the various components of the systemd repository. Source Code Directories in src/ provide the implementation of all daemons …

    0 points
  4. mkosi.systemd.iohttps://mkosi.systemd.io › debugging
    More about mkosi.systemd.io
    Debugging failing sandboxed commands

    … returned non-zero exit code 1. ‣ [main] Sandbox command: mkosi-sandbox --bind … -- /usr/bin/some-command --some-option You need --debug-shell to pause the build inside the sandbox and keep the …

    0 points
  5. systemd.iohttps://systemd.io › TRANSLATORS
    More about systemd.io
    Notes for Translators

    … po/systemd.pot in the source tree. Then simply copy it to a new ${lang_code}.po file, where ${lang_code} is the two-letter code for a language (possibly followed by a …

    0 points
  6. systemd.iohttps://systemd.io › DISTRO_PORTING
    More about systemd.io
    Porting systemd To New Distributions

    … make changes to systemd’s source code to make it work on your distribution, unless your code is generic enough to be generally useful, we are unlikely to merge it. Please always consider …

    0 points
  7. systemd.iohttps://systemd.io › HACKING
    More about systemd.io
    Hacking on systemd

    … If adding a new source file, consider adding a matching test executable. For features at a higher level, tests in src/test/ are very strongly recommended. If that is not possible, integration …

    0 points
  8. systemd.iohttps://systemd.io › TESTING_WITH_SANITIZERS
    More about systemd.io
    Testing systemd Using Sanitizers

    Testing systemd Using Sanitizers To catch the nastier kind of bugs, you can run your code with Address Sanitizer and Undefined Behavior Sanitizer . This is mostly done automagically by various CI systems …

    0 points
  9. systemd.iohttps://systemd.io › OPTIMIZATIONS
    More about systemd.io
    systemd Optimizations

    … or reliability of our code, or that would make systemd harder to maintain. So in case you work on optimizations for systemd, try to keep your stuff mainlineable. If in doubt, ask …

    0 points
  10. systemd.iohttps://systemd.io › JOURNAL_EXPORT_FORMATS
    More about systemd.io
    Journal Export Formats

    … MESSAGE ^G^@^@^@^@^@^@^@foo bar CODE_FILE=<string> _PID=16853 _CMDLINE=python3 -c from systemd import journal; journal.send("foo\nbar") _SOURCE_REALTIME_TIMESTAMP=1423944916372858 Journal JSON Format Note that this section describes the …

    0 points

Search for “source code site:systemd.io” on Google, or add !ddg, !w and other shortcuts to any search.