Closed rytis-paskauskas closed 2 years ago
Hi, sorry for the late reply.
build_docs.py
injects a environment variable called BUILDDIR
, which is missing if you call sphinx directly like this. You can try exporting this before running it. It's the link to the build directory for the docs (the build output), so e.g. path-to/esp-idf/path-to/esp-idf/docs/en /path-to/esp-idf/docs/_build/en/esp32
in your case.
Just curious, any reason why you need to invoke it this way instead of letting build-docs
handle it?
Guys, never been able to build the docs (but building ESP32 projects with esp-idf goes smoothly, so I guess the installation is OK) Any help to resolving this issue and pointers towards successfully building the help/manual, will be most appreciated. Here's the
/tmp/sphinx-err-[a-z]*.txt
file.The above is a result of
python -u -m sphinx.cmd.build -j 1 -b html -d /path-to/esp-idf/docs/_build/en/esp32/doctrees -w sphinx-warning-log.txt -t esp32 -D idf_target=esp32 -D docs_to_build= -D config_dir=/path-to/.local/lib/python3.9/site-packages/esp_docs -D doxyfile_dir=/path-to/esp-idf/docs -D project_path=/path-to/esp-idf/path-to/esp-idf/docs/en /path-to/esp-idf/docs/_build/en/esp32/html
which is my translation ofbuild-docs -l en -t esp32
, in which I substituted/usr/bin/python
withpython
, the latter being a link to the binaries that the API expects.