On Thu, May 2, 2013 at 4:02 PM, Hanspeter Niederstrasser <
[email protected]> wrote:
> After trying to understand the doxygen build system, I can say this:
>
> 1) the bad compiler commands come from src/Makefile.libdoxycfg. In the
> failed builds, src/Makefile.libdoxycfg is not regenerated by tmake and
> therefore uses the file that came with the tarball
>
> 2) src/Makefile.libdoxycfg is not regenerated because the
> "Makefile.libdoxycfg" target in src/Makefile is skipped
>
> For reasons that we have not been able to figure out, this target is not
> run about 50% of the time. This is the log output from a successful run:
>
What's the difference in the modification times between libdoxycfg.pro and
Makefile.libdoxycfg and what is the timing resolution of the file system?
Could make think that the Makefiles are newer than the pro files?
Does touching the pro files after extracting them force a rebuild of the
Makefiles every time?
Erik
--
*************************************************
Erik Zeek
[email protected]
*************************************************
Against stupidity the very gods
Themselves contend in vain.
- Johann Christoph Friedrich von Schiller (1801)
*************************************************
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Doxygen-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
