99
edits
Windows Installer: Difference between revisions
→If things go wrong
| Line 93: | Line 93: | ||
* The configuration will be for the target system, not your own. In particular, if you have not installed all of the packages that MXE-octave installs, then your configuration will be different. However, some configuration variables will differ even if you have the same packages, and some compiler features may be available on the host system that are not available in cross-compile mode. | * The configuration will be for the target system, not your own. In particular, if you have not installed all of the packages that MXE-octave installs, then your configuration will be different. However, some configuration variables will differ even if you have the same packages, and some compiler features may be available on the host system that are not available in cross-compile mode. | ||
* A possible causes for build failure is having files in your local source or build directory that are not listed in the module.mk files; these are not copied into the dist archive. | * A possible causes for build failure is having files in your local source or build directory that are not listed in the module.mk files; these are not copied into the dist archive. | ||
* (philip) On my core i5 desktop system with a fast SSD, mxe-octave usually fails when building libmng, suspectedly because of a race condition related to disk I/O. I found that I can get past this by specifying "make nsis-installer JOBS=1", if required repeatedly (sometimes 5 or 6 times), interrupting the build in the next step/dependency once libmng has been built fine, and restaring with "make nsis-installer JOBS=<higher number>". AFAICS it is only libmng that suffers from this issue. | |||
==Installing requirements of MXE Octave== | ==Installing requirements of MXE Octave== | ||