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

[Patch] Add extra files to HTML output (Origin: bugzilla #640875) #4121

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity enhancement in component general for ---
Reported in version unspecified on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2011-01-29 00:56:15 +0000, Haffmans wrote:

Created attachment 179567
Extra files for HTML patch

I've patched Doxygen to allow copying extra files (such as images, javascript, etc) to the HTML output directory. This makes it much easier to create richer templates with additional images etc., rather than being restricted to just the header, footer and style sheet.

The approach is as follows:

  • Configuration tag "HTML_EXTRA_FILES" takes a list of files to copy
  • After copying the logo and stylesheet, these files are copied. They are also added to the indexList, so they will be copied along to compressed help files (I tested with the QHelpGenerator, and that works).

I've only briefly tested this, so far with success.

Note that at the moment only single files are allowed, not directories. That might be a useful addition.

The patch is attached.

On 2011-01-29 15:04:10 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2011-03-28 14:18:56 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.4. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment