Searched +full:python +full:- +full:yaml (Results 1 – 9 of 9) sorted by relevance
1 # SPDX-License-Identifier: GPL-2.02 DT_DOC_CHECKER ?= dt-doc-validate3 DT_EXTRACT_EX ?= dt-extract-example4 DT_MK_SCHEMA ?= dt-mk-schema7 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 FORCE28 find_all_cmd = find $(src) \( -name '*.yaml' ! \29 -name 'processed-schema*' \)[all …]
1 .. SPDX-License-Identifier: GPL-2.03 Writing Devicetree Bindings in json-schema6 Devicetree bindings are written using json-schema vocabulary. Schema files are7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it11 Also see :ref:`example-schema`.14 ---------------16 Each schema doc is a structured json-schema which is defined by a set of17 top-level properties. Generally, there is one binding defined per file. The18 top-level json-schema properties used are:21 A json-schema unique identifier string. The string must be a valid[all …]
1 ## LibYAML - A C library for parsing and emitting YAML.11 - gcc12 - libtool13 - make24 - autoconf25 - libtool26 - make29 homepage](https://github.com/yaml/libyaml).33 You may also use the [YAML-Core mailing34 list](http://lists.sourceforge.net/lists/listinfo/yaml-core).[all …]
1 0.2.5 2020-06-013 https://github.com/yaml/libyaml/pull/1056 https://github.com/yaml/libyaml/pull/1869 https://github.com/yaml/libyaml/pull/18512 https://github.com/yaml/libyaml/pull/18713 Add -h and --flow (on|off|keep) to run-*-test-suite15 https://github.com/yaml/libyaml/pull/18218 https://github.com/yaml/libyaml/pull/17721 https://github.com/yaml/libyaml/pull/18122 Output error position in run-parser-test-suite.c[all …]
3 image: freebsd-11-2-release-amd644 install_script: pkg install -y git py27-yaml6 - fetch http://tetworks.opengroup.org/downloads/38/software/Sources/3.8/tet3.8-src.tar.gz7 - tar -x -C test/tet -f tet3.8-src.tar.gz8 - make14 - apt-get update15 - apt-get install -y17 libarchive-dev libbsd-dev libc6-dev libexpat1-dev lsb-release18 m4 perl python-yaml sharutils zlib1g-dev20 - curl -O http://tetworks.opengroup.org/downloads/38/software/Sources/3.8/tet3.8-src.tar.gz[all …]
4 cmake-build-debug/6 bazel-bin7 bazel-genfiles8 bazel-googletest9 bazel-out10 bazel-testlogs11 # python22 Win32-Debug/23 Win32-Release/24 x64-Debug/[all …]
2 .clang-format3 .clang-tidy4 .git-blame-ignore-revs15 clang/.clang-format16 clang/.clang-tidy38 clang/include/clang/Format/.clang-format68 clang/lib/Format/.clang-format102 clang/tools/amdgpu-arch/103 clang/tools/apinotes-test/104 clang/tools/arcmt-test/[all …]
6 * The following notes assume that you are familiar with the YAML specification7 * (http://yaml.org/spec/cvs/current.html). We mostly follow it, although in10 * The process of transforming a YAML stream into a sequence of events is18 * 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 …]
4 # the check-old* and delete-old* targets.18 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-sav.in19 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-sav.out20 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-u.out21 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-usr.in22 OLD_FILES+=usr/tests/usr.sbin/sa/v1-amd64-usr.out23 OLD_FILES+=usr/tests/usr.sbin/sa/v1-i386-sav.in24 OLD_FILES+=usr/tests/usr.sbin/sa/v1-i386-sav.out25 OLD_FILES+=usr/tests/usr.sbin/sa/v1-i386-u.out26 OLD_FILES+=usr/tests/usr.sbin/sa/v1-i386-usr.in[all …]