Searched refs:build (Results 1 – 25 of 64) sorted by relevance
123
| /systemd-251/tools/ |
| D | oss-fuzz.sh | 26 build="$WORK/build"
27 rm -rf "$build"
28 mkdir -p "$build"
72 if ! meson "$build" "-D$fuzzflag" -Db_lundef=false; then
73 cat "$build/meson-logs/meson-log.txt"
77 ninja -v -C "$build" fuzzers
100 df="$build/dns-fuzzing"
105 "$build"/src/shared/libsystemd-shared-*.so \
106 "$build"/src/core/libsystemd-core-*.so
110 find "$build" -maxdepth 1 -type f -executable -name "fuzz-*" -exec mv {} "$OUT" \;
|
| D | coverity.sh | 65 build Issue Coverity build
74 Applicable to build command
106 …COVERITY_UNSUPPORTED=1 cov-build --dir $RESULTS_DIR $_cov_build_options sh -c "$COVERITY_SCAN_BUIL…
161 build)
|
| D | find-build-dir.sh | 16 for i in "$root"/../*/build.ninja; do
|
| /systemd-251/.github/workflows/ |
| D | unit_tests.sh | 52 apt-get -y build-dep systemd
66 find . -type f -name meson.build -exec sed -i '/install_tag/d' '{}' '+'
68 …-group=nogroup --werror -Dtests=unsafe -Dslow-tests=true -Dfuzz-tests=true "${MESON_ARGS[@]}" build
69 ninja -C build -v
70 meson test -C build --print-errorlogs
90 find . -type f -name meson.build -exec sed -i '/install_tag/d' '{}' '+'
92 …obody-group=nogroup --werror -Dtests=unsafe -Db_sanitize=address,undefined "${MESON_ARGS[@]}" build
93 ninja -C build -v
108 meson test --timeout-multiplier=3 -C build --print-errorlogs
|
| D | build_test.sh | 105 apt-get -y build-dep systemd
130 find . -type f -name meson.build -exec sed -i '/install_tag/d' '{}' '+'
141 -Dcryptolib="${CRYPTOLIB:?}" $args build; then
143 cat build/meson-logs/meson-log.txt
147 if ! meson compile -C build -v; then
151 for loader in build/src/boot/efi/*.efi; do
|
| D | coverity.yml | 16 build:
35 - name: Install build dependencies
38 - name: Preconfigure the build directory
39 run: meson cov-build -Dman=false
41 run: tools/coverity.sh build
|
| D | cifuzz.yml | 14 - '**/meson.build'
36 id: build
54 if: failure() && steps.build.outcome == 'success'
|
| D | unit_tests.yml | 16 build:
34 - name: Install build dependencies
|
| D | build_test.yml | 9 - '**/meson.build'
19 build:
|
| D | mkosi.yml | 4 # Simple boot tests that build and boot the mkosi images generated by the mkosi config files in mko…
72 run: ./.github/workflows/run_mkosi.sh build
|
| /systemd-251/docs/ |
| D | HACKING.md | 31 run the relevant tool from the build directory.
35 a set of `mkosi` build files directly in the source tree.
37 from an upstream distribution in combination with a fresh build of the project
40 the [GitHub repository](https://github.com/systemd/mkosi). `mkosi` will build an
57 you can use mkosi's incremental mode (`-i`). This instructs mkosi to build a set
59 both instructs mkosi to build cached images if they don't exist yet and to use
63 If you're going to build mkosi images that use the same distribution and release
73 If you want to do a local build without mkosi, most distributions also provide
75 to build systemd:
81 $ sudo apt-get build-dep systemd
[all …]
|
| D | RELEASE.md | 11 2. Update the contributors list in NEWS (`ninja -C build git-contrib`)
13 4. Update hwdb (`ninja -C build update-hwdb`, `ninja -C build update-hwdb-autosuspend`, commit sepa…
14 5. Update syscall numbers (`ninja -C build update-syscall-tables update-syscall-header`).
15 6. [RC1] Update version and library numbers in `meson.build`
16 7. Check dbus docs with `ninja -C build update-dbus-docs`
18 9. Do `ninja -C build`
19 10. Make sure that the version string and package string match: `build/systemctl --version`
20 11. Upload the documentation: `ninja -C build doc-sync`
|
| D | CODE_QUALITY.md | 14 1. Use `meson test -C build` to run the unit tests. Some tests are skipped if
16 meson test -C build`. A couple of unit tests are considered "unsafe" (as
17 they change system state); to run those too, build with `meson setup
19 build them too with `meson setup -Dslow-tests=true`. (Note that there are a
21 change these flags for an already set up build tree, too, with "meson
22 configure -C build -D…".)
25 suite. This will build OS images with a number of integration tests and run
41 6. Use `ninja -C build check-api-docs` to compare the list of exported symbols
45 7. Use `ninja -C build update-hwdb` and `ninja -C build update-hwdb-autosuspend`
49 8. Use `ninja -C build update-man-rules` to update the meson rules for building
[all …]
|
| D | TRANSLATORS.md | 14 The build system (meson/ninja) can be used to generate a template (`*.pot`),
30 $ ninja -C build/ systemd-pot
54 $ ninja -C build/ systemd-update-po
78 $ ninja -C build/ systemd-gmo
81 The resulting files will be saved in the `build/po/` directory.
|
| D | COREDUMP_PACKAGE_METADATA.md | 15 ELF binaries get stamped with a unique, build-time generated hex string identifier called
16 `build-id`, [which gets embedded as an ELF note called `.note.gnu.build-id`](https://fedoraproject.…
22 However, this usage of the `build-id` requires either local metadata, usually set up by
26 Thus it becomes desirable to add additional metadata to a binary at build time, so that
40 build tools should strive to use the same names, for consistency. The most common will be
85 A reference implementations of a [build-time tool is provided](https://github.com/systemd/package-n…
86 and can be used to generate a linker script, which can then be used at build time via
132 INSERT AFTER .note.gnu.build-id;
|
| /systemd-251/test/ |
| D | README.testsuite | 8 $ ninja -C build # Avoid building anything as root later
10 ninja: Entering directory `/home/zbyszek/src/systemd/build'
31 Specifying the build directory
34 If the build directory is not detected automatically, it can be specified
37 $ sudo BUILD_DIR=some-other-build/ test/run-integration-tests
41 $ sudo make -C test/TEST-01-BASIC BUILD_DIR=../../some-other-build/ ...
50 of the systemd from a build, use the NO_BUILD=1:
184 Now install necessary build & test dependencies:
188 # apt build-dep -y systemd
234 This can occur if the specified build commands failed to compile or process any code.
[all …]
|
| D | mkosi.default.networkd-test | 58 ninja-build
81 BuildScript=mkosi.build.networkd-test
|
| /systemd-251/ |
| D | README | 206 python-lxml (optional, required to build the indices)
211 clang >= 10.0, llvm >= 10.0 (optional, required to build BPF programs
225 To build in directory build/:
226 meson setup build/ && ninja -C build/
229 to meson. After the build directory is initially configured, meson will
231 meson configure -Darg=value build/
236 ninja -C build -v some/target
237 meson test -C build/
238 sudo meson install -C build/ --no-rebuild
239 DESTDIR=... meson install -C build/
[all …]
|
| D | Makefile | 4 ninja -C build
7 DESTDIR=$(DESTDIR) ninja -C build install
|
| D | mkosi.build | 22 [ -z "$BUILDDIR" ] && BUILDDIR=build
47 if [ ! -f "$BUILDDIR"/build.ninja ] ; then
|
| D | README.md | 9 [](https:/…
27 Information about build requirements is provided in the [README file](README).
|
| D | configure | 24 exec meson build "${args[@]}"
|
| /systemd-251/mkosi.default.d/fedora/ |
| D | 10-mkosi.fedora | 4 # Symlink this file to mkosi.default in the project root directory and invoke "mkosi" to build an O…
24 ninja-build
|
| /systemd-251/mkosi.default.d/centos_epel/ |
| D | 10-mkosi.centos_epel | 4 # Symlink this file to mkosi.default in the project root directory and invoke "mkosi" to build an O…
27 ninja-build
|
| /systemd-251/man/ |
| D | meson.build | 223 command : [update_dbus_docs_py, '--build-dir', project_build_root, '@INPUT@'],
230 args : ['--build-dir', project_build_root, '--test', dbus_docs],
239 '@0@/rules/meson.build'.format(meson.current_source_dir())],
|
123