Either of :
* a Unix-like system (including Windows with cygwin)
- * Windows 98 or newer
- * Mac OS 10.2 or newer
+ * Windows 2000 or newer
+ * Mac OS 10.2 or newer
A decent LaTeX2e installation (e.g. teTeX for unix) not older
than 1995/12/01.
- Python 1.5.2 or later to convert old LyX files
+ Python 2.3 or later to convert old LyX files and for helper scripts
How does the LyX version scheme work?
- LyX uses a continuous numbering scheme in which odd or
- even numbering is not significant. Instead a number '1.x.y'
- indicates stable release '1.x', fix level 'y'. Prereleases
- are labeled with a "pre" suffix. Thus there are three possible
- file names:
-
- lyx-1.4.0.tar.gz -- stable release
- lyx-1.4.5.tar.gz -- fifth maintenance release of the
- 1.4 stable release
- lyx-1.4.0pre1.tar.gz -- potentially unstable test release
-
- The maintenance releases are designed primarily to fix bugs. The
- goal here is not to have parallel development as for the linux
- kernel (the team is too small to afford that), but rather to
- include all the simple (so that the maintenance burden on us
+ LyX uses a contiguous numbering scheme for versions, where a
+ number "1.x.y" indicates a stable release '1.x', fix level 'y'.
+ Prereleases are denoted with the suffix "pre" and there are
+ therefore three possible types of file names:
+
+ lyx-1.5.0.tar.gz -- stable release
+ lyx-1.5.5.tar.gz -- fifth maintenance release of LyX 1.5
+ lyx-1.5.0pre1.tar.gz -- potentially unstable test release
+
+ The maintenance releases are designed primarily to fix bugs,
+ and the file format will _never_ change due to a maintenance
+ release!
+
+ The goal here is not to have parallel development as for the
+ linux kernel (the team is too small to afford that), but rather
+ to include all the simple (so that the maintenance burden on us
is not too high) and safe (so that system administrators can
install them without fear) bug fixes. Experience shows that
these releases will contain a few new features, and that the
bulk of the patches will be documentation updates.
- If you get the source from cvs, the version string will look like
- one of:
+ If you get the source from Subversion, the version string will
+ look like one of:
- 1.4.1cvs -- this is the stable branch on which maintenance
- release 1.4.1 will eventually be tagged.
- 1.5.0cvs -- this is the main branch on which stable
- release 1.5.0 will eventually be tagged.
+ 1.5.1svn -- this is the stable branch on which maintenance
+ release 1.5.1 will eventually be tagged.
+ 1.6.0svn -- this is the main branch on which stable
+ release 1.6.0 will eventually be tagged.
What's new?
What do I need to compile LyX from the source distribution?
* A good C++ compiler. Development is being done mainly with
- gcc/g++, but some others work also. As of LyX 1.4.0, you need at
- least gcc 3.x.
-
- Either:
- * The Xforms library, version 1.0.
- * LibXpm, version 4.7 or newer.
+ gcc/g++, but some others work also. As of LyX 1.5.0, you need at
+ least gcc 3.2.x.
- Or:
- * The Qt library, version 3.0 or newer (although version 2.3
- may work).
+ * The Qt4 library, version 4.1.1 or newer.
Read the file "INSTALL" for more information on compiling.
right-to-left languages like Arabic or Hebrew. There is a port
of LyX named CJK-LyX which adds support for Chinese, Korean
and Japanese (http://cellular.phys.pusan.ac.kr/cjk.html)
+ [This support is being merged in lyx-1.5]
Menus and error messages have been translated to 17 languages.
For the status of the different translations, see
ftp://ftp.lyx.org/pub/lyx/
The LyX Development page has information about the development
- effort. LyX is under CVS control, so you can get the very
+ effort. LyX is under Subversion control, so you can get the very
latest sources from there at any time.
http://www.lyx.org/devel
ftp://ftp.devel.lyx.org/pub/lyx/
projects / lyx.git / blobdiff