On computers without internet connectivity, attempts to build manuals fail with the following (or similar) output: make html DOC=dev-manual ******** Building dev-manual cd dev-manual; xsltproc --xinclude -o dev-manual.html dev-manual-customization.xsl dev-manual.xml; cd .. error : No such file or directory warning: failed to load external entity "http://downloads.yoctoproject.org/mirror/docbook-mirror/docbook-xsl-1.76.1/xhtml/docbook.xsl" compilation error: file dev-manual-customization.xsl line 4 element import xsl:import : unable to load http://downloads.yoctoproject.org/mirror/docbook-mirror/docbook-xsl-1.76.1/xhtml/docbook.xsl make html DOC=mega-manual ******** Building mega-manual cd mega-manual; xsltproc --stringparam html.stylesheet mega-style.css --stringparam chapter.autolabel 1 --stringparam section.autolabel 1 --stringparam section.label.includes.component.label 1 --xinclude -o mega-manual.html mega-manual-customization.xsl mega-manual.xml; cd .. error : No such file or directory warning: failed to load external entity "http://downloads.yoctoproject.org/mirror/docbook-mirror/docbook-xsl-1.76.1/xhtml/docbook.xsl" compilation error: file mega-manual-customization.xsl line 4 element import xsl:import : unable to load http://downloads.yoctoproject.org/mirror/docbook-mirror/docbook-xsl-1.76.1/xhtml/docbook.xsl ******** Using mega-manual.sed to process external links cd mega-manual; sed -f ../tools/mega-manual.sed < mega-manual.html > mega-output.html; cd .. /bin/sh: mega-manual.html: No such file or directory ******** Cleaning up transient file mega-output.html cd mega-manual; rm mega-manual.html; mv mega-output.html mega-manual.html; cd .. rm: cannot remove ‘mega-manual.html’: No such file or directory mv: cannot stat ‘mega-output.html’: No such file or directory
This was confirmed in a very recent poky 81f9e815d36848761a9dfa94b00ad998bb39a4a6.
This is a known issue, our manuals needs a copy of the dockbook xsl files to build. As such making this work offline is an enhancement we could consider in the next release. Not quite sure how we'd do that though.
Perhaps a bitbake recipe could be used so bitbake's abilities to support offline builds could be leveraged to support offline building of the documents.
We have switch to Sphinx so this is obsolete.