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-doc.txt

12 lines
177 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
# DOC: used to generate docs
doc: bump breathe requirement to >=4.23.0 Breathe>=4.23.0 brings in basic xrefitem rendering support and fixes issues parsing anonymous struct/unions. This version also adds a config knob for showing or hiding enumerator values, so set it to generate documentation compatible with previous versions. Signed-off-by: Fabio Utzig <fabio.utzig@nordicsemi.no>
2020-10-23 18:40:49 +08:00
breathe>=4.23.0
doc: update versions of build tools Update documentation build tooling: - Sphinx>=3.2.0 - Breathe>=4.20.0 - docutil>=0.16.0 Signed-off-by: Fabio Utzig <fabio.utzig@nordicsemi.no>
2020-08-12 23:49:44 +08:00
docutils>=0.16
doc: fix broken text search Require Sphinx<3.4.0 to avoid the issue described in: https://github.com/sphinx-doc/sphinx/issues/8603 This requirement can be relaxed once a new sphinx-rtd-theme is released. Signed-off-by: Fabio Utzig <fabio.utzig@nordicsemi.no>
2020-12-28 20:15:48 +08:00
sphinx>=3.3.0,<3.4.0
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
sphinx_rtd_theme
sphinx-tabs
sphinxcontrib-svg2pdfconverter
requirements-doc: add missing pkwalify doc/CMakeLists.txt uses zephyr_module Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2021-01-09 05:43:25 +08:00
# Used by zephyr_module
pykwalify