Open hongxuchen opened 7 years ago
Hi thank you for your interest.
I don't know exactly what do you understand by include latexmk
to the project. latexmk
at the end of the day a perl script
and as far as I see this Makefile
is a replacement for it.
Maybe the question arises for the need for documentation for this
Makefile, the nice feature I use all the time is the target for creating
figures in a project, you can check what I mean by going to the tests
and testing it for yourself, for example the test build-dir
has the
following structure
tests/build-dir/
├── config.mk
├── doTest.sh
├── file.bib
├── file.tex
├── images
│ ├── test.asy
│ ├── transitions.tex
└── Makefile
when we hit make
we obtain
tests/build-dir/
├── build
│ ├── file.aux
│ ├── file.bbl
│ ├── file.bib
│ ├── file.blg
│ ├── file.log
│ ├── file.pdf
│ └── file.toc
├── config.mk
├── doTest.sh
├── file.bib
├── file.pdf
├── file.tex
├── images
│ ├── build
│ │ ├── transitions.aux
│ │ ├── transitions.log
│ │ └── transitions.pdf
│ ├── test.asy
│ ├── test.pdf
│ ├── transitions.pdf
│ └── transitions.tex
└── Makefile
this means the asymptote files and the tex
files in the images
directory have been created automatically. As far as I know you don't
get this kind of behaviour with latexmk
. So for me and people using
this makefile, it is a replacement for latexmk
that you can simply
leave in your working directory for other collaborators also to use.
Thanks for your reply.
What I mean is that you may use latexmk
to deal with what it is good at
and use latex-makefile
as a program to drive it and other tools.
Anyway, latexmk has been existing for a couple of years and since it's
written in perl it has the potential be more portable.
This is only my favor, though.
Best Regards, Hongxu
On Sun, Feb 12, 2017 at 6:36 PM, alejandrogallo notifications@github.com wrote:
Hi thank you for your interest. I don't know exactly what do you understand by include
latexmk
to the project.latexmk
at the end of the day a perl script and as far as I see thisMakefile
is a replacement for it.Maybe the question arises for the need for documentation for this Makefile, the nice feature I use all the time is the target for creating figures in a project, you can check what I mean by going to the tests and testing it for yourself, for example the test
build-dir
has the following structuretests/build-dir/ ├── config.mk ├── doTest.sh ├── file.bib ├── file.tex ├── images │ ├── test.asy │ ├── transitions.tex └── Makefile
when we hit
make
we obtaintests/build-dir/ ├── build │ ├── file.aux │ ├── file.bbl │ ├── file.bib │ ├── file.blg │ ├── file.log │ ├── file.pdf │ └── file.toc ├── config.mk ├── doTest.sh ├── file.bib ├── file.pdf ├── file.tex ├── images │ ├── build │ │ ├── transitions.aux │ │ ├── transitions.log │ │ └── transitions.pdf │ ├── test.asy │ ├── test.pdf │ ├── transitions.pdf │ └── transitions.tex └── Makefile
this means the asymptote files and the
tex
files in theimages
directory have been created automatically. As far as I know you don't get this kind of behaviour withlatexmk
. So for me and people using this makefile, it is a replacement forlatexmk
that you can simply leave in your working directory for other collaborators also to use.— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alejandrogallo/latex-makefile/issues/1#issuecomment-279209602, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzeAxINLMacuUzGfmEO1rzUfjTSAyfwks5rbuDFgaJpZM4L-beD .
I'll explore the possibility of adding the current Makefile
behavior for .tex
and .bib
compilation as a fallback
for systems with no latexmk
program installed, I think that
would be getting the best from both worlds, of course you are
more than welcome to contribute ;) Thank you for your suggestion.
AFAIK,
latexmk
is also doing automation of latex compiling however is different from whatlatex-makefile
does (as to html, pandoc, python, etc.). Therefore is it possible to integrate that into this project?