Re: mxe-octave change

[Philip Nienhuis]

John W. Eaton wrote
> I moved the functionality of the mk-dist script in the mxe-octave
> build system into the Makefile and removed the mk-dist script.
> 
> Now you just need to run
> 
>     make nsis-installer
> 
> or
> 
>     make tar-dist
> 
> to build everything and generate an installer or tar file containing
> all the files.
> 
> Currently this will build the stable-octave target.  If you have a
> previous build that used the octave target, then I think you'll end up
> with both versions included in the tar file or installer so some care
> is needed to avoid having unintended files in the binary distribution.
> Eventually I hope we can eliminate that problem so that the files that
> are included are predictable without having to run "make clean" first
> before building the installer (and everything else).

I don't know if it's caused by these changes, but nowadays I see that 

"make -j4 nsis-installer"

spawns 4 simultaneous package download/build jobs, rather than doing the
download/build steps one by one and invoking all CPU cores to that package
build.
Previously there was a little bit of slowdown when one CPU core was used for
downloading and configure, followed by all 4 during the actual build step
for each package (usually the longest step when building a package).
(The longest step was always zipping in the end (for either zip or
installer; both ~25 mins), as that seemingly can invoke just one core.)

The effect is that it now takes much longer -at least for me- to make
mxe-octave builds.  
When restarting an mxe-octave build with the "-j4" flag, the CPU monitor
shows that just one CPU core is invoked to build octave for the entire build
step; same for other packages (tested by removing entries in
mxe-octave/log).

Philip




--
View this message in context: 
http://octave.1599824.n4.nabble.com/mxe-octave-change-tp4661119p4661410.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.