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

[Aidan G. <wgs...@ih...>]

Christian Walther wrote:
> 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.

Ok, I figured out what the problem was: By default, make uses /bin/sh as the
shell, and that is very often, on Unix systems, a link to the bash binary, but
on some Linux configurations, that is instead a link to (or is the binary) a
more stripped down, POSIX compliant shell that isn't compatable with all bash
scripts.  So if I add the line...

export SHELL=/bin/bash

...to the top of the Makefile, it runs, and actually finishes.

Since the Makefile for the Pipmak documentation uses some bash specific 
features (i.e. is not 100% POSIX compliant), should this line be added to the 
documentation Makefile?

> 
>> 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.

I think that might be best, so that the EXACT SAME file is packaged with each 
OS build of Pipmak.  I don't know if there would be any slight differences if 
there were different people generating Reference.pdf on different systems, but 
it would probably best to try to avoid that for the official release.

> 
>>> 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
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Pipmak-Devel mailing list
> Pip...@li...
> news://news.gmane.org/gmane.games.devel.pipmak.devel
> https://lists.sourceforge.net/lists/listinfo/pipmak-devel
>