Re: Windows Cross build fails because pspp executable is required during build

[John Darrington]

We're now using the pspp binary to generate its own documentation.  So
the documentation cannot work when cross building.  I can think of 3
things we could do:

1.  Like Fritz suggests, ship the generated files in the tarball.
2.  Don't generate any documentation when cross building.
3.  For cross builds, also build a native binary and generate the
    documentation using that.

All of these solutions have their own (de)merits.

J'



On Tue, Nov 17, 2020 at 07:20:22AM +0100, Friedrich Beckmann wrote:
     Hi,
     
     i completely forgot that the windows build is a cross build, i.e. pspp.exe 
can of course not be executed on the build machine. The current build process 
fails with
     
     ====
     (cd ./examples \
              && 
/home/pspp/pspp-master-20201117/pspp-1.5.2-gc04cd4/src/ui/terminal/pspp.exe 
../doc/examples/autorecode.sps -o - -O format=spv) > 
doc/examples/autorecode.spv.tmp
     /bin/sh: line 1: 
/home/pspp/pspp-master-20201117/pspp-1.5.2-gc04cd4/src/ui/terminal/pspp.exe: 
cannot execute binary file: Fehler im Format der Programmdatei
     make[2]: *** [Makefile:14217: doc/examples/autorecode.spv] Error 126
     make[2]: Leaving directory 
'/home/pspp/pspp-master-20201117/pspp-1.5.2-gc04cd4'
     make[1]: *** [Makefile:12303: all-recursive] Error 1
     make[1]: Leaving directory 
'/home/pspp/pspp-master-20201117/pspp-1.5.2-gc04cd4'
     make: *** [Makefile:6401: all] Error 2
     Uncaught exception from user code:
        system 'Mingw32-make'  failed: 512 at ./buildpspp4windows.pl line 568, 
<FILE> line 937.
        main::ProcMake() called at ./buildpspp4windows.pl line 369
        main::ProcGeneratePSPP("w32", "Debug") called at ./buildpspp4windows.pl 
line 124
     program finished with exit code 2
     elapsedTime=419.754343
     
     ===
     
     While executing a simple „make“ 
     
     
https://github.com/fredowski/pspp-buildbot/blob/master/win/buildpspp4windows.pl#L568
     
     Any ideas how this can be avoided? Aren’t this examples for the 
documentation, i.e. could that be part of the doc target?
     
     http://caeis.etech.fh-augsburg.de:8010/#/builders/7/builds/95
     
     Fritz