You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simply adding a new version for which we want to generate API documentation in the Makefile has no effect; running make will not generate the API documentation if it has been generated earlier for a smaller set of versions because all the "stamp" files are unversioned. E.g., after adding a new Python version, I cannot simply run make python to update the Python docs. Running make clean_python && make python does the trick; however, it removes the entire Python build folder and all the generated Python docs so everything will be re-built from scratch. This will become a bottleneck as soon as we start having more versions in the makefile.
The ideal solution would be for make python to recognize that a new version was added and to build the documentation for that version only, leaving all previously generated versions alone.
The text was updated successfully, but these errors were encountered:
Simply adding a new version for which we want to generate API documentation in the
Makefile
has no effect; runningmake
will not generate the API documentation if it has been generated earlier for a smaller set of versions because all the "stamp" files are unversioned. E.g., after adding a new Python version, I cannot simply runmake python
to update the Python docs. Runningmake clean_python && make python
does the trick; however, it removes the entire Python build folder and all the generated Python docs so everything will be re-built from scratch. This will become a bottleneck as soon as we start having more versions in the makefile.The ideal solution would be for
make python
to recognize that a new version was added and to build the documentation for that version only, leaving all previously generated versions alone.The text was updated successfully, but these errors were encountered: