mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-02 19:47:04 +00:00
a457681b1c
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>
20 lines
364 B
Plaintext
20 lines
364 B
Plaintext
# BUILD-TEST: required to do build tests of zephyr
|
|
#
|
|
# things used by sanitycheck or other things like code coverage or python
|
|
# testing
|
|
|
|
# used by sanitycheck for ansi color
|
|
colorama
|
|
|
|
# python lex/yex used by sanitycheck
|
|
ply>=3.10
|
|
|
|
# optional, but used for validation of YAML
|
|
pykwalify
|
|
|
|
# used for code coverage
|
|
gcovr>=4.2
|
|
|
|
# used for west-command testing
|
|
pytest
|