Home
last modified time | relevance | path

Searched +full:python +full:- +full:yaml (Results 1 – 12 of 12) sorted by relevance

/src/contrib/libcbor/
H A D.readthedocs.yaml1 # .readthedocs.yaml
3 # See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
8 # Set the version of Python and other tools you might need
10 os: ubuntu-22.04
12 python: "3.11"
18 # https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
19 python:
21 - requirements: doc/source/requirements.txt
/src/sys/contrib/device-tree/Bindings/
H A DMakefile1 # SPDX-License-Identifier: GPL-2.0
2 DT_DOC_CHECKER ?= dt-doc-validate
3 DT_EXTRACT_EX ?= dt-extract-example
4 DT_MK_SCHEMA ?= dt-mk-schema
7 echo "warning: python package 'yamllint' not installed, skipping" >&2)
15 echo "Ensure dtschema python package is installed and in your PATH." >&2; \
19 $(DT_DOC_CHECKER) --version 2>/dev/null || echo 0; } | sort -Vc >/dev/null || \
25 $(obj)/%.example.dts: $(src)/%.yaml check_dtschema_version FORCE
28 find_all_cmd = find $(src) \( -name '*.yaml' ! \
29 -name 'processed-schema*' \)
[all …]
H A Dwriting-schema.rst1 .. SPDX-License-Identifier: GPL-2.0
3 Writing Devicetree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it
11 Also see :ref:`example-schema`.
14 ---------------
16 Each schema doc is a structured json-schema which is defined by a set of
17 top-level properties. Generally, there is one binding defined per file. The
18 top-level json-schema properties used are:
21 A json-schema unique identifier string. The string must be a valid
[all …]
/src/contrib/libyaml/
H A DReadMe.md1 ## LibYAML - A C library for parsing and emitting YAML.
11 - gcc
12 - libtool
13 - make
24 - autoconf
25 - libtool
26 - make
29 homepage](https://github.com/yaml/libyaml).
33 You may also use the [YAML-Core mailing
34 list](http://lists.sourceforge.net/lists/listinfo/yaml-core).
[all …]
H A DChanges1 0.2.5 2020-06-01
3 https://github.com/yaml/libyaml/pull/105
6 https://github.com/yaml/libyaml/pull/186
9 https://github.com/yaml/libyaml/pull/185
12 https://github.com/yaml/libyaml/pull/187
13 Add -h and --flow (on|off|keep) to run-*-test-suite
15 https://github.com/yaml/libyaml/pull/182
18 https://github.com/yaml/libyaml/pull/177
21 https://github.com/yaml/libyaml/pull/181
22 Output error position in run-parser-test-suite.c
[all …]
/src/contrib/elftoolchain/
H A D.cirrus.yml3 image: freebsd-11-2-release-amd64
4 install_script: pkg install -y git py27-yaml
6 - fetch http://tetworks.opengroup.org/downloads/38/software/Sources/3.8/tet3.8-src.tar.gz
7 - tar -x -C test/tet -f tet3.8-src.tar.gz
8 - make
14 - apt-get update
15 - apt-get install -y
17 libarchive-dev libbsd-dev libc6-dev libexpat1-dev lsb-release
18 m4 perl python-yaml sharutils zlib1g-dev
20 - curl -O http://tetworks.opengroup.org/downloads/38/software/Sources/3.8/tet3.8-src.tar.gz
[all …]
/src/contrib/googletest/
H A D.gitignore4 cmake-build-debug/
6 bazel-bin
7 bazel-genfiles
8 bazel-googletest
9 bazel-out
10 bazel-testlogs
12 # python
23 Win32-Debug/
24 Win32-Release/
25 x64-Debug/
[all …]
/src/contrib/llvm-project/
H A DFREEBSD-Xlist2 .clang-format
3 .clang-tidy
4 .git-blame-ignore-revs
15 clang/.clang-format
16 clang/.clang-tidy
38 clang/include/clang/Format/.clang-format
68 clang/lib/Format/.clang-format
102 clang/tools/amdgpu-arch/
103 clang/tools/apinotes-test/
104 clang/tools/arcmt-test/
[all …]
/src/contrib/libyaml/src/
H A Dscanner.c6 * The following notes assume that you are familiar with the YAML specification
7 * (http://yaml.org/spec/cvs/current.html). We mostly follow it, although in
10 * The process of transforming a YAML stream into a sequence of events is
18 * is a straightforward implementation of a recursive-descendant parser (or,
30 * STREAM-START(encoding) # The stream start.
31 * STREAM-END # The stream end.
32 * VERSION-DIRECTIVE(major,minor) # The '%YAML' directive.
33 * TAG-DIRECTIVE(handle,prefix) # The '%TAG' directive.
34 * DOCUMENT-START # '---'
35 * DOCUMENT-END # '...'
[all …]
/src/contrib/bc/project/
H A Dgithub_issues.json10 …I'm getting the incorrect result from a simple calculation...\n\n80 - (30 * 0) / 50 - (80 / 100) *…
12 "closedAt": "2025-02-25T19:10:08Z",
20 …-only math.\n\nApplying integer-only math to the expression you gave, we get:\n\n```\n80 - (30 * 0…
21 "createdAt": "2025-02-25T19:10:08Z",
33 "url": "https://github.com/gavinhoward/bc/issues/87#issuecomment-2683017820",
42 "body": "Thanks, i solved the problem with '-l' to 'bc'\n\ne.g:\necho '1 + 1' | bc -l",
43 "createdAt": "2025-02-26T00:44:54Z",
48 "url": "https://github.com/gavinhoward/bc/issues/87#issuecomment-2683611929",
52 "createdAt": "2025-02-25T17:57:06Z",
64 "updatedAt": "2025-02-26T00:44:54Z",
[all …]
/src/tools/build/mk/
H A DOptionalObsoleteFiles.inc4 # the check-old* and delete-old* targets.
18 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-sav.in
19 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-sav.out
20 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-u.out
21 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-usr.in
22 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-usr.out
23 OLD_FILES+=usr/tests/usr.sbin/sa/v1-i386-sav.in
24 OLD_FILES+=usr/tests/usr.sbin/sa/v1-i386-sav.out
25 OLD_FILES+=usr/tests/usr.sbin/sa/v1-i386-u.out
26 OLD_FILES+=usr/tests/usr.sbin/sa/v1-i386-usr.in
[all …]
/src/
H A DObsoleteFiles.inc9 # delete-old-libs target, whereas OLD_FILES and OLD_DIRS are removed by the
10 # delete-old target. This separation allows users to avoid deleting old
18 # For files listed in OLD_FILES, OLD_LIBS, and MOVED_LIBS, the check-old*
19 # and delete-old* targets will also delete associated debug symbols from
34 # ( grep '+=' /usr/src/ObsoleteFiles.inc | sort -u ; \
35 # grep '+=' /usr/src/tools/build/mk/OptionalObsoleteFiles.inc | sort -u) | \
36 # sort | uniq -d
40 # for t in `make -V TARGETS universe`; do
41 # __MAKE_CONF=/dev/null make -f Makefile.inc1 TARGET=$t \
42 # -V OLD_FILES -V OLD_LIBS -V MOVED_LIBS -V OLD_DIRS check-old | \
[all …]