michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/scripts/requirements-extras.txt

35 lines
824 B
Text
Raw Normal View History

scripts/requirements: Split & document requirement.txt Split up requirements.txt into several files so that CI tools can utilize/reference the specific requirements-<FOO>.txt they may need while keep things in sync with the development. This is to reduce both time and amount of work CI actions due to python package install. Create the following groupings: 1. BASE - needed to build or create zephyr images 2. BUILD-TEST - need to run compile/build tests 3. DOC - need to build the docs 4. RUN-TEST - need for runtime testing 5. EXTRAS - optional or useful for development/developers workflow Also tried to add a comment about what or why a given package is being pulled in for. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2020-02-07 14:58:00 -06:00
# EXTRAS: optional or useful for development/developers workflow
cleanup: rename sanitycheck references to twister Cleanup references to sanitycheck that should now be twister. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2021-01-13 12:08:34 -06:00
# used by twister for --test-tree option
scripts/requirements: Split & document requirement.txt Split up requirements.txt into several files so that CI tools can utilize/reference the specific requirements-<FOO>.txt they may need while keep things in sync with the development. This is to reduce both time and amount of work CI actions due to python package install. Create the following groupings: 1. BASE - needed to build or create zephyr images 2. BUILD-TEST - need to run compile/build tests 3. DOC - need to build the docs 4. RUN-TEST - need for runtime testing 5. EXTRAS - optional or useful for development/developers workflow Also tried to add a comment about what or why a given package is being pulled in for. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2020-02-07 14:58:00 -06:00
anytree
# helper for developers - check git commit messages
gitlint
# helper for developers
junit2html
scripts: requirements: extras: add clang-format Add clang-format to the requirements-extras.txt and require a version compatible with the configuration options present in the .clang-format file. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-06-27 21:55:28 +02:00
# helper for developers - code formatter
scripts: requirements: extras: Suitable clang-format version Even when BreakBeforeBraces is set to Linux, implying BraceWrapping for AfterEnum to be true, clang-format version 12 puts the opening brace of an enum declaration on a new line. [1] One possible workaround would be to change AllowShortEnumsOnASingleLine from false to true, but that would yield a different kind of unwanted formatting. clang-format version 13 and newer have this issue fixed, therefore bumping the minimal version. [1] https://github.com/llvm/llvm-project/issues/48983 Signed-off-by: Reto Schneider <reto.schneider@husqvarnagroup.com>
2022-07-23 01:28:47 +02:00
clang-format>=1.13x
scripts: requirements: extras: add clang-format Add clang-format to the requirements-extras.txt and require a version compatible with the configuration options present in the .clang-format file. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-06-27 21:55:28 +02:00
scripts/requirements: add lpc_checksum script On some NXP LPC MCUs (such as LPC11U6x), a valid firmware image must include a checksum in the 7th entry of the ARM Cortex-M0 exception vector table. This checksum is verified by the bootloader. The lpc_checksum.py python script allows to insert this checksum into the firmware images (BIN and HEX formats). Project page: https://github.com/basilfx/lpc_checksum Signed-off-by: Simon Guinot <simon.guinot@seagate.com>
2020-06-08 23:45:44 +02:00
# Script used to build firmware images for NXP LPC MCUs.
lpc_checksum
scripts: move gen_cfb_font_header.py to scripts/build Move scripts needed by the build system and not designed to be run individually or standalone into the build subfolder. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2022-07-11 10:59:14 -04:00
# used by scripts/build/gen_cfb_font_header.py - helper script for user
scripts/requirements: Split & document requirement.txt Split up requirements.txt into several files so that CI tools can utilize/reference the specific requirements-<FOO>.txt they may need while keep things in sync with the development. This is to reduce both time and amount of work CI actions due to python package install. Create the following groupings: 1. BASE - needed to build or create zephyr images 2. BUILD-TEST - need to run compile/build tests 3. DOC - need to build the docs 4. RUN-TEST - need for runtime testing 5. EXTRAS - optional or useful for development/developers workflow Also tried to add a comment about what or why a given package is being pulled in for. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2020-02-07 14:58:00 -06:00
Pillow
scripts: Add imgtool to requirements On Windows, west sign command fails when imgtool not installed via 'pip3 install' Signed-off-by: Eug Krashtan <eug.krashtan@gmail.com>
2020-11-06 13:36:57 +02:00
# can be used to sign a Zephyr application binary for consumption by a bootloader
scripts: requirements-extras: Request imgtool 1.9 for write-block-size > 8 On some targets (such as STM32U5) using write-block-size >8, imgtool should be called using option '--align 16/32' which is only available starting version 1.9. Update requirement for imgtool to make it available to such platforms. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2022-08-25 17:51:39 +02:00
imgtool>=1.9
modules: nanopb: introduce new module Add the nanopb library and generator tools as a module. Nanopb is a small code-size Protocol Buffers implementation in ansi C. It is especially suitable for use in microcontrollers, but fits any memory restricted system. Nanopb home: https://jpa.kapsi.fi/nanopb/ Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>
2021-03-10 13:34:57 +01:00
# used by nanopb module to generate sources from .proto files
scripts/requirements: Replace protobuf with grpcio-tools The nanopb module generates source files from .proto files, however the latest protobuf v4.21.0 python package breaks compatibility. Using grpcio-tools instead fixes this. Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be>
2022-06-23 09:09:24 +02:00
grpcio-tools
scripts: add script to extract top-ten bug-bashers This script allows us to programmatically query bug-bashers within a user-supplied time-window. For example, we held a "Bug Bash Week" August 1-7, 2021 (it was announced a week early though). The output of the script prints the "top ten" bug bashers in tab-separated columns in descending order. The first column is the number of bugs squashed and the second column is the github user id. Signed-off-by: Christopher Friedt <chrisfriedt@gmail.com>
2021-08-17 08:10:07 -04:00
# used by scripts/release/bug_bash.py for generating top ten bug squashers
PyGithub
scripts: gen_handles: output dependency graph Output the final dependency graph as a `.dot` file, which when rendered by graphviz can be easier to comprehend than the text descriptions. This output is optional in that it will not be generated if `graphviz` is not installed. Signed-off-by: Jordan Yates <jordan.yates@data61.csiro.au>
2022-07-10 13:46:17 +10:00
# used to generate devicetree dependency graphs
graphviz
scripts: requirements: extras: add zcbor Add ZCBOR to the requirements-extras.txt and require at least version 0.6.0 which is the current version of the ZCBOR C library. Signed-off-by: Veijo Pesonen <veijo.pesonen@nordicsemi.no>
2022-11-21 13:26:12 +02:00
# used to generate CBOR encoders and decoders, e.g. lwm2m_senml_cbor.
zcbor>=0.6.0
Copy permalink