I discovered that I was looking at hardcoded output from tutorial.tex, not output from the example conversion. Oops.
On Sat, Oct 24, 2020 at 1:37 PM Ben Pfaff <b...@cs.stanford.edu> wrote: > > I fixed the build now. > > The examples don't look very good in the PDF version of the manual. > They overflow the right margin and they get cut off at the bottom of > the page. > > On Thu, Oct 15, 2020 at 10:55 AM Ben Pfaff <b...@cs.stanford.edu> wrote: > > > > On Thu, Oct 15, 2020 at 10:38 AM John Darrington > > <j...@darrington.wattle.id.au> wrote: > > > > > > 41;344;0cOn Thu, Oct 15, 2020 at 09:18:35AM -0700, Ben Pfaff wrote: > > > Hmm. It's worse than that, since now it's impossible to build a > > > source > > > distribution from Git without first building the PSPP binary. > > > > > > That much is true. > > > > > > And I think that cross-compiling from Git is impossible now? > > > Since you can't build the manual unless you first build and run the > > > binary. > > > > > > Yes and no. One must first build a native binary, at least for the > > > terminal version of PSPP, because that is used to generate the > > > example outputs. Once you've done that, then you can do a cross build. > > > > > > However, it's going to get worse :/ because I have plans to auto > > > generate > > > screenshots for the manual. These will depend upon a nativly built > > > and installed PSPPIRE. So when that happens, then yes, almost everything > > > will have to be built, before the manual can be built. > > > > > > I think I need to discard the idea of having separate "source" and > > > "binary" > > > nightly builds. > > > > > > In my opinion, it would still be useful to have a regular build-bot > > > to check that cross-builds can be performed from the tarball, even if > > > that tarball can only be generated after building a native binary > > > > OK. I think it's a big benefit for our users to improve the manual, so I'll > > work to deal with this in the autobuilder.
