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

35 lines
693 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
# 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
scripts: Increased minimal pyelftools version Increased minimal pyelftools version to 0.26 else scripts/footprint/size_report will fail to import LocationExpr from elftools.dwarf.locationlists Signed-off-by: Jan Van Winkel <jan.van_winkel@dxplore.eu>
2020-07-22 21:43:41 +02:00
pyelftools>=0.26
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 dts generation to parse binding YAMLs, also used by
scripts: move pip pykwalify from requirements-build-test to -base ... because zephyr_module needs it. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2021-01-12 01:01:45 +01:00
# twister to parse YAMLs, by west, zephyr_module,...
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
PyYAML>=5.1
scripts: move pip pykwalify from requirements-build-test to -base ... because zephyr_module needs it. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2021-01-12 01:01:45 +01:00
# YAML validation. Used by zephyr_module.
pykwalify
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 west_commands
scripts: west: add CANopen flash runner Add west flash runner for program download via CANopen. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2020-03-08 21:48:48 +01:00
canopen
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
packaging
scripts: west: add CANopen flash runner Add west flash runner for program download via CANopen. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2020-03-08 21:48:48 +01:00
progress
ARC: west: mdb runner: record MDB's CLD process pid to file Record MDB's CLD process pid to file so this process can be terminated by sanitycheck infrastructure. Update mdb runners test to be able to handle changes. Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-10-08 19:59:39 +02:00
psutil
requirements-base.txt: fix pylink package name This should be pylink-square. Reported-by: Henrik Brix Andersen <henrik@brixandersen.dk> Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2021-05-03 21:49:47 +02:00
pylink-square
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
requirements: add anytree Needed now by both ram and rom report targets. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2020-08-14 21:46:09 +02:00
# for ram/rom reports
anytree
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
# intelhex used by mergehex.py
intelhex
# it's west
requirements: bump west to >=0.10.1 We are in the process of changing the HEAD branch in the zephyr repository from 'master' to 'main'. Users will need west version at least 0.10.1 for the plain 'west init' line in the getting started guide to still work after that change. To avoid problems: - add -U to the macOS and Windows lines for installing west (this option is already there for Ubuntu). Upgrading west will make the guide 'just work' for users who have an old version. - bump the minimum version in the relevant requirements file, in case anybody is doing something like basing a CI setup on those versions. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2021-05-11 17:40:05 +02:00
west>=0.10.1
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 for windows based 'menuconfig'
# "win32" is used for 64-bit Windows as well
windows-curses; sys_platform == "win32"
Reference in a new issue Copy permalink