Re: [Pipmak-Devel] The Pipmak Make setup for Linux

[Christian W. <cwa...@gm...>]

Aidan Gauland wrote:
> when I type "make" in "pipmak/documentation/" it seems to run
> something that looks like it's dealing with LATEX in an infinite
> loop

The loop isn't supposed to be infinite. It's supposed to loop until the 
.toc, .aux, and .ind files stop changing. Two or three times through the 
loop should be sufficient for that. The files depend on each other in a 
roundabout way: the first pdflatex run creates Reference.toc, 
Reference.idx, and an unfinished version of Reference.pdf. Then 
makeindex generates Reference.ind from Reference.idx. The second run of 
pdflatex integrates Reference.toc and Reference.ind to generate an 
updated version of Reference.pdf. Or something like that. I don't 
remember what the .aux file is for, perhaps section links.

> but when I run "pdflatex Reference.tex" it seems to generate
> Reference.pdf, Reference.aux, Reference.idx, Reference.log,
> Reference.out, and Reference.toc just fine.

But I bet that Reference.pdf has incomplete or missing table of 
contents, index, or section links.

> Is this okay for putting in the Pipmak releases?

If you don't want to fiddle with the LaTeX stuff, you could package the 
Reference.pdf generated by me. We can talk about how to best organize that.

>> That looks like it only runs if the current working directory is the 
>> directory that contains pipmak-bin and libs. Is that acceptable?
> 
> Hmmm, maybe not.  I could put pipmak-bin and libs in a directory called
> something like "data", and leave the wrapper script "pipmak" where it is.

How would that solve the problem?

> I guess the best way to find out works best is to let Linux users try
> it out, and make changes based on feedback (on the Pipmak users
> mailing list).

OK. I'm still trying to find out how we would publish such test 
packages. SourceForge doesn't want us to release files on the web site, 
and using the file release systems where each release will be kept 
around forever doesn't sound right either. I somehow seem to remember 
that SourceForge had a specific facility for releasing nightly builds, 
but I can't find any trace of it now.

  -Christian