What do I need to run LyX?
- Either of :
+ Either:
* a Unix-like system (including Windows with cygwin)
* Windows 2000 or newer
- * Mac OS 10.2 or newer
+ * Mac OS 10.4 or newer
A decent LaTeX2e installation (e.g. TeX Live for Linux, MikTeX for
- Windows).
- Python 2.3 or later to convert old LyX files and for helper scripts
- (note that you need at least Python 2.3.4 for exporting LyX files
- to a pre-unicode format, as previous versions are affected by a bug
- about the normalization of unicode strings)
+ Windows).
+
+ Python 2.7 to convert old LyX files and for helper scripts.
+ Note: Python 3 (3.3 or later) support is work in progress.
How does the LyX version scheme work?
LyX uses a contiguous numbering scheme for versions, where a
- number "1.x.y" indicates a stable release '1.x', maintenance
- release 'y'. In other words, LyX 1.5.0 was the first stable
- release in the 1.5-series of LyX. At the time of writing, the
- latest maintenance release in the 1.5-series was LyX 1.5.2
+ number "2.x.y" indicates a stable release '2.x', maintenance
+ release 'y'. In other words, LyX 2.2.0 was the first stable
+ release in the 2.2-series of LyX. At the time of writing, the
+ latest maintenance release in the 2.2-series was LyX 2.2.3.
Please note that maintenance releases are designed primarily to
fix bugs, and that the file format will _never_ change due to a
series. To summarize, there are three possible types of file names
that are of interest to normal users:
- lyx-1.5.0.tar.gz -- stable release, first in the 1.5-series
- lyx-1.5.5.tar.gz -- fifth maintenance release of LyX 1.5
- lyx-1.5.0rc1.tar.gz -- potentially unstable release candidate
+ lyx-2.2.0.tar.gz -- stable release, first in the 2.2-series
+ lyx-2.2.3.tar.gz -- fifth maintenance release of LyX 2.2
+ lyx-2.3.0rc1.tar.gz -- potentially unstable release candidate
Note that the goal is not parallel development as for the linux
kernel --the team is too small to afford that-- but rather to
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 Subversion, the version string will
- look like one of:
+ If you get the source from Git, the version string will look like
+ one of:
- 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.
+ 2.2.4dev -- this is the stable branch on which maintenance
+ release 2.2.4 will eventually be tagged.
+ 2.3.0dev -- this is the main branch on which stable
+ release 2.3.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.6.0, you need at
- least gcc 3.2.x.
+ gcc/g++, but some others work also. As of LyX 2.3.0, you need
+ at least gcc 4.6.x.
- * The Qt4 library, at least version 4.2.0. For all features
- newer versions (e.g. Qt 4.5) are recommended.
+ * The Qt library, at least version 4.8.0. For all features
+ newer versions (e.g. Qt 5.6) are recommended.
Read the file "INSTALL" for more information on compiling.
ftp://ftp.lyx.org/pub/lyx/
The LyX Development page has information about the development
- effort. LyX is under Subversion control, so you can get the very
+ effort. LyX is under Git version 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/
+ http://www.lyx.org/Development
How do I submit a bug report?
You'll find detailed info on submitting bug reports there.
If you can't do that, send details to the LyX Developers' mailing
- list, or use the LyX bug tracker at http://www.lyx.org/trac/.
+ list, or use the LyX bug tracker at
+ http://www.lyx.org/trac/wiki/BugTrackerHome .
Don't forget to mention which version you are having problems with!
How can I participate in the development of LyX?