-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add cookingsymbols package #48
base: master
Are you sure you want to change the base?
Conversation
I can't figure out why the test doesn't build - the only error I get is |
b219953
to
393207f
Compare
393207f
to
2836733
Compare
2836733
to
fdcd0ea
Compare
When rebased ontop of #89, we get more details:
I suspect this is what happens:
This fails because @solsjo any suggestion? |
fdcd0ea
to
e6f9f9f
Compare
@Kernald, sorry, missed this comment. No, I'm afraid I don't much information to add. I did encounter a similar problem, at that time it was related to latex not finding the fontmaps files (*.map) need to produce the font, IIRC. For me that was related to refactoring messing with the rules and kpathsea lookup. So it should work in the standard case? unless cockingsymbols depend on some package containing some separate font maps? |
@Kernald, TL;DRI managed to reproduce your error, and I've spent some time trying to figure it out. reproducing the error after removing the tool_wrapperWhen trying to reproduce the error I noticed that because of the refactoring (not mimicking the TDS structure + latex install structure, but making use of environment variables) we need to do so additional changes.
to find web2c files from scripts, and
To make the scripts find kpsewhich (some of the scripts execute in a temp-folder instead, but beacuse kpsewhich directory is added to PATH with relative path it only works from the bazel entrypoint) we need to add the path to kpsewhich in the scripts, which themselves appends to the PATH to find their own scripts directory. The hack above simply follows on that. We should probably implement a more solid solution than this. |
I'm honestly not sure about any of that - I never dealt with those files before, you clearly have more LaTeX knowledge than I do :-) The only thing that I know is that I didn't have to do any manual work to use |
Hmm, I read that pdflatex and XeTex does generate e.g. generate tfm files on the fly but not lualatex. Do you remember which program you used? |
I suspect pdflatex, but can't say for certain. Looking for files named
Something did generate those |
No description provided.