mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-09 20:35:50 +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>
25 lines
546 B
Plaintext
25 lines
546 B
Plaintext
# BASE: required to build or create images with zephyr
|
|
#
|
|
# While technically west isn't required it's considered in base since it's
|
|
# part of the recommended workflow
|
|
|
|
# used by various build scripts
|
|
pyelftools>=0.24
|
|
|
|
# used by dts generation to parse binding YAMLs, also used by
|
|
# sanitycheck to parse YAMLs
|
|
PyYAML>=5.1
|
|
|
|
# used by west_commands
|
|
packaging
|
|
|
|
# intelhex used by mergehex.py
|
|
intelhex
|
|
|
|
# it's west
|
|
west>=0.6.2
|
|
|
|
# used for windows based 'menuconfig'
|
|
# "win32" is used for 64-bit Windows as well
|
|
windows-curses; sys_platform == "win32"
|