PDF compilation creates a lot of aux files

[jecisc]

If you generate PDF with Pillar 4 you get a lot of noise in the book result. A lot of file as: .aux, .fls, .listing…

This should be clean IMO.

[YannDub]

For me, it is not the job of pillar to delete those files, but the script

[jecisc]

Do you have another forge for the scripts?

[YannDub]

For the moment, every books are their Makefile, so, we don't have another forge.

But we have Pillar-Archetype to describe archetypes. I think it's a good place to talk about the scripts.

[guillep]

Everything should be managed from Pharo. We cannot have our workflow divided between:

• pharo
• makefiles
• bash scripts
• ...

I'm in a next release removing at least all makefiles. The build can already be done from Pharo using OSSubprocess.

This issue is however still valid in latest pillar versions: pdf compilation leaves a lot of intermediate files.

[guillep]

This could be solved in two ways:

1. having an intermediate build directory where the build is done and intermediate files are created. And a results directory where the resulting files are copied at the end.
2. having just a clean action on the build directory.

[cdlm]

LatexMk is already used to drive the compilation. It can also clean up temporary files (see flag -c).