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
Building the profiles PDF document, asciidoctor will report
asciidoctor: WARNING: image to embed not found or not readable: .../sig-soft-cpu/TG/riscv-profiles/images/riscv-images/risc-v_logo.png
This is due to the lack of the docs-resources submodule in the riscv-profiles directory, which in turn is due to riscv-profiles being included as a subtree, not a submodule. A subtree was used in this case since these profiles are only for discussion, not active development, and a subtree is a lower overhead solution.
It is expected that if and when the profile discussion elevates to a more formal draft, the documents will move to a more suitable location. A subtree allows the history here to be migrated when that happens.
In the interim, the above warning can simply be ignored, and the resulting PDF will be generated except for the RISC-V logo. Alternatively, one can manually populate the docs-resources directory, perhaps with a symlink to a local clone of that repository.
The text was updated successfully, but these errors were encountered:
Building the profiles PDF document, asciidoctor will report
This is due to the lack of the docs-resources submodule in the riscv-profiles directory, which in turn is due to riscv-profiles being included as a subtree, not a submodule. A subtree was used in this case since these profiles are only for discussion, not active development, and a subtree is a lower overhead solution.
It is expected that if and when the profile discussion elevates to a more formal draft, the documents will move to a more suitable location. A subtree allows the history here to be migrated when that happens.
In the interim, the above warning can simply be ignored, and the resulting PDF will be generated except for the RISC-V logo. Alternatively, one can manually populate the
docs-resources
directory, perhaps with a symlink to a local clone of that repository.The text was updated successfully, but these errors were encountered: