Skip to content
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

reference page intro.html not being generated #1121

Closed
bashbaug opened this issue Mar 31, 2024 · 3 comments · Fixed by #1127
Closed

reference page intro.html not being generated #1121

bashbaug opened this issue Mar 31, 2024 · 3 comments · Fixed by #1127
Assignees

Comments

@bashbaug
Copy link
Contributor

It looks like the reference page "intro.html" is not being properly generated, so the initial reference page "index.html" is showing a missing page. There is probably an issue in the build scripts somewhere, but I'm not exactly sure where the problem lies.

I am generating the reference pages with:

python3 makeSpec -clean -spec khr OUTDIR=out -j32 manhtmlpages

oddhack added a commit that referenced this issue Apr 1, 2024
These were commented out during debugging and not restored.
Also factors out a small difference between Vulkan and OpenCL scripts.

Closes #1121
@oddhack
Copy link
Contributor

oddhack commented Apr 1, 2024

Should be fixed in #1127. However, note that while the alphabetic refpage index in the left panel is autogenerated and should be complete, the category index following that is a static file that has not been updated in some time and does not include some extension refpages and extension APIs (this is in man/toctail). It would be difficult to autogenerate this, but relatively straightforward to check it against the refpages to see which refpages are not mentioned somewhere in the category index, and perhaps even throw a CI error if there are any.

Orthogonally, @bashbaug would you be OK with setting 'Automatically delete head branches' on merge in the repo settings? I noticed my branches were not being deleted which surprised me, although it appears? other branches are, so maybe most WG members are used to cleaning up after themselves.

@bashbaug
Copy link
Contributor Author

bashbaug commented Apr 1, 2024

would you be OK with setting 'Automatically delete head branches' on merge in the repo settings? I noticed my branches were not being deleted which surprised me, although it appears? other branches are, so maybe most WG members are used to cleaning up after themselves.

Works for me, though we may want to check with the working group to be sure.

I've just been cleaning up after myself, but if this could be done automatically it'd save me a click.

bashbaug pushed a commit that referenced this issue Apr 1, 2024
These were commented out during debugging and not restored.
Also factors out a small difference between Vulkan and OpenCL scripts.

Closes #1121
@bashbaug
Copy link
Contributor Author

bashbaug commented Apr 1, 2024

note that while the alphabetic refpage index in the left panel is autogenerated and should be complete, the category index following that is a static file that has not been updated in some time and does not include some extension refpages and extension APIs (this is in man/toctail). It would be difficult to autogenerate this, but relatively straightforward to check it against the refpages to see which refpages are not mentioned somewhere in the category index, and perhaps even throw a CI error if there are any.

I just merged #1127, which automatically closed this issue.

Should we file any other trackers for this task?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants