Re: Compare with already existing and identical output file and *not* refresh its *filesystem* timestamp?

Marc Herbert <[email protected]> Thu, 14 Feb 2019 12:39:40 -0800
Newsgroups gmane.text.doxygen.general
Message-ID <CA+rkZbi1qQcvV=fzbh7jjOgiioKBB9YLt8B8dYZVDr+8MMznJg@mail.gmail.com>
Short of actually implementing complex incremental builds, there's another,
unrelated and also much simpler optimization Doxygen could do: just vaguely
keep track of modified times on *input* files.

1. Offer some way to --remember the newest modified_time across all input
files. Could be stored in some empty file.
2. Then have a new, optional feature that: "--runs only if any input file
is newer than this (empty) file"

This would make a huge difference for incremental builds that involve not
just doxygen but other (and faster) tools too; they could just skip running
doxygen when not needed.

I considered filing a new doxygen feature request for this on github (and
also for the previously discussed *output* mtime optimization), however
https://github.com/doxygen/doxygen/issues has 1800+ open issues right now
so it feels like a black hole.

PS: If anyone has ideas on how to emulate this with a small number of lines
of CMake then please share. For instance this could generate an empty file
right before starting doxygen as a decent approximation.

_______________________________________________
Doxygen-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doxygen-users