patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity
zephyr/scripts/requirements-extras.txt

17 lines
361 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-07 21:58:00 +01:00
# EXTRAS: optional or useful for development/developers workflow
# used by sanitycheck for --test-tree option
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-08 23:45:44 +02: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-07 21:58:00 +01:00
# used by scripts/gen_cfb_font_header.py - helper script for user
Pillow
Reference in a new issue Copy permalink