I was running:
pretext build print
where "print" is a valid target in the project file that makes a PDF.
The LaTeX compilation choked on missing play-button.png, so I ran:
pretext devscript -p publication/publication.xml -c play-button src/orcca.ptx
and then tried again:
pretext build print
I got an inch further. This time the LaTeX compilation choked on
missing QR code image files. So I tried:
pretext generate qr-codes
but "qr-codes" is not a valid "pretext generate" command. (You wrote
this is available in the CLI; what makes the QR codes then if not
pretext generate?)
So then I did:
pretext devscript -p publication/publication.xml -c qr-code src/orcca.ptx
and tried again:
pretext build print
And it built successfully.
For both things, the pretext devscript is placing files in the
project's generated folder. Either in:
generated-assets/play-button/
or in:
generated-assets/qr-code/
Then the generated-assets folder is copied to the temporary folder as
"generated/". Then the .tex file is looking for images to insert from
folders generated/play-button/ and from generated/qr-code/.
Ideally if you run:
pretext build print
it would be good if it recognized the project will need the QR-codes
and the play-button image. And then just make them one step ahead of
building the PDF when they are needed. With the play-button, it's
super fast and harmless to overwrite what was already there. With the
QR-codes, also harmless to overwrite, but maybe can take up time? So
maybe good to not automatically remake them? I don't know.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/pretext-dev/76eea14b-9662-45c5-94b0-edccf2022be5n%40googlegroups.com.