# Suitable versions of Sphinx for building different versions of CMake Docs?

**URL:** https://discourse.cmake.org/t/suitable-versions-of-sphinx-for-building-different-versions-of-cmake-docs/7982
**Category:** Development
**Created:** [April 25, 2023, 5:01pm UTC](https://discourse.cmake.org/t/suitable-versions-of-sphinx-for-building-different-versions-of-cmake-docs/7982 "2023-04-25T17:01:33Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [March 29, 2024, 11:26am UTC](https://discourse.cmake.org/t/suitable-versions-of-sphinx-for-building-different-versions-of-cmake-docs/7982/9 "2024-03-29T11:26:15Z")

</div>

> [@hwhsu1231](#):
>
> Is it technically possible to do so?

I suspect other changes may need backported to those source trees. But CMake generates its docs from the source tree, so some tracking of how to update these releases to newer Sphinx would best be tracked in the history as well (basically, branch off of the last 3.0.x release, update it to work with new Sphinx, then regenerate and merge the changes into `master` with `-s ours` for tracking purposes). What would be the benefit of regenerating the docs?

---

_[View the full topic](https://discourse.cmake.org/t/suitable-versions-of-sphinx-for-building-different-versions-of-cmake-docs/7982)._