[Resend including the list, updated]

On 24 Apr 2014, at 15:53, Eric Gallager <eg...@gwmail.gwu.edu> wrote:

> Instead of modifying the Makefile, how about trying to modify the Doxyfile 
> instead? That was what eventually worked for me when I was running into some 
> issues with doxygen when adding a `+docs` variant to the port for dpkg…
> 

For sure in practice it is not possible to act on the Makefile which is 
dynamically created in the build step. But I have no idea how this would be 
influences in doxygen and where to start looking. Now, I will have closer look 
into the `Doxyfile` and the cited port to get a better idea.

Update:
I actually looked at the port `pdkg`, but found no trace of some patch to 
Doxyfile or a `+docs` variant. Are you referring really to this port? I also 
looked at the `Doxyfile` and found no parameter which would influence the 
rebuild look.

Thanks!
~petr


> 
> 
> On Tue, Apr 22, 2014 at 2:16 PM, Peter Danecek <peter.dane...@bo.ingv.it> 
> wrote:
> 
> Hi all,
> 
> I am running into some quite stupid build problem with a not yet official 
> globus port, `globus_ftp_control`. This software also builds documentations 
> via doxygen and the problem is related to doxygen/pdflatex, but I have no 
> idea how to fix this.
> 
> During the process doxygen creates some Makefile with a loop to run 
> `pdflatex` several times until no rebuild is needed. The logic is probably 
> that it would run few times, and if there is some problem and the process 
> does not converge, this is caught at count=5. Now looking into the details I 
> realise that on my system the document/pdflatex, there are really 5 
> iterations need to build the document, so I hit the limit and the process is 
> interrupted.
> 
> A easy fix would e to raise the no. of iterations, or to modify the Makefile 
> in some other way. But as all this doc directories are created during the 
> build by doxygen I have no idea how to influence the process.
> 
> Any ideas what could be done to solve this issue?
> 
> Thanks!
> ~petr
> 
>  
> _______________________________________________
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
> 
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to