Is my current workflow worth using or idiotic?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
10
down vote

favorite
2












I am currently writting my thesis and use several graphics which I make using tikz. For now on my workflow/document looks as the following:



In the latex project folder I have a seperate folder where I store all my .tex files which contains the drawings.



So for example:



  • business_model_overview.tex

  • distribution_of_findings.tex

  • ...

I then include these files in the main latex_file just by using the include option.



The tikz files mentioned above are created capsulated either using Tikz_EDT or QTikz.



I nowstarted to rearranging my worklfow as I swapped using Kile as Editor instead of Overleaf as before. I heared about the standalone_package I did not use till now.



Simple qeustion: Would the use of the standalone package could make my life/workflow easier in any form?
Is my current workflow okay or did you see some aspects for improvement as I can adjust now before starting over.
[ One downward as I see till now could be that every time I recompile each picture must be compiled again. But not sure if this is really so bad. ]



Many thanks in advacne for suggestions.




tikz-pgf standalone workflow




share|improve this question




















  • I actually use always the standalone class for creating TikZ pictures ('cause so I can see more details and so on), but your way of doing TeX (or writing your thesis) isn't bad. I can tell only for me: I would do it exactly that way (but I wouldn't use an external TikZ editor for creating pictures, as you mentioned it is better to use the standalone package …).
    – current_user
    Aug 15 at 17:54






  • 3




    You're using include for those pictures? That is not good, as include does a clearpage, input seems like the reasonable thing to do for pictures (if they shouldn't be made standalone).
    – Skillmon
    Aug 15 at 17:55










  • My workflow for documents with many TikZ graphics differs quite a lot. I'll create a write-up (using GNU make).
    – Skillmon
    Aug 15 at 17:57










  • @Skillmon sorry that was my fault, I look it up and you were right, I use input rather than include
    – SRel
    Aug 15 at 18:11










  • Not directly applicable but possibly helpful: tex.stackexchange.com/questions/123058/…
    – Ethan Bolker
    Aug 16 at 15:55














up vote
10
down vote

favorite
2












I am currently writting my thesis and use several graphics which I make using tikz. For now on my workflow/document looks as the following:



In the latex project folder I have a seperate folder where I store all my .tex files which contains the drawings.



So for example:



  • business_model_overview.tex

  • distribution_of_findings.tex

  • ...

I then include these files in the main latex_file just by using the include option.



The tikz files mentioned above are created capsulated either using Tikz_EDT or QTikz.



I nowstarted to rearranging my worklfow as I swapped using Kile as Editor instead of Overleaf as before. I heared about the standalone_package I did not use till now.



Simple qeustion: Would the use of the standalone package could make my life/workflow easier in any form?
Is my current workflow okay or did you see some aspects for improvement as I can adjust now before starting over.
[ One downward as I see till now could be that every time I recompile each picture must be compiled again. But not sure if this is really so bad. ]



Many thanks in advacne for suggestions.




tikz-pgf standalone workflow




share|improve this question




















  • I actually use always the standalone class for creating TikZ pictures ('cause so I can see more details and so on), but your way of doing TeX (or writing your thesis) isn't bad. I can tell only for me: I would do it exactly that way (but I wouldn't use an external TikZ editor for creating pictures, as you mentioned it is better to use the standalone package …).
    – current_user
    Aug 15 at 17:54






  • 3




    You're using include for those pictures? That is not good, as include does a clearpage, input seems like the reasonable thing to do for pictures (if they shouldn't be made standalone).
    – Skillmon
    Aug 15 at 17:55










  • My workflow for documents with many TikZ graphics differs quite a lot. I'll create a write-up (using GNU make).
    – Skillmon
    Aug 15 at 17:57










  • @Skillmon sorry that was my fault, I look it up and you were right, I use input rather than include
    – SRel
    Aug 15 at 18:11










  • Not directly applicable but possibly helpful: tex.stackexchange.com/questions/123058/…
    – Ethan Bolker
    Aug 16 at 15:55












up vote
10
down vote

favorite
2









up vote
10
down vote

favorite
2






2





I am currently writting my thesis and use several graphics which I make using tikz. For now on my workflow/document looks as the following:



In the latex project folder I have a seperate folder where I store all my .tex files which contains the drawings.



So for example:



  • business_model_overview.tex

  • distribution_of_findings.tex

  • ...

I then include these files in the main latex_file just by using the include option.



The tikz files mentioned above are created capsulated either using Tikz_EDT or QTikz.



I nowstarted to rearranging my worklfow as I swapped using Kile as Editor instead of Overleaf as before. I heared about the standalone_package I did not use till now.



Simple qeustion: Would the use of the standalone package could make my life/workflow easier in any form?
Is my current workflow okay or did you see some aspects for improvement as I can adjust now before starting over.
[ One downward as I see till now could be that every time I recompile each picture must be compiled again. But not sure if this is really so bad. ]



Many thanks in advacne for suggestions.




tikz-pgf standalone workflow




share|improve this question












I am currently writting my thesis and use several graphics which I make using tikz. For now on my workflow/document looks as the following:



In the latex project folder I have a seperate folder where I store all my .tex files which contains the drawings.



So for example:



  • business_model_overview.tex

  • distribution_of_findings.tex

  • ...

I then include these files in the main latex_file just by using the include option.



The tikz files mentioned above are created capsulated either using Tikz_EDT or QTikz.



I nowstarted to rearranging my worklfow as I swapped using Kile as Editor instead of Overleaf as before. I heared about the standalone_package I did not use till now.



Simple qeustion: Would the use of the standalone package could make my life/workflow easier in any form?
Is my current workflow okay or did you see some aspects for improvement as I can adjust now before starting over.
[ One downward as I see till now could be that every time I recompile each picture must be compiled again. But not sure if this is really so bad. ]



Many thanks in advacne for suggestions.





tikz-pgf standalone workflow





share|improve this question











share|improve this question




share|improve this question










asked Aug 15 at 17:48









SRel

34610




34610











  • I actually use always the standalone class for creating TikZ pictures ('cause so I can see more details and so on), but your way of doing TeX (or writing your thesis) isn't bad. I can tell only for me: I would do it exactly that way (but I wouldn't use an external TikZ editor for creating pictures, as you mentioned it is better to use the standalone package …).
    – current_user
    Aug 15 at 17:54






  • 3




    You're using include for those pictures? That is not good, as include does a clearpage, input seems like the reasonable thing to do for pictures (if they shouldn't be made standalone).
    – Skillmon
    Aug 15 at 17:55










  • My workflow for documents with many TikZ graphics differs quite a lot. I'll create a write-up (using GNU make).
    – Skillmon
    Aug 15 at 17:57










  • @Skillmon sorry that was my fault, I look it up and you were right, I use input rather than include
    – SRel
    Aug 15 at 18:11










  • Not directly applicable but possibly helpful: tex.stackexchange.com/questions/123058/…
    – Ethan Bolker
    Aug 16 at 15:55
















  • I actually use always the standalone class for creating TikZ pictures ('cause so I can see more details and so on), but your way of doing TeX (or writing your thesis) isn't bad. I can tell only for me: I would do it exactly that way (but I wouldn't use an external TikZ editor for creating pictures, as you mentioned it is better to use the standalone package …).
    – current_user
    Aug 15 at 17:54






  • 3




    You're using include for those pictures? That is not good, as include does a clearpage, input seems like the reasonable thing to do for pictures (if they shouldn't be made standalone).
    – Skillmon
    Aug 15 at 17:55










  • My workflow for documents with many TikZ graphics differs quite a lot. I'll create a write-up (using GNU make).
    – Skillmon
    Aug 15 at 17:57










  • @Skillmon sorry that was my fault, I look it up and you were right, I use input rather than include
    – SRel
    Aug 15 at 18:11










  • Not directly applicable but possibly helpful: tex.stackexchange.com/questions/123058/…
    – Ethan Bolker
    Aug 16 at 15:55















I actually use always the standalone class for creating TikZ pictures ('cause so I can see more details and so on), but your way of doing TeX (or writing your thesis) isn't bad. I can tell only for me: I would do it exactly that way (but I wouldn't use an external TikZ editor for creating pictures, as you mentioned it is better to use the standalone package …).
– current_user
Aug 15 at 17:54




I actually use always the standalone class for creating TikZ pictures ('cause so I can see more details and so on), but your way of doing TeX (or writing your thesis) isn't bad. I can tell only for me: I would do it exactly that way (but I wouldn't use an external TikZ editor for creating pictures, as you mentioned it is better to use the standalone package …).
– current_user
Aug 15 at 17:54




3




3




You're using include for those pictures? That is not good, as include does a clearpage, input seems like the reasonable thing to do for pictures (if they shouldn't be made standalone).
– Skillmon
Aug 15 at 17:55




You're using include for those pictures? That is not good, as include does a clearpage, input seems like the reasonable thing to do for pictures (if they shouldn't be made standalone).
– Skillmon
Aug 15 at 17:55












My workflow for documents with many TikZ graphics differs quite a lot. I'll create a write-up (using GNU make).
– Skillmon
Aug 15 at 17:57




My workflow for documents with many TikZ graphics differs quite a lot. I'll create a write-up (using GNU make).
– Skillmon
Aug 15 at 17:57












@Skillmon sorry that was my fault, I look it up and you were right, I use input rather than include
– SRel
Aug 15 at 18:11




@Skillmon sorry that was my fault, I look it up and you were right, I use input rather than include
– SRel
Aug 15 at 18:11












Not directly applicable but possibly helpful: tex.stackexchange.com/questions/123058/…
– Ethan Bolker
Aug 16 at 15:55




Not directly applicable but possibly helpful: tex.stackexchange.com/questions/123058/…
– Ethan Bolker
Aug 16 at 15:55










1 Answer
1






active

oldest

votes

















up vote
16
down vote



accepted










So as promised in the comments, here is my current setup for image-heavy documents using TikZ and similar (the below uses TikZ, circuitikz, includes SVGs, plots created with Python and possibly other images):



I maintain a shared preamble for all standalone TeX creations (like those of TikZ and circuitikz images) to sync stuff like font sizes and other stuff related to design. Additionally there is a shared preamble for every TikZ picture and a shared one for the circuitikz stuff.



For my latest work the shared preamble only includes



documentclass[tikz]standalone


the one dedicated to all ordinary TikZ pictures is in fact empty and the one for all the circuitikz images contains



usepackage[european,straightvoltages]circuitikz


For every image I can now create a file which contains only a begindocument and enddocument and the contents in between (additional preamble material for that file could be added here, too). circuitikz image code is saved as img/<filename>.circuit, ordinary TikZ pictures as img/<filename>.tikz.



The next thing to setup is a Makefile for the main document and another Makefile for all those images.



The main Makefile for my latest project looks like this:



# User defined variables 
##########################################
# engine to be used
TEX = pdflatex
# flags for that engine
FLAGS = -halt-on-error -8bit
# relative path to included TeX-files
TEXF = ./tex
# relative path to included TeX-files containing only preamble stuff
PREF = ./preamble
# relative path to img folder containing tikz and circuit files
IMGF = ./img
##########################################
# 
# Automatically defined variables 
##########################################
FILE = $(wildcard ./*.tex)
SFILES = $(wildcard $(TEXF)/*.tex)
PREAMB = $(wildcard $(PREF)/*.tex)
PREAMB += $(wildcard $(PREF)/*.sty)
PREAMB += $(wildcard ./*.sty)
NAME = $(FILE:%.tex=%)
OUT = $(NAME).pdf
FMT = $(NAME).fmt
##########################################
# 
# default target 
## the name 'quick' maybe misleading! 'all' might be faster if $(FILE) hasn't
## changed. 'quick' is for quickly running TeX assuming that you know what
## you're doing
quick: $(FMT) img
 $(TEX) $(FLAGS) -fmt="$(NAME)" $(FILE)
 #$(TEX) $(FLAGS) $(FILE);
# 
all: img $(OUT) #bib
$(OUT): $(FILE) $(SFILES) $(PREAMB)# 
 $(TEX) $(FLAGS) $(FILE);
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
# 
$(FMT): $(FILE) $(PREAMB)# 
 $(TEX) -ini -enc -jobname="$(NAME)" "&$(TEX)" mylatexformat.ltx """$(FILE)"""
# 
img: # 
 cd $(IMGF); make -j4
# 
.PHONY: clean cleantex cleansubfoldertex quick all img clean_img
clean: cleantex cleansubfoldertex clean_img
cleantex: # 
 -rm $(shell find $(NAME).* 
cleansubfoldertex: # 
 -cd $(TEXF); rm $(shell cd $(TEXF); find * 
clean_img: # 
 -cd $(IMGF); make clean
#


This Makefile has the default target quick, which will build a custom format if something in ./preamble/ or the main file has changed, call the Makefile for the images with the option -j4 which means that that Makefile can run 4 processes in parallel and build the PDF. It assumes that there is only one file with the file extension .tex which is the main file of the project.



The other targets are:




  • all: running TeX three times (and building the images if necessary)


  • clean: calling cleantex, cleansubfoldertex and clean_img


  • cleantex: delete every file having the same name as the main file, except those having the file extensions .tex, .sty and .bib


  • cleansubfoldertex: delete all files in ./tex/ except those containing tex in their names or file extension


  • clean_img: call the img Makefile with clean

The second Makefile should be placed in the ./img/ sub folder. It defines the rules to build the different image file types.



# User defined variables 
##########################################
# engine to use for everything that needs TeX
TEX = pdflatex
# flags for the TeX engine
TFLAG = -halt-on-error
# Python call
PY = python
# flags for python
PFLAG = 
# inkscape call (used for conversion of svg to pdf)
INK = inkscape
# flags for inkscape
IFLAG = --without-gui
# output option for inkscape
IOOPT = --export-pdf=
# relative path to included TeX-files containing preamble stuff
# circuit related preamble
CPREAMB = circuit_preamble.tex
# tikz related preamble
TPREAMB = tikz_preamble.tex
# shared preamble
MPREAMB = ct_preamble.tex
# a configuration file for python
PYCONF = custom_rcParams.py
# file extensions of different files
# for the tikz pictures
TIKZ = tikz
# for circuitikz pictures
CIRC = circuit
# for plots created by python
PYPL = plot.py
# for svg files
SVG = svg
##########################################
# 
# Automatically defined variables 
##########################################
CFILES = $(wildcard ./*.$(CIRC))
PFILES = $(wildcard ./*.$(PYPL))
SFILES = $(wildcard ./*.$(SVG))
TFILES = $(wildcard ./*.$(TIKZ))
COUT = $(CFILES:%.$(CIRC)=%.$(CIRC).pdf)
POUT = $(PFILES:%.$(PYPL)=%.$(PYPL).pdf)
SOUT = $(SFILES:%.$(SVG)=%.$(SVG).pdf)
TOUT = $(TFILES:%.$(TIKZ)=%.$(TIKZ).pdf)
##########################################
# 

all: circuit pypl svg tikz
circuit: $(COUT)
pypl: $(POUT)
svg: $(SOUT)
tikz: $(TOUT)

%.$(CIRC).pdf: %.$(CIRC) $(CPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(CPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(TIKZ).pdf: %.$(TIKZ) $(TPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(TPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(PYPL).pdf: %.$(PYPL) $(PYCONF)
 $(PY) $(PFLAG) $<

%.$(SVG).pdf: %.$(SVG)
 $(INK) $(IFLAG) $< $(IOOPT)"$<.pdf"

.PHONY: all circuit pypl svg tikz clean clean_tikz clean_circuit clean_pypl clean_svg

clean: clean_tikz clean_circuit clean_pypl clean_svg

clean_circuit:
 -rm $(COUT)
clean_tikz:
 -rm $(TOUT)
clean_pypl:
 -rm $(POUT)
clean_svg:
 -rm $(SOUT)


All the PDFs created by it have the naming scheme <filename>.<type>.pdf, so every TikZ picture which's source was named <filename>.tikz will create a PDF named <filename>.tikz.pdf. This way the clean target knows which PDFs can be removed and you can distinguish the files and use different includegraphics options based on the filename.



One important thing left to do is setting up graphicx to recognize those image files as PDFs. This is done with



usepackagegraphicx
DeclareGraphicsRule.circuit.pdfpdf*
DeclareGraphicsRule.tikz.pdfpdf*
DeclareGraphicsRule.plot.py.pdfpdf*
DeclareGraphicsRule.svg.pdfpdf*


Now you can include your TikZ picture with includegraphicsimg/<filename>.tikz.pdf.



Running make in the directory of your main file should build everything necessary for your finished PDF.



The overall approach keeps a clean structure with distinctive names for different types of content.



Possible speed gains



The above method builds really quick, as it parallelizes as much as possible (if you have many cores in your machine, you can change the -j4 option to more processes). Further speed gains could be achieved with building formats for the TikZ and circuitikz files.



Stuff to add



The project I used this on was a formulary for an exam, so I didn't need any bibliography or index. These should be added to the main Makefile if you need those (and shouldn't be too hard to do).






share|improve this answer






















  • Wow, many thanks for the detailed description of your way handling pictures with tikz. I will have a try in using some aspects :)
    – SRel
    Aug 15 at 19:03










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f446185%2fis-my-current-workflow-worth-using-or-idiotic%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
16
down vote



accepted










So as promised in the comments, here is my current setup for image-heavy documents using TikZ and similar (the below uses TikZ, circuitikz, includes SVGs, plots created with Python and possibly other images):



I maintain a shared preamble for all standalone TeX creations (like those of TikZ and circuitikz images) to sync stuff like font sizes and other stuff related to design. Additionally there is a shared preamble for every TikZ picture and a shared one for the circuitikz stuff.



For my latest work the shared preamble only includes



documentclass[tikz]standalone


the one dedicated to all ordinary TikZ pictures is in fact empty and the one for all the circuitikz images contains



usepackage[european,straightvoltages]circuitikz


For every image I can now create a file which contains only a begindocument and enddocument and the contents in between (additional preamble material for that file could be added here, too). circuitikz image code is saved as img/<filename>.circuit, ordinary TikZ pictures as img/<filename>.tikz.



The next thing to setup is a Makefile for the main document and another Makefile for all those images.



The main Makefile for my latest project looks like this:



# User defined variables 
##########################################
# engine to be used
TEX = pdflatex
# flags for that engine
FLAGS = -halt-on-error -8bit
# relative path to included TeX-files
TEXF = ./tex
# relative path to included TeX-files containing only preamble stuff
PREF = ./preamble
# relative path to img folder containing tikz and circuit files
IMGF = ./img
##########################################
# 
# Automatically defined variables 
##########################################
FILE = $(wildcard ./*.tex)
SFILES = $(wildcard $(TEXF)/*.tex)
PREAMB = $(wildcard $(PREF)/*.tex)
PREAMB += $(wildcard $(PREF)/*.sty)
PREAMB += $(wildcard ./*.sty)
NAME = $(FILE:%.tex=%)
OUT = $(NAME).pdf
FMT = $(NAME).fmt
##########################################
# 
# default target 
## the name 'quick' maybe misleading! 'all' might be faster if $(FILE) hasn't
## changed. 'quick' is for quickly running TeX assuming that you know what
## you're doing
quick: $(FMT) img
 $(TEX) $(FLAGS) -fmt="$(NAME)" $(FILE)
 #$(TEX) $(FLAGS) $(FILE);
# 
all: img $(OUT) #bib
$(OUT): $(FILE) $(SFILES) $(PREAMB)# 
 $(TEX) $(FLAGS) $(FILE);
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
# 
$(FMT): $(FILE) $(PREAMB)# 
 $(TEX) -ini -enc -jobname="$(NAME)" "&$(TEX)" mylatexformat.ltx """$(FILE)"""
# 
img: # 
 cd $(IMGF); make -j4
# 
.PHONY: clean cleantex cleansubfoldertex quick all img clean_img
clean: cleantex cleansubfoldertex clean_img
cleantex: # 
 -rm $(shell find $(NAME).* 
cleansubfoldertex: # 
 -cd $(TEXF); rm $(shell cd $(TEXF); find * 
clean_img: # 
 -cd $(IMGF); make clean
#


This Makefile has the default target quick, which will build a custom format if something in ./preamble/ or the main file has changed, call the Makefile for the images with the option -j4 which means that that Makefile can run 4 processes in parallel and build the PDF. It assumes that there is only one file with the file extension .tex which is the main file of the project.



The other targets are:




  • all: running TeX three times (and building the images if necessary)


  • clean: calling cleantex, cleansubfoldertex and clean_img


  • cleantex: delete every file having the same name as the main file, except those having the file extensions .tex, .sty and .bib


  • cleansubfoldertex: delete all files in ./tex/ except those containing tex in their names or file extension


  • clean_img: call the img Makefile with clean

The second Makefile should be placed in the ./img/ sub folder. It defines the rules to build the different image file types.



# User defined variables 
##########################################
# engine to use for everything that needs TeX
TEX = pdflatex
# flags for the TeX engine
TFLAG = -halt-on-error
# Python call
PY = python
# flags for python
PFLAG = 
# inkscape call (used for conversion of svg to pdf)
INK = inkscape
# flags for inkscape
IFLAG = --without-gui
# output option for inkscape
IOOPT = --export-pdf=
# relative path to included TeX-files containing preamble stuff
# circuit related preamble
CPREAMB = circuit_preamble.tex
# tikz related preamble
TPREAMB = tikz_preamble.tex
# shared preamble
MPREAMB = ct_preamble.tex
# a configuration file for python
PYCONF = custom_rcParams.py
# file extensions of different files
# for the tikz pictures
TIKZ = tikz
# for circuitikz pictures
CIRC = circuit
# for plots created by python
PYPL = plot.py
# for svg files
SVG = svg
##########################################
# 
# Automatically defined variables 
##########################################
CFILES = $(wildcard ./*.$(CIRC))
PFILES = $(wildcard ./*.$(PYPL))
SFILES = $(wildcard ./*.$(SVG))
TFILES = $(wildcard ./*.$(TIKZ))
COUT = $(CFILES:%.$(CIRC)=%.$(CIRC).pdf)
POUT = $(PFILES:%.$(PYPL)=%.$(PYPL).pdf)
SOUT = $(SFILES:%.$(SVG)=%.$(SVG).pdf)
TOUT = $(TFILES:%.$(TIKZ)=%.$(TIKZ).pdf)
##########################################
# 

all: circuit pypl svg tikz
circuit: $(COUT)
pypl: $(POUT)
svg: $(SOUT)
tikz: $(TOUT)

%.$(CIRC).pdf: %.$(CIRC) $(CPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(CPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(TIKZ).pdf: %.$(TIKZ) $(TPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(TPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(PYPL).pdf: %.$(PYPL) $(PYCONF)
 $(PY) $(PFLAG) $<

%.$(SVG).pdf: %.$(SVG)
 $(INK) $(IFLAG) $< $(IOOPT)"$<.pdf"

.PHONY: all circuit pypl svg tikz clean clean_tikz clean_circuit clean_pypl clean_svg

clean: clean_tikz clean_circuit clean_pypl clean_svg

clean_circuit:
 -rm $(COUT)
clean_tikz:
 -rm $(TOUT)
clean_pypl:
 -rm $(POUT)
clean_svg:
 -rm $(SOUT)


All the PDFs created by it have the naming scheme <filename>.<type>.pdf, so every TikZ picture which's source was named <filename>.tikz will create a PDF named <filename>.tikz.pdf. This way the clean target knows which PDFs can be removed and you can distinguish the files and use different includegraphics options based on the filename.



One important thing left to do is setting up graphicx to recognize those image files as PDFs. This is done with



usepackagegraphicx
DeclareGraphicsRule.circuit.pdfpdf*
DeclareGraphicsRule.tikz.pdfpdf*
DeclareGraphicsRule.plot.py.pdfpdf*
DeclareGraphicsRule.svg.pdfpdf*


Now you can include your TikZ picture with includegraphicsimg/<filename>.tikz.pdf.



Running make in the directory of your main file should build everything necessary for your finished PDF.



The overall approach keeps a clean structure with distinctive names for different types of content.



Possible speed gains



The above method builds really quick, as it parallelizes as much as possible (if you have many cores in your machine, you can change the -j4 option to more processes). Further speed gains could be achieved with building formats for the TikZ and circuitikz files.



Stuff to add



The project I used this on was a formulary for an exam, so I didn't need any bibliography or index. These should be added to the main Makefile if you need those (and shouldn't be too hard to do).






share|improve this answer






















  • Wow, many thanks for the detailed description of your way handling pictures with tikz. I will have a try in using some aspects :)
    – SRel
    Aug 15 at 19:03














up vote
16
down vote



accepted










So as promised in the comments, here is my current setup for image-heavy documents using TikZ and similar (the below uses TikZ, circuitikz, includes SVGs, plots created with Python and possibly other images):



I maintain a shared preamble for all standalone TeX creations (like those of TikZ and circuitikz images) to sync stuff like font sizes and other stuff related to design. Additionally there is a shared preamble for every TikZ picture and a shared one for the circuitikz stuff.



For my latest work the shared preamble only includes



documentclass[tikz]standalone


the one dedicated to all ordinary TikZ pictures is in fact empty and the one for all the circuitikz images contains



usepackage[european,straightvoltages]circuitikz


For every image I can now create a file which contains only a begindocument and enddocument and the contents in between (additional preamble material for that file could be added here, too). circuitikz image code is saved as img/<filename>.circuit, ordinary TikZ pictures as img/<filename>.tikz.



The next thing to setup is a Makefile for the main document and another Makefile for all those images.



The main Makefile for my latest project looks like this:



# User defined variables 
##########################################
# engine to be used
TEX = pdflatex
# flags for that engine
FLAGS = -halt-on-error -8bit
# relative path to included TeX-files
TEXF = ./tex
# relative path to included TeX-files containing only preamble stuff
PREF = ./preamble
# relative path to img folder containing tikz and circuit files
IMGF = ./img
##########################################
# 
# Automatically defined variables 
##########################################
FILE = $(wildcard ./*.tex)
SFILES = $(wildcard $(TEXF)/*.tex)
PREAMB = $(wildcard $(PREF)/*.tex)
PREAMB += $(wildcard $(PREF)/*.sty)
PREAMB += $(wildcard ./*.sty)
NAME = $(FILE:%.tex=%)
OUT = $(NAME).pdf
FMT = $(NAME).fmt
##########################################
# 
# default target 
## the name 'quick' maybe misleading! 'all' might be faster if $(FILE) hasn't
## changed. 'quick' is for quickly running TeX assuming that you know what
## you're doing
quick: $(FMT) img
 $(TEX) $(FLAGS) -fmt="$(NAME)" $(FILE)
 #$(TEX) $(FLAGS) $(FILE);
# 
all: img $(OUT) #bib
$(OUT): $(FILE) $(SFILES) $(PREAMB)# 
 $(TEX) $(FLAGS) $(FILE);
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
# 
$(FMT): $(FILE) $(PREAMB)# 
 $(TEX) -ini -enc -jobname="$(NAME)" "&$(TEX)" mylatexformat.ltx """$(FILE)"""
# 
img: # 
 cd $(IMGF); make -j4
# 
.PHONY: clean cleantex cleansubfoldertex quick all img clean_img
clean: cleantex cleansubfoldertex clean_img
cleantex: # 
 -rm $(shell find $(NAME).* 
cleansubfoldertex: # 
 -cd $(TEXF); rm $(shell cd $(TEXF); find * 
clean_img: # 
 -cd $(IMGF); make clean
#


This Makefile has the default target quick, which will build a custom format if something in ./preamble/ or the main file has changed, call the Makefile for the images with the option -j4 which means that that Makefile can run 4 processes in parallel and build the PDF. It assumes that there is only one file with the file extension .tex which is the main file of the project.



The other targets are:




  • all: running TeX three times (and building the images if necessary)


  • clean: calling cleantex, cleansubfoldertex and clean_img


  • cleantex: delete every file having the same name as the main file, except those having the file extensions .tex, .sty and .bib


  • cleansubfoldertex: delete all files in ./tex/ except those containing tex in their names or file extension


  • clean_img: call the img Makefile with clean

The second Makefile should be placed in the ./img/ sub folder. It defines the rules to build the different image file types.



# User defined variables 
##########################################
# engine to use for everything that needs TeX
TEX = pdflatex
# flags for the TeX engine
TFLAG = -halt-on-error
# Python call
PY = python
# flags for python
PFLAG = 
# inkscape call (used for conversion of svg to pdf)
INK = inkscape
# flags for inkscape
IFLAG = --without-gui
# output option for inkscape
IOOPT = --export-pdf=
# relative path to included TeX-files containing preamble stuff
# circuit related preamble
CPREAMB = circuit_preamble.tex
# tikz related preamble
TPREAMB = tikz_preamble.tex
# shared preamble
MPREAMB = ct_preamble.tex
# a configuration file for python
PYCONF = custom_rcParams.py
# file extensions of different files
# for the tikz pictures
TIKZ = tikz
# for circuitikz pictures
CIRC = circuit
# for plots created by python
PYPL = plot.py
# for svg files
SVG = svg
##########################################
# 
# Automatically defined variables 
##########################################
CFILES = $(wildcard ./*.$(CIRC))
PFILES = $(wildcard ./*.$(PYPL))
SFILES = $(wildcard ./*.$(SVG))
TFILES = $(wildcard ./*.$(TIKZ))
COUT = $(CFILES:%.$(CIRC)=%.$(CIRC).pdf)
POUT = $(PFILES:%.$(PYPL)=%.$(PYPL).pdf)
SOUT = $(SFILES:%.$(SVG)=%.$(SVG).pdf)
TOUT = $(TFILES:%.$(TIKZ)=%.$(TIKZ).pdf)
##########################################
# 

all: circuit pypl svg tikz
circuit: $(COUT)
pypl: $(POUT)
svg: $(SOUT)
tikz: $(TOUT)

%.$(CIRC).pdf: %.$(CIRC) $(CPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(CPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(TIKZ).pdf: %.$(TIKZ) $(TPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(TPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(PYPL).pdf: %.$(PYPL) $(PYCONF)
 $(PY) $(PFLAG) $<

%.$(SVG).pdf: %.$(SVG)
 $(INK) $(IFLAG) $< $(IOOPT)"$<.pdf"

.PHONY: all circuit pypl svg tikz clean clean_tikz clean_circuit clean_pypl clean_svg

clean: clean_tikz clean_circuit clean_pypl clean_svg

clean_circuit:
 -rm $(COUT)
clean_tikz:
 -rm $(TOUT)
clean_pypl:
 -rm $(POUT)
clean_svg:
 -rm $(SOUT)


All the PDFs created by it have the naming scheme <filename>.<type>.pdf, so every TikZ picture which's source was named <filename>.tikz will create a PDF named <filename>.tikz.pdf. This way the clean target knows which PDFs can be removed and you can distinguish the files and use different includegraphics options based on the filename.



One important thing left to do is setting up graphicx to recognize those image files as PDFs. This is done with



usepackagegraphicx
DeclareGraphicsRule.circuit.pdfpdf*
DeclareGraphicsRule.tikz.pdfpdf*
DeclareGraphicsRule.plot.py.pdfpdf*
DeclareGraphicsRule.svg.pdfpdf*


Now you can include your TikZ picture with includegraphicsimg/<filename>.tikz.pdf.



Running make in the directory of your main file should build everything necessary for your finished PDF.



The overall approach keeps a clean structure with distinctive names for different types of content.



Possible speed gains



The above method builds really quick, as it parallelizes as much as possible (if you have many cores in your machine, you can change the -j4 option to more processes). Further speed gains could be achieved with building formats for the TikZ and circuitikz files.



Stuff to add



The project I used this on was a formulary for an exam, so I didn't need any bibliography or index. These should be added to the main Makefile if you need those (and shouldn't be too hard to do).






share|improve this answer






















  • Wow, many thanks for the detailed description of your way handling pictures with tikz. I will have a try in using some aspects :)
    – SRel
    Aug 15 at 19:03












up vote
16
down vote



accepted







up vote
16
down vote



accepted






So as promised in the comments, here is my current setup for image-heavy documents using TikZ and similar (the below uses TikZ, circuitikz, includes SVGs, plots created with Python and possibly other images):



I maintain a shared preamble for all standalone TeX creations (like those of TikZ and circuitikz images) to sync stuff like font sizes and other stuff related to design. Additionally there is a shared preamble for every TikZ picture and a shared one for the circuitikz stuff.



For my latest work the shared preamble only includes



documentclass[tikz]standalone


the one dedicated to all ordinary TikZ pictures is in fact empty and the one for all the circuitikz images contains



usepackage[european,straightvoltages]circuitikz


For every image I can now create a file which contains only a begindocument and enddocument and the contents in between (additional preamble material for that file could be added here, too). circuitikz image code is saved as img/<filename>.circuit, ordinary TikZ pictures as img/<filename>.tikz.



The next thing to setup is a Makefile for the main document and another Makefile for all those images.



The main Makefile for my latest project looks like this:



# User defined variables 
##########################################
# engine to be used
TEX = pdflatex
# flags for that engine
FLAGS = -halt-on-error -8bit
# relative path to included TeX-files
TEXF = ./tex
# relative path to included TeX-files containing only preamble stuff
PREF = ./preamble
# relative path to img folder containing tikz and circuit files
IMGF = ./img
##########################################
# 
# Automatically defined variables 
##########################################
FILE = $(wildcard ./*.tex)
SFILES = $(wildcard $(TEXF)/*.tex)
PREAMB = $(wildcard $(PREF)/*.tex)
PREAMB += $(wildcard $(PREF)/*.sty)
PREAMB += $(wildcard ./*.sty)
NAME = $(FILE:%.tex=%)
OUT = $(NAME).pdf
FMT = $(NAME).fmt
##########################################
# 
# default target 
## the name 'quick' maybe misleading! 'all' might be faster if $(FILE) hasn't
## changed. 'quick' is for quickly running TeX assuming that you know what
## you're doing
quick: $(FMT) img
 $(TEX) $(FLAGS) -fmt="$(NAME)" $(FILE)
 #$(TEX) $(FLAGS) $(FILE);
# 
all: img $(OUT) #bib
$(OUT): $(FILE) $(SFILES) $(PREAMB)# 
 $(TEX) $(FLAGS) $(FILE);
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
# 
$(FMT): $(FILE) $(PREAMB)# 
 $(TEX) -ini -enc -jobname="$(NAME)" "&$(TEX)" mylatexformat.ltx """$(FILE)"""
# 
img: # 
 cd $(IMGF); make -j4
# 
.PHONY: clean cleantex cleansubfoldertex quick all img clean_img
clean: cleantex cleansubfoldertex clean_img
cleantex: # 
 -rm $(shell find $(NAME).* 
cleansubfoldertex: # 
 -cd $(TEXF); rm $(shell cd $(TEXF); find * 
clean_img: # 
 -cd $(IMGF); make clean
#


This Makefile has the default target quick, which will build a custom format if something in ./preamble/ or the main file has changed, call the Makefile for the images with the option -j4 which means that that Makefile can run 4 processes in parallel and build the PDF. It assumes that there is only one file with the file extension .tex which is the main file of the project.



The other targets are:




  • all: running TeX three times (and building the images if necessary)


  • clean: calling cleantex, cleansubfoldertex and clean_img


  • cleantex: delete every file having the same name as the main file, except those having the file extensions .tex, .sty and .bib


  • cleansubfoldertex: delete all files in ./tex/ except those containing tex in their names or file extension


  • clean_img: call the img Makefile with clean

The second Makefile should be placed in the ./img/ sub folder. It defines the rules to build the different image file types.



# User defined variables 
##########################################
# engine to use for everything that needs TeX
TEX = pdflatex
# flags for the TeX engine
TFLAG = -halt-on-error
# Python call
PY = python
# flags for python
PFLAG = 
# inkscape call (used for conversion of svg to pdf)
INK = inkscape
# flags for inkscape
IFLAG = --without-gui
# output option for inkscape
IOOPT = --export-pdf=
# relative path to included TeX-files containing preamble stuff
# circuit related preamble
CPREAMB = circuit_preamble.tex
# tikz related preamble
TPREAMB = tikz_preamble.tex
# shared preamble
MPREAMB = ct_preamble.tex
# a configuration file for python
PYCONF = custom_rcParams.py
# file extensions of different files
# for the tikz pictures
TIKZ = tikz
# for circuitikz pictures
CIRC = circuit
# for plots created by python
PYPL = plot.py
# for svg files
SVG = svg
##########################################
# 
# Automatically defined variables 
##########################################
CFILES = $(wildcard ./*.$(CIRC))
PFILES = $(wildcard ./*.$(PYPL))
SFILES = $(wildcard ./*.$(SVG))
TFILES = $(wildcard ./*.$(TIKZ))
COUT = $(CFILES:%.$(CIRC)=%.$(CIRC).pdf)
POUT = $(PFILES:%.$(PYPL)=%.$(PYPL).pdf)
SOUT = $(SFILES:%.$(SVG)=%.$(SVG).pdf)
TOUT = $(TFILES:%.$(TIKZ)=%.$(TIKZ).pdf)
##########################################
# 

all: circuit pypl svg tikz
circuit: $(COUT)
pypl: $(POUT)
svg: $(SOUT)
tikz: $(TOUT)

%.$(CIRC).pdf: %.$(CIRC) $(CPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(CPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(TIKZ).pdf: %.$(TIKZ) $(TPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(TPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(PYPL).pdf: %.$(PYPL) $(PYCONF)
 $(PY) $(PFLAG) $<

%.$(SVG).pdf: %.$(SVG)
 $(INK) $(IFLAG) $< $(IOOPT)"$<.pdf"

.PHONY: all circuit pypl svg tikz clean clean_tikz clean_circuit clean_pypl clean_svg

clean: clean_tikz clean_circuit clean_pypl clean_svg

clean_circuit:
 -rm $(COUT)
clean_tikz:
 -rm $(TOUT)
clean_pypl:
 -rm $(POUT)
clean_svg:
 -rm $(SOUT)


All the PDFs created by it have the naming scheme <filename>.<type>.pdf, so every TikZ picture which's source was named <filename>.tikz will create a PDF named <filename>.tikz.pdf. This way the clean target knows which PDFs can be removed and you can distinguish the files and use different includegraphics options based on the filename.



One important thing left to do is setting up graphicx to recognize those image files as PDFs. This is done with



usepackagegraphicx
DeclareGraphicsRule.circuit.pdfpdf*
DeclareGraphicsRule.tikz.pdfpdf*
DeclareGraphicsRule.plot.py.pdfpdf*
DeclareGraphicsRule.svg.pdfpdf*


Now you can include your TikZ picture with includegraphicsimg/<filename>.tikz.pdf.



Running make in the directory of your main file should build everything necessary for your finished PDF.



The overall approach keeps a clean structure with distinctive names for different types of content.



Possible speed gains



The above method builds really quick, as it parallelizes as much as possible (if you have many cores in your machine, you can change the -j4 option to more processes). Further speed gains could be achieved with building formats for the TikZ and circuitikz files.



Stuff to add



The project I used this on was a formulary for an exam, so I didn't need any bibliography or index. These should be added to the main Makefile if you need those (and shouldn't be too hard to do).






share|improve this answer














So as promised in the comments, here is my current setup for image-heavy documents using TikZ and similar (the below uses TikZ, circuitikz, includes SVGs, plots created with Python and possibly other images):



I maintain a shared preamble for all standalone TeX creations (like those of TikZ and circuitikz images) to sync stuff like font sizes and other stuff related to design. Additionally there is a shared preamble for every TikZ picture and a shared one for the circuitikz stuff.



For my latest work the shared preamble only includes



documentclass[tikz]standalone


the one dedicated to all ordinary TikZ pictures is in fact empty and the one for all the circuitikz images contains



usepackage[european,straightvoltages]circuitikz


For every image I can now create a file which contains only a begindocument and enddocument and the contents in between (additional preamble material for that file could be added here, too). circuitikz image code is saved as img/<filename>.circuit, ordinary TikZ pictures as img/<filename>.tikz.



The next thing to setup is a Makefile for the main document and another Makefile for all those images.



The main Makefile for my latest project looks like this:



# User defined variables 
##########################################
# engine to be used
TEX = pdflatex
# flags for that engine
FLAGS = -halt-on-error -8bit
# relative path to included TeX-files
TEXF = ./tex
# relative path to included TeX-files containing only preamble stuff
PREF = ./preamble
# relative path to img folder containing tikz and circuit files
IMGF = ./img
##########################################
# 
# Automatically defined variables 
##########################################
FILE = $(wildcard ./*.tex)
SFILES = $(wildcard $(TEXF)/*.tex)
PREAMB = $(wildcard $(PREF)/*.tex)
PREAMB += $(wildcard $(PREF)/*.sty)
PREAMB += $(wildcard ./*.sty)
NAME = $(FILE:%.tex=%)
OUT = $(NAME).pdf
FMT = $(NAME).fmt
##########################################
# 
# default target 
## the name 'quick' maybe misleading! 'all' might be faster if $(FILE) hasn't
## changed. 'quick' is for quickly running TeX assuming that you know what
## you're doing
quick: $(FMT) img
 $(TEX) $(FLAGS) -fmt="$(NAME)" $(FILE)
 #$(TEX) $(FLAGS) $(FILE);
# 
all: img $(OUT) #bib
$(OUT): $(FILE) $(SFILES) $(PREAMB)# 
 $(TEX) $(FLAGS) $(FILE);
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
 $(TEX) $(FLAGS) $(NAME).tex > /dev/null;
# 
$(FMT): $(FILE) $(PREAMB)# 
 $(TEX) -ini -enc -jobname="$(NAME)" "&$(TEX)" mylatexformat.ltx """$(FILE)"""
# 
img: # 
 cd $(IMGF); make -j4
# 
.PHONY: clean cleantex cleansubfoldertex quick all img clean_img
clean: cleantex cleansubfoldertex clean_img
cleantex: # 
 -rm $(shell find $(NAME).* 
cleansubfoldertex: # 
 -cd $(TEXF); rm $(shell cd $(TEXF); find * 
clean_img: # 
 -cd $(IMGF); make clean
#


This Makefile has the default target quick, which will build a custom format if something in ./preamble/ or the main file has changed, call the Makefile for the images with the option -j4 which means that that Makefile can run 4 processes in parallel and build the PDF. It assumes that there is only one file with the file extension .tex which is the main file of the project.



The other targets are:




  • all: running TeX three times (and building the images if necessary)


  • clean: calling cleantex, cleansubfoldertex and clean_img


  • cleantex: delete every file having the same name as the main file, except those having the file extensions .tex, .sty and .bib


  • cleansubfoldertex: delete all files in ./tex/ except those containing tex in their names or file extension


  • clean_img: call the img Makefile with clean

The second Makefile should be placed in the ./img/ sub folder. It defines the rules to build the different image file types.



# User defined variables 
##########################################
# engine to use for everything that needs TeX
TEX = pdflatex
# flags for the TeX engine
TFLAG = -halt-on-error
# Python call
PY = python
# flags for python
PFLAG = 
# inkscape call (used for conversion of svg to pdf)
INK = inkscape
# flags for inkscape
IFLAG = --without-gui
# output option for inkscape
IOOPT = --export-pdf=
# relative path to included TeX-files containing preamble stuff
# circuit related preamble
CPREAMB = circuit_preamble.tex
# tikz related preamble
TPREAMB = tikz_preamble.tex
# shared preamble
MPREAMB = ct_preamble.tex
# a configuration file for python
PYCONF = custom_rcParams.py
# file extensions of different files
# for the tikz pictures
TIKZ = tikz
# for circuitikz pictures
CIRC = circuit
# for plots created by python
PYPL = plot.py
# for svg files
SVG = svg
##########################################
# 
# Automatically defined variables 
##########################################
CFILES = $(wildcard ./*.$(CIRC))
PFILES = $(wildcard ./*.$(PYPL))
SFILES = $(wildcard ./*.$(SVG))
TFILES = $(wildcard ./*.$(TIKZ))
COUT = $(CFILES:%.$(CIRC)=%.$(CIRC).pdf)
POUT = $(PFILES:%.$(PYPL)=%.$(PYPL).pdf)
SOUT = $(SFILES:%.$(SVG)=%.$(SVG).pdf)
TOUT = $(TFILES:%.$(TIKZ)=%.$(TIKZ).pdf)
##########################################
# 

all: circuit pypl svg tikz
circuit: $(COUT)
pypl: $(POUT)
svg: $(SOUT)
tikz: $(TOUT)

%.$(CIRC).pdf: %.$(CIRC) $(CPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(CPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(TIKZ).pdf: %.$(TIKZ) $(TPREAMB) $(MPREAMB)
 $(TEX) $(TFLAG) -jobname="$<" "input$(MPREAMB)input$(TPREAMB)input$<"
 -rm $<.aux
 -rm $<.log

%.$(PYPL).pdf: %.$(PYPL) $(PYCONF)
 $(PY) $(PFLAG) $<

%.$(SVG).pdf: %.$(SVG)
 $(INK) $(IFLAG) $< $(IOOPT)"$<.pdf"

.PHONY: all circuit pypl svg tikz clean clean_tikz clean_circuit clean_pypl clean_svg

clean: clean_tikz clean_circuit clean_pypl clean_svg

clean_circuit:
 -rm $(COUT)
clean_tikz:
 -rm $(TOUT)
clean_pypl:
 -rm $(POUT)
clean_svg:
 -rm $(SOUT)


All the PDFs created by it have the naming scheme <filename>.<type>.pdf, so every TikZ picture which's source was named <filename>.tikz will create a PDF named <filename>.tikz.pdf. This way the clean target knows which PDFs can be removed and you can distinguish the files and use different includegraphics options based on the filename.



One important thing left to do is setting up graphicx to recognize those image files as PDFs. This is done with



usepackagegraphicx
DeclareGraphicsRule.circuit.pdfpdf*
DeclareGraphicsRule.tikz.pdfpdf*
DeclareGraphicsRule.plot.py.pdfpdf*
DeclareGraphicsRule.svg.pdfpdf*


Now you can include your TikZ picture with includegraphicsimg/<filename>.tikz.pdf.



Running make in the directory of your main file should build everything necessary for your finished PDF.



The overall approach keeps a clean structure with distinctive names for different types of content.



Possible speed gains



The above method builds really quick, as it parallelizes as much as possible (if you have many cores in your machine, you can change the -j4 option to more processes). Further speed gains could be achieved with building formats for the TikZ and circuitikz files.



Stuff to add



The project I used this on was a formulary for an exam, so I didn't need any bibliography or index. These should be added to the main Makefile if you need those (and shouldn't be too hard to do).







share|improve this answer














share|improve this answer



share|improve this answer








edited Aug 15 at 21:54

























answered Aug 15 at 18:33









Skillmon

17.4k11535




17.4k11535











  • Wow, many thanks for the detailed description of your way handling pictures with tikz. I will have a try in using some aspects :)
    – SRel
    Aug 15 at 19:03
















  • Wow, many thanks for the detailed description of your way handling pictures with tikz. I will have a try in using some aspects :)
    – SRel
    Aug 15 at 19:03















Wow, many thanks for the detailed description of your way handling pictures with tikz. I will have a try in using some aspects :)
– SRel
Aug 15 at 19:03




Wow, many thanks for the detailed description of your way handling pictures with tikz. I will have a try in using some aspects :)
– SRel
Aug 15 at 19:03

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f446185%2fis-my-current-workflow-worth-using-or-idiotic%23new-answer', 'question_page');

);

Post as a guest
































































Comments

Post a Comment

Popular posts from this blog

What does second last employer means? [closed]

Image
Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote -3 down vote favorite Say, for example I have worked in the following companies, Company A => 2010 - 2011 Company B => 2011 - 2012 Company C => 2012 - Till Date Company D => Have offer Now assume Company D is asking to submit documents from my second last employer. So from the list of companies given, which company would be qualified as second last employer? software-industry employer share | improve this question asked Aug 10 '14 at 5:16 Rajaprabhu Aravindasamy 559 1 6 13 closed as off-topic by Jim G., jmort253 ♦ Aug 11 '14 at 1:58 This question appears to be off-topic. The users who voted to close gave this specific reason: "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address...
Read more

List of Gilmore Girls characters

Image
The season three cast—(Back row): Lane, Michel, Paris, Emily, Richard, Sookie, Miss Patty, Kirk; Front row: Jess, Luke, Lorelai, Rory, Dean This is a list of characters for the comedy-drama television series Gilmore Girls . Contents 1 Main characters 1.1 Lorelai Gilmore 1.2 Rory Gilmore 1.3 Sookie St. James 1.4 Lane Kim 1.5 Michel Gerard 1.6 Luke Danes 1.7 Emily Gilmore 1.8 Richard Gilmore 1.9 Paris Geller 1.10 Dean Forester 1.11 Jess Mariano 1.12 Kirk Gleason 1.13 Jason Stiles 1.14 Logan Huntzberger 2 Major recurring characters 2.1 Christopher Hayden 2.2 Jackson Belleville 2.3 Mrs. Kim 2.4 Tristin DuGray 2.5 Max Medina 2.6 Taylor Doose 2.7 Dave Rygalski 2.8 Marty 3 Recurring characters 3.1 Stars Hollow 3.2 Chilton 3.3 Yale 3.4 Other 4 Notable guest stars 5 Unseen characters 6 Notes 7 References Main characters Actor Character Appearances Season 1 Season 2 Season 3 Season 4 Season 5 Season 6 Season 7 A Year in the Life Lauren Graham Lorelai Gilmore...
Read more

Confectionery

Image
Prepared foods made with a lot of sugar or other cabohydrates "Sweetmeat" redirects here. For the racehorse, see Sweetmeat (horse). Not to be confused with Sweetbread. This Kransekake is a traditional Scandinavian baker's confection. Confectionery is the art of making confections , which are food items that are rich in sugar and carbohydrates. Exact definitions are difficult. [1] In general, though, confectionery is divided into two broad and somewhat overlapping categories, bakers' confections and sugar confections. [2] Bakers' confectionery, also called flour confections , includes principally sweet pastries, cakes, and similar baked goods. Sugar confectionery includes candies ( sweets in British English), candied nuts, chocolates, chewing gum, bubble gum, pastillage, and other confections that are made primarily of sugar. In some cases, chocolate confections (confections made of chocolate) are treated as a separate category, as are sugar-free versions of ...
Read more