Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Can't build the documentation sets for Bridle and Zephyr anymore #270

Open
1 of 3 tasks
rexut opened this issue Oct 30, 2024 · 0 comments
Open
1 of 3 tasks
Assignees
Labels
bug Something isn't working
Milestone

Comments

@rexut
Copy link
Member

rexut commented Oct 30, 2024

Describe the bug
Since Zephyr upstream goes on to v4.0 and thus removes some major functional features for processing all the spreaded RST documentation in code we are no longer able to rebuild our own downstream documentation sets for Bridle. The following functions have been removed without replacement:

Additional changes inside the Zephyr upstream documentation build process that Bridle now have to or should respect:

To Reproduce
Steps to reproduce the behavior:

  1. proper Bridle workspace setup from main branch
  2. cmake -Bbuild/bridle-doc -GNinja bridle/doc
  3. ninja -Cbuild/bridle-doc zephyr-doxygen
  4. ninja -Cbuild/bridle-doc bridle-doxygen
  5. ninja -Cbuild/bridle-doc build-all
  6. See error:
    ninja: Entering directory `build/bridle-doc'
    ninja: error: '/.../workspace/zephyr/doc/known-warnings.txt', needed by 'zephyr/known- 
    warnings.txt', missing and no known rule to make it
    

Expected behavior
Rebuild all documentation sats as before.

Impact
Showstopper: can't release next Bridle version.

Logs and console output
See above.

Screenshots
None.

Development Environment (please complete the following information):

  • OS: Linux
  • Toolchain: West v1.3.0, CMake v3.28.1, Sphinx v8.1.3, Doxygen v1.9.8
  • Branch: main, Zephyr v4.0.0-rc1 (upstream main)

Additional context
None.

Procedure

Error correction is increasingly proving to be a more complex challenge than initially expected. We will therefore proceed via several pull requests in the following individual steps.

  • Fix the new board catalog generator to skip foreign boards (the Bridle boards) on our own Zephyr main line mirror repository at https://github.com/tiacsys/zephyr.
  • Copy and own the always removed zephyr.warnings_filter Sphinx extension as bridle.warnings_filter – as long as Bridle have to rebuild different documentation sets by a splitted strategy (apartly the document inventory first and then the other documents at all that dependent to other inventories), Bridle have to expect and tolerate warnings of unknown or invalid references to "other" inter-Sphinx documents. In the past it was a good practice to filter out such expected warnings explicitly by the warnings_filter.
  • Remove the dependency to the Sphinx extension breathe (and interbreathe) also for the Bridle documentation set in the same manner as Zephyr already done. The Bridle documentation will swap to the new functionality by the Zephyr provided Sphinx extensions zephyr.doxybridge and maybe zephyr.doxytooltip
@rexut rexut added the bug Something isn't working label Oct 30, 2024
@rexut rexut self-assigned this Oct 30, 2024
@rexut rexut added this to the v3.7.99 milestone Oct 30, 2024
@rexut rexut modified the milestones: v3.7.99, v4.0.0 Nov 10, 2024
rexut added a commit that referenced this issue Nov 10, 2024
Add statement about the copy-and-onw of Sphinx extension warnings_filter.
Add GitHub issues #270, #271 and #272.

Signed-off-by: Stephan Linz <[email protected]>
rexut added a commit that referenced this issue Nov 10, 2024
Add statement about the copy-and-onw of Sphinx extension warnings_filter.
Add GitHub issues #270, #271 and #272.

Signed-off-by: Stephan Linz <[email protected]>
rexut added a commit that referenced this issue Nov 14, 2024
Add statement about the copy-and-onw of Sphinx extension warnings_filter.
Add GitHub issues #270, #271 and #272.

Signed-off-by: Stephan Linz <[email protected]>
rexut added a commit that referenced this issue Nov 14, 2024
Add statement about the copy-and-own of Sphinx extension warnings_filter.
Add GitHub issues #270, #271 and #272.

Signed-off-by: Stephan Linz <[email protected]>
rexut added a commit that referenced this issue Nov 15, 2024
Add statement about:

  * the CI workflow changes
  * the standalone 'stm32f777xx' SoC support by Bridle
  * the DTS binding and Kconfig changes for the two I2C-based
    GPIO expander 'PCA9554' and 'PCA9555'
  * the copy-and-own of Sphinx extension 'warnings_filter'
  * the changes on documentation level: Sphinx v8.1, Sphinx
    copy button, inter-Sphinx links with valid official syntax
    and update output messages

Add GitHub issues #270, #271 and #272.

Signed-off-by: Stephan Linz <[email protected]>
rexut added a commit that referenced this issue Nov 15, 2024
Add statement about:

  * the CI workflow changes
  * the standalone 'stm32f777xx' SoC support by Bridle
  * the DTS binding and Kconfig changes for the two I2C-based
    GPIO expander 'PCA9554' and 'PCA9555'
  * the copy-and-own of Sphinx extension 'warnings_filter'
  * the changes on documentation level: Sphinx v8.1, Sphinx
    copy button, inter-Sphinx links with valid official syntax
    and update output messages

Add GitHub issues #270, #271 and #272.

Signed-off-by: Stephan Linz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant