-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generating coqdoc on merge to master #19
Comments
What does coqdoc need to produce HTML? Does it need to compile the project? |
coqdoc can work without having to compile the project, but it will then not have any cross-references between files/projects. For that, the |
Coqdoc uses the .glob files to generate links between different .v files.
If the .glob are absent (or too old ?), it generates a warning.
… Le 5 janv. 2021 à 17:14, Théo Zimmermann ***@***.***> a écrit :
What does coqdoc need to produce HTML? Does it need to compile the project?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJW6FCVDG7QVHNCTQXSEXWDSYM3ERANCNFSM4VVCMZEA>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@Zimmi48 could it be a good idea to generate coqdoc HTML on all merges to master in the same CI job as the LaTeX one? Maybe this approach to documentation could be used for additional projects until we have more automation for releases?
The text was updated successfully, but these errors were encountered: