zara/zephyr - zephyr - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Benjamin Cabé	be504b000d	west: spdx: allow to generate for different SPDX versions When support for SPDX 2.3 was added, it effectively dropped support for SPDX 2.2, which in retrospect was a bad idea since SPDX 2.2 is the version that is the current ISO/IEC standard. This commit adds a `--spdx-version` option to the `west spdx` command so that users can generate SPDX 2.2 documents if they want. Default is 2.3 given that's effectively what shipped for a few releases now, including latest LTS. Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>	4 weeks ago
Benjamin Cabé	4655e0d9d4	west: spdx: remove unnecessary format strings As reported by sonarqube, "String formatting should be used correctly" Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>	4 weeks ago
Pieter De Gendt	1378669736	scripts: west_command: spdx: Exit with non-zero code on failure If the init or the generation fails, the resulting exit code should be non-zero. Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>	6 months ago
Reto Schneider	743761d7d1	scripts: Fix CMake spelling As per its creators, CMake is written with a capital "M". The initial reason for this change is that I want Twister to print "ERROR : CMake build failure" instead of "ERROR : Cmake build failure". Signed-off-by: Reto Schneider <reto.schneider@husqvarnagroup.com>	8 months ago
Pieter De Gendt	46cc7a054d	scripts: west_commands: spdx: Remove deprecated west.log The global state west.log is deprecated, replace with WestCommand logging. Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>	9 months ago
Martí Bolívar	91f0212399	doc: add docs for west spdx These are based on the commit log in `fd31b9b4ac`. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>	4 years ago
Steve Winslow	fd31b9b4ac	west: spdx: Generate SPDX 2.2 tag-value documents This adds support to generate SPDX 2.2 tag-value documents via the new west spdx command. The CMake file-based APIs are leveraged to create relationships from source files to the corresponding generated build files. SPDX-License-Identifier comments in source files are scanned and filled into the SPDX documents. Before `west build` is run, a specific file must be created in the build directory so that the CMake API reply will run. This can be done by running: west spdx --init -d BUILD_DIR After `west build` is run, SPDX generation is then activated by calling `west spdx`; currently this requires passing the build directory as a parameter again: west spdx -d BUILD_DIR This will generate three SPDX documents in `BUILD_DIR/spdx/`: 1) `app.spdx`: This contains the bill-of-materials for the application source files used for the build. 2) `zephyr.spdx`: This contains the bill-of-materials for the specific Zephyr source code files that are used for the build. 3) `build.spdx`: This contains the bill-of-materials for the built output files. Each file in the bill-of-materials is scanned, so that its hashes (SHA256 and SHA1) can be recorded, along with any detected licenses if an `SPDX-License-Identifier` appears in the file. SPDX Relationships are created to indicate dependencies between CMake build targets; build targets that are linked together; and source files that are compiled to generate the built library files. `west spdx` can be called with optional parameters for further configuration: * `-n PREFIX`: specifies a prefix for the Document Namespaces that will be included in the generated SPDX documents. See SPDX spec 2.2 section 2.5 at https://spdx.github.io/spdx-spec/2-document-creation-information/. If -n is omitted, a default namespace will be generated according to the default format described in section 2.5 using a random UUID. * `-s SPDX_DIR`: specifies an alternate directory where the SPDX documents should be written. If not specified, they will be saved in `BUILD_DIR/spdx/`. * `--analyze-includes`: in addition to recording the compiled source code files (e.g. `.c`, `.S`) in the bills-of-materials, if this flag is specified, `west spdx` will attempt to determine the specific header files that are included for each `.c` file. This will take longer, as it performs a dry run using the C compiler for each `.c` file (using the same arguments that were passed to it for the actual build). * `--include-sdk`: if `--analyze-includes` is used, then adding `--include-sdk` will create a fourth SPDX document, `sdk.spdx`, which will list any header files included from the SDK. Signed-off-by: Steve Winslow <steve@swinslow.net>	4 years ago