LyX. It is imperative that you have the correct versions of these
libraries, and their associated header files.
-As of LyX version 1.1.5, you will need to have Xforms library and header
-version 0.88 or 0.89. Version 0.88 is a stable release and the
-recommended version. On some systems, such as linux ELF, there are shared
-library versions of the Xforms library, which require an installation step
-to configure the system.
+As of LyX version 1.1.5, you will need to have Xforms library and
+header version 0.88 or 0.89. Version 0.88 is a stable release and the
+recommended version, but 0.89.6 seems to be work very well too. On
+some systems, such as linux ELF, there are shared library versions of
+the Xforms library, which require an installation step to configure
+the system.
Xforms is available (free) only in binary format, source code is not
available. If it is not available for your machine, contact the Xforms
In addition, you must have libXpm version 4.7 (or newer; 4.8 rumoured
to work).
+To use the thesaurus, you will need to install libAikSaurus, available
+from :
+
+ http://aiken.clan11.com/aiksaurus/
+
+You will also probably need GNU m4 (perhaps installed as gm4).
+
libXpm can be found at:
http://www.funet.fi/pub/Linux/sunsite/X11/libs/!INDEX.html
(or similar locations at other sunsites like sunsite.unc.edu)
You will also need a recent C++ compiler, where recent means that the
-compilers are close to C++ standard conforming. Compilers that are
-known to compile LyX are gcc 2.8.1 and 2.95.x, the various versions of
-egcs and Digital C++ version 6.1. Please tell us your experience with
-other compilers. It is _not_ possible to compile LyX with gcc 2.7.x,
-and this is not likely to change in the future.
+compilers are close to C++ standard conforming. Compilers that are
+known to compile LyX are egcs 1.1.x, gcc 2.95.x and later, and Digital
+C++ version 6.1 and later. Please tell us your experience with other
+compilers. It is _not_ possible to compile LyX with gcc 2.7.x and
+2.8.x, and this is not likely to change in the future.
Note that, contrary to LyX 1.0.x, LyX 1.1.x makes great use of C++
Standard Template Library (STL); this means that gcc users will have
to install the relevant libstdc++ library to be able to compile this
version.
-If you make modifications to files in src/ (for example by applying a
-patch), you will need to have the GNU gettext package installed, due to
-some dependencies in the makefiles. You can find the latest (alpha)
-version from:
+If you make modifications to files in src/ (for example by applying a
+patch), you will need to have the GNU gettext package installed, due
+to some dependencies in the makefiles. You can find the latest version
+from:
- ftp://alpha.gnu.org/gnu/gettext-0.10.xx.tar.gz.
+ ftp://ftp.gnu.org/gnu/gettext-0.10.xx.tar.gz.
LyX contains a hack to work around this, but you should not rely too
much on it.
--with-extra-lib=DIRECTORY/lib --with-extra-inc=DIRECTORY/include
If DIRECTORY is not specified, the current prefix is used.
- o --with-lyxname=STRING sets the name of the installed LyX binary and
- of the LyX library directory to STRING. This may be used to
- compile lyx as lyx-1.1 and avoid clashes with earlier/later
- versions. Default is "lyx".
+ o --with-version-suffix will install LyX as lyx-<version>, e.g. lyx-1.2.0
+ The LyX data directory will be something like <whatever>/lyx-1.2.0/.
+ Additionally your user configuration files will be found in e.g.
+ $HOME/.lyx-1.2.0
+
+ You can use this feature to install more than one version of LyX on
+ the same system. You can optionally specify a "version" of your own,
+ by doing something like : ./configure --with-version-suffix=-latestcvs
+ o --enable-optimization=VALUE enables you to set optimization to a
+ higher level as the default (-O), for example --enable-optimization=-O3.
+ o --disable-optimization - you can use this to disable compiler
+ optimization of LyX. The compile may be much quicker with some
+ compilers, but LyX will run more slowly.
+
There are also flags to control the internationalization support in
LyX:
Moreover, the following generic configure flags may be useful:
o --prefix=DIRECTORY specifies the root directory to use for
- installation. [defaults to where lyx has already been installed or
- /usr/local]
+ installation. [defaults to /usr/local]
o --datadir=DIRECTORY gives the directory where all extra LyX
files (lyxrc example, documentation, templates and layouts
In particular, the following options could be useful in some
desperate cases:
- o --with-warnings that make the compiler output more warnings during
- the compilation of LyX. Opposite is --without-warnings. By default,
+ o --enable-warnings that make the compiler output more warnings during
+ the compilation of LyX. Opposite is --disable-warnings. By default,
this flag is on for development versions only.
o --enable-assertions that make the compilier generater run-time
in some private place and running it. In particular, check the
output of `ldd lyx' to know which libraries are really needed.
- o Upload your binary file to ftp.lyx.org:/pub/lyx/uploads.
+ o Upload your binary file to ftp.devel.lyx.org:/pub/incoming, and
+ notify larsbj@lyx.org.
Problems
the xforms or Xpm library, use the --with-extra-lib and --with-extra-inc
options of configure to specify where these libraries reside.
- o Configure will seemingly fail to find xpm.h and forms.h on linux if
- you did a 'make mrproper' in the kernel directory, because this
- removes some symbolic links that are needed for compilation. A 'make
- symlinks' in linux kernel sources fixes that.
+ o Configure will seemingly fail to find xpm.h and forms.h on linux
+ if the kernel headers are not available. Two cases are possible:
+
+ - you have not installed the kernel sources. Then you should
+ install them or at least the kernel-headers package (or
+ whatever it is called in your distribution).
- o If you have GNU gettext installed on your system (e.g. on linux),
- you will get tons of warnings like:
+ - you have the sources, but you did a 'make mrproper' in the
+ kernel directory (this this removes some symbolic links that
+ are needed for compilation). A 'make symlinks' in linux kernel
+ sources fixes that.
- bullet_forms.C:101: warning: passing `char *' to argument 1 of
- `__builtin_constant_p(int)' lacks a cast
+ o if you are using RedHat Linux 7.x, you must make sure you have the
+ latest updated gcc and related packages installed (at least -85),
+ or LyX will not compile or will be mis-compiled.
+
+ o if you get an error message when compiling LyX that looks like this :
- These are in harmless warnings caused by a bug in libintl.h, but
- will be solved if you use --with-included-gettext when configuring
- LyX.
+ ../../src/minibuffer.h:17: using directive `Object' introduced
+ ambiguous type `_ObjectRec *'
- o It is possible to compile lyx with Digital Unix cxx compiler
- version 6.1 (and presumably compaq C++ 6.2 on both Tru64 unix and
- linux/alpha, when this will be available), provided one uses
- CXX=cxx
- CXXFLAGS='-ptr /tmp/lyx_cxx_repository -std strict_ansi -g -O'
+ then you need to upgrade the version of the xforms library you have
+ installed.
+
+ o It is possible to compile lyx with Tru64 Unix cxx compiler
+ version 6.2, provided one uses
+ CXX='cxx -std strict_ansi'
+ CXXFLAGS='-ptr /tmp/lyx_cxx_repository -g'
+ CC=cc
Note that this will not work when compiling directly from the cvs
repository, due to the tricks used by automake for dependencies. Ask
Jean-Marc.Lasgouttes@inria.fr for a workaround.
- o On Digital Unix with cxx, you may have a compilation error in
+ o On Tru64 Unix, you may have to compile with
+ --with-included-string to work around a Tru64 linker limitation
+ (the STL string template creates names which may be too long). We
+ also had reports that it helps with gcc 2.95.2 on solaris 2.6.
+
+ o On Tru64 Unix with cxx, you may have a compilation error in
lyx_main.C if you have GNU gettext installed. This is due to a bug
in gettext. To solve this, you can either (1) configure with
--with-included-gettext or (2) add -D__STDC__ to cxx flags.
- o The configure script seems to hang while it is checking the LaTeX setup.
- We think that this is not a real problem, but rather a symptom of the
- fact that the ec-fonts are being rendered. This process can take quite
- some time, so the remedy is simply to have patience. (The fonts need to
- be rendered at some point to be usable anyways.)
-
o According to John Collins <collins@phys.psu.edu>, on SunOS 4.1.3 you may
find two sets of X libraries, and they are of course incompatible :-)
One is the set provided as part of OpenWindows, and one is the standard
projects / lyx.git / blobdiff