OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/scripts/requirements-extras.txt

23 lines
527 B
Plaintext
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-08 04:58:00 +08: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-14 02:08:34 +08: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-08 04:58:00 +08:00
anytree
# 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-09 05:45:44 +08:00
# Script used to build firmware images for NXP LPC MCUs.
lpc_checksum
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-08 04:58:00 +08:00
# used by scripts/gen_cfb_font_header.py - helper script for user
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 19:36:57 +08:00
# can be used to sign a Zephyr application binary for consumption by a bootloader
scripts/requirements: Add required version to imgtool in extras The minimal version of imgtool has been set at 1.7.1 Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
2020-12-19 04:56:38 +08:00
imgtool>=1.7.1
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 20:34:57 +08:00
# used by nanopb module to generate sources from .proto files
protobuf