Mercurial > mxe-octave

comparison README @ 4380:ecad9fe83f88

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
README: Fix typo.
author John W. Eaton <jwe@octave.org>
date Wed, 12 Apr 2017 16:18:55 -0400
parents 886056e979a4
children
comparison
equal deleted inserted replaced
4379:886056e979a4 4380:ecad9fe83f88
6 for Windows. At the time, the MXE developers did not seem interested 6 for Windows. At the time, the MXE developers did not seem interested
7 in modifying MXE to build shared libraries (. Since then, MXE has been modified 7 in modifying MXE to build shared libraries (. Since then, MXE has been modified
8 8
9 As stated here: 9 As stated here:
10 http://lists.defectivebydesign.org/archive/html/mingw-cross-env-list/2013-10/msg00006.html 10 http://lists.defectivebydesign.org/archive/html/mingw-cross-env-list/2013-10/msg00006.html
11 I never intended to permanently fork MXE, I was only looking ofr a way 11 I never intended to permanently fork MXE, I was only looking for a way
12 to build Octave and all its dependencies, primarily for Windows 12 to build Octave and all its dependencies, primarily for Windows
13 systems. 13 systems.
14 14
15 Later, I needed to build Octave for old RHEL and SuSE systems that did 15 Later, I needed to build Octave for old RHEL and SuSE systems that did
16 not have sufficiently recent versions of the build tools or other 16 not have sufficiently recent versions of the build tools or other
41 able to use EPEL, then they could probably get dependencies that are 41 able to use EPEL, then they could probably get dependencies that are
42 new enough to build Octave. I my experience, people using these old 42 new enough to build Octave. I my experience, people using these old
43 systems are not willing to use packages from EPEL or similar projects. 43 systems are not willing to use packages from EPEL or similar projects.
44 44
45 John W. Eaton 45 John W. Eaton
46 jwe@octave.org
46 2017-04-11 47 2017-04-11