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

26 lines
597 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
scripts: footprint: Add converter to twister_footprint.json Add new script `pack_as_twister.py` to convert memory footprint data prepared by `./footprint/scripts/track.py` into JSON files compatible with Twister report schema. Next, the data can be transformed and uploaded to ElasticSearch data storage the same way as memory footprint (and other) reports executed by Twister. Add to `plan.txt` an optional column with the corresponding test suite names for 'footprints' as an example for test instance name composing with `--test-name` command argumnent. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2024-08-30 09:48:04 +02:00
# to use in ./scripts for memory footprint, code coverage, etc.
scripts: make sure we do not install vulunerable python packages Make sure we install packages with no issues, some of the issues being reporting on packages we might install using pip: Warn: Project is vulnerable to: PYSEC-2019-41 / GHSA-qfc5-mcwq-26q8 Warn: Project is vulnerable to: PYSEC-2014-14 / GHSA-652x-xj99-gmcc Warn: Project is vulnerable to: GHSA-9wx4-h78v-vm56 Warn: Project is vulnerable to: PYSEC-2014-13 / GHSA-cfj3-7x9c-4p3h Warn: Project is vulnerable to: PYSEC-2018-28 / GHSA-x84v-xcm2-53pg Warn: Project is vulnerable to: PYSEC-2017-74 Warn: Project is vulnerable to: GHSA-55x5-fj6c-h6m8 Warn: Project is vulnerable to: PYSEC-2014-9 / GHSA-57qw-cc2g-pv5p Warn: Project is vulnerable to: PYSEC-2021-19 / GHSA-jq4v-f5q6-mjqq Warn: Project is vulnerable to: GHSA-pgww-xf46-h92r Warn: Project is vulnerable to: PYSEC-2022-230 / GHSA-wrxv-2j5q-m38w Warn: Project is vulnerable to: PYSEC-2018-12 / GHSA-xp26-p53h-6h2p Warn: Project is vulnerable to: PYSEC-2024-4 / GHSA-2mqj-m65w-jghx Warn: Project is vulnerable to: PYSEC-2023-165 / GHSA-cwvm-v4w8-q58c Warn: Project is vulnerable to: PYSEC-2022-42992 / GHSA-hcpj-qp55-gfph Warn: Project is vulnerable to: PYSEC-2023-137 / GHSA-pr76-5cm5-w9cj Warn: Project is vulnerable to: PYSEC-2023-161 / GHSA-wfm5-v35h-vwf4 Warn: Project is vulnerable to: GHSA-3f63-hfp8-52jq Warn: Project is vulnerable to: GHSA-44wm-f244-xhp3 Warn: Project is vulnerable to: GHSA-56pw-mpj4-fxww Warn: Project is vulnerable to: GHSA-j7hp-h8jx-5ppr Warn: Project is vulnerable to: PYSEC-2023-175 Warn: Project is vulnerable to: PYSEC-2018-34 / GHSA-2fc2-6r4j-p65h Warn: Project is vulnerable to: PYSEC-2021-856 / GHSA-5545-2q6w-2gh6 Warn: Project is vulnerable to: PYSEC-2019-108 / GHSA-9fq2-x9r6-wfmf Warn: Project is vulnerable to: PYSEC-2018-33 / GHSA-cw6w-4rcx-xphc Warn: Project is vulnerable to: PYSEC-2021-857 / GHSA-f7c7-j99h-c22f Warn: Project is vulnerable to: GHSA-fpfv-jqm9-f5jm Warn: Project is vulnerable to: PYSEC-2017-1 / GHSA-frgw-fgh6-9g52 Warn: Project is vulnerable to: GHSA-c6fm-rgw4-8q73 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2025-03-22 12:13:34 -04:00
gitpython>=3.1.41
scripts: footprint: Add converter to twister_footprint.json Add new script `pack_as_twister.py` to convert memory footprint data prepared by `./footprint/scripts/track.py` into JSON files compatible with Twister report schema. Next, the data can be transformed and uploaded to ElasticSearch data storage the same way as memory footprint (and other) reports executed by Twister. Add to `plan.txt` an optional column with the corresponding test suite names for 'footprints' as an example for test instance name composing with `--test-name` command argumnent. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2024-08-30 09:48:04 +02:00
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
# helper for developers - check git commit messages
gitlint
# helper for developers
junit2html
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: make sure we do not install vulunerable python packages Make sure we install packages with no issues, some of the issues being reporting on packages we might install using pip: Warn: Project is vulnerable to: PYSEC-2019-41 / GHSA-qfc5-mcwq-26q8 Warn: Project is vulnerable to: PYSEC-2014-14 / GHSA-652x-xj99-gmcc Warn: Project is vulnerable to: GHSA-9wx4-h78v-vm56 Warn: Project is vulnerable to: PYSEC-2014-13 / GHSA-cfj3-7x9c-4p3h Warn: Project is vulnerable to: PYSEC-2018-28 / GHSA-x84v-xcm2-53pg Warn: Project is vulnerable to: PYSEC-2017-74 Warn: Project is vulnerable to: GHSA-55x5-fj6c-h6m8 Warn: Project is vulnerable to: PYSEC-2014-9 / GHSA-57qw-cc2g-pv5p Warn: Project is vulnerable to: PYSEC-2021-19 / GHSA-jq4v-f5q6-mjqq Warn: Project is vulnerable to: GHSA-pgww-xf46-h92r Warn: Project is vulnerable to: PYSEC-2022-230 / GHSA-wrxv-2j5q-m38w Warn: Project is vulnerable to: PYSEC-2018-12 / GHSA-xp26-p53h-6h2p Warn: Project is vulnerable to: PYSEC-2024-4 / GHSA-2mqj-m65w-jghx Warn: Project is vulnerable to: PYSEC-2023-165 / GHSA-cwvm-v4w8-q58c Warn: Project is vulnerable to: PYSEC-2022-42992 / GHSA-hcpj-qp55-gfph Warn: Project is vulnerable to: PYSEC-2023-137 / GHSA-pr76-5cm5-w9cj Warn: Project is vulnerable to: PYSEC-2023-161 / GHSA-wfm5-v35h-vwf4 Warn: Project is vulnerable to: GHSA-3f63-hfp8-52jq Warn: Project is vulnerable to: GHSA-44wm-f244-xhp3 Warn: Project is vulnerable to: GHSA-56pw-mpj4-fxww Warn: Project is vulnerable to: GHSA-j7hp-h8jx-5ppr Warn: Project is vulnerable to: PYSEC-2023-175 Warn: Project is vulnerable to: PYSEC-2018-34 / GHSA-2fc2-6r4j-p65h Warn: Project is vulnerable to: PYSEC-2021-856 / GHSA-5545-2q6w-2gh6 Warn: Project is vulnerable to: PYSEC-2019-108 / GHSA-9fq2-x9r6-wfmf Warn: Project is vulnerable to: PYSEC-2018-33 / GHSA-cw6w-4rcx-xphc Warn: Project is vulnerable to: PYSEC-2021-857 / GHSA-f7c7-j99h-c22f Warn: Project is vulnerable to: GHSA-fpfv-jqm9-f5jm Warn: Project is vulnerable to: PYSEC-2017-1 / GHSA-frgw-fgh6-9g52 Warn: Project is vulnerable to: GHSA-c6fm-rgw4-8q73 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2025-03-22 12:13:34 -04:00
Pillow>=10.3.0
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
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
Copy permalink