At least for html you can set the option HTML_TIMESTAMP = OFF.
Sebastien.
On 02/07/2019 04:15 AM, Richard Damon wrote:
On 2/6/19 9:45 PM, Marc Herbert wrote:
Hi,
I understand incremental doxygen compilation is a hard problem. I've
read some of the past discussions. This request is *not* about
incremental doxygen compilation and it is not about making doxygen
faster at all. It's about something much simpler.
Can doxygen redundantly recompute everything from scratch (even when
no input has changed), and then at the very end compare and realise
that it just regenerated the exact same (XML, HTML,...) output file
that is already there from the previous run? Is there in this case an
option /not/ to refresh the timestamp? I mean on a per output file
basis of course.
Refreshing the timestamp has a disastrous cascade effect on further
processing like Sphinx which wrongly assumes everything has changed
even when no doxygen output has changed at all (except timestamps).
Marc
The simplest method in my mind would be to have a post-process task
that compares the Doxygen output directory with another copy, updating
that copy if there is a ''significant' (not just timestamping)
difference. It would be a simple enough program to write to customize
for you own needs.
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
