> > > 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. >
That was my plan B. I've implemented it in Python and it works: https://github.com/zephyrproject-rtos/zephyr/pull/13159 restore_modifications_times.py In this particular example this brings down the incremental build time from 70-80 seconds down to less than 10 seconds. It took a surprisingly high number of lines of code: about 100. As usual file management in Python proved wordy. But hey, data structures suck in shell script and it's not even portable anyway. To be fair these 100 lines include logging and a decent option parser with help text. This script is not specific to Doxygen and could be used for other similar situations (Apache license). Back to Doxygen I suspect this script could be entirely avoided with say 10-20 lines of logic inside Doxygen itself? :-( Marc
_______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
