Open dmitrizagidulin opened 7 years ago
pillarPostExport.sh
should definitely be ignored as it's generated each time pillar export
gets called.
About sbabook.cls
not being found, I'm not sure. The LaTeX compile happens from inside the book-result
directory, so you should check that it's accessible from there, instead of from the git clone. In any case I'd try a clean (removing book-result
) build before anything else.
I keep seeing references to ./root/support/latex/sbabook/sbabook.cls
in the errors. Where's the root
part coming from
Those are links that are created from the pillarPostExport.sh
script. They should be created in each book-result/$CHAPTER/
directory and pointing back up to book-result
.
@cdlm - If you check out a fresh copy of this repo, run the download script, does compiling work for you? (And if so, what are the environmental differences? What OS, etc?) I can't get it to work (and another person at Camp Smalltalk this weekend couldn't get it to work either).
On my machine download.sh
gets a VM that's too old to run on OS X 10.12 so it doesn't even build the Pillar image… I'll try to get the build to work by downloading a working VM/Pillar image myself, but cannot guarantee when :(
Thanks, very much appreciate it.
Our installation / Pillar setup instructions no longer seem to work. I went to set up Updated Pharo by Example on a new laptop, and couldn't get it to compile either the whole book or individual chapters.
I took the following steps:
pdftex
was accessible on my current path, etc)./download.sh
, it ran no problem, installed Pillar on Pharo 4.0, etc../compile.sh
or./compileBook.sh
doesn't work.Running
./compile.sh
by itself gives the following error:Running
./compileBook.sh
gives the following error:I'm not sure what is causing the
File 'support/latex/sbabook/sbabook.cls' not found.
error, because the file is there:It looks like something has changed as of the Migrate to the sbabook class commit. How do I install / compile things now?
(Oh, I also noticed that
/pillarPostExport.sh
is in the.gitignore
file. That doesn't seem right; should it be ignored?)