4 If you have checked this out from CVS, you need to have
5 automake, autoconf, and gettext installed. Then,
6 type "./autogen.sh" to build the needed configuration
7 files and proceed as stated below.
9 Compiling and installing LyX
10 ============================
12 Quick compilation guide
13 -----------------------
15 These four steps will compile, test and install LyX:
18 configures LyX to your system.
24 runs the program so you can check it out.
27 will install it. You can use "make install-strip" instead
28 if you want a smaller binary.
34 You will need to have both an Xforms library and Xpm library to compile
35 LyX. It is imperative that you have the correct versions of these
36 libraries, and their associated header files.
38 As of LyX version 1.1.5, you will need to have Xforms library and header
39 version 0.88 or 0.89. Version 0.88 is a stable release and the
40 recommended version. On some systems, such as linux ELF, there are shared
41 library versions of the Xforms library, which require an installation step
42 to configure the system.
44 Xforms is available (free) only in binary format, source code is not
45 available. If it is not available for your machine, contact the Xforms
46 developers to request a version for your system. You can get it from
48 http://world.std.com/~xforms/
49 ftp://ncmir.ucsd.edu/pub/xforms/
50 ftp://ftp.lyx.org/pub/xforms/
51 ftp://ftp.fu-berlin.de/unix/X11/gui/xforms
52 ftp://ftp.cs.ruu.nl/pub/XFORMS/
54 In addition, you must have libXpm version 4.7 (or newer; 4.8 rumoured
57 libXpm can be found at:
58 http://www.funet.fi/pub/Linux/sunsite/X11/libs/!INDEX.html
59 (or similar locations at other sunsites like sunsite.unc.edu)
61 You will also need a recent C++ compiler, where recent means that the
62 compilers are close to C++ standard conforming. Compilers that are
63 known to compile LyX are gcc 2.8.1 and 2.95.x, the various versions of
64 egcs and Digital C++ version 6.1. Please tell us your experience with
65 other compilers. It is _not_ possible to compile LyX with gcc 2.7.x,
66 and this is not likely to change in the future.
68 Note that, contrary to LyX 1.0.x, LyX 1.1.x makes great use of C++
69 Standard Template Library (STL); this means that gcc users will have
70 to install the relevant libstdc++ library to be able to compile this
73 If you make modifications to files in src/ (for example by applying a
74 patch), you will need to have the GNU gettext package installed, due to
75 some dependencies in the makefiles. You can find the latest (alpha)
78 ftp://alpha.gnu.org/gnu/gettext-0.10.xx.tar.gz.
80 LyX contains a hack to work around this, but you should not rely too
84 Finally, the two following programs should be available at
87 o Perl (at least 5.002) is needed for the reLyX script. reLyX will
88 not be installed if perl is not found. If the environment
89 variable PERL is set to point to some program, this value will be
90 used, even if the program does no exist (this can be useful if
91 the machine on which LyX is built is not the one where it will
94 o LaTeX2e should be correctly setup for the user you are logged
95 as. Otherwise, LyX will not be able to run a number of tests. Note
96 that users can run these tests manually with Option->Configure.
100 ---------------------
102 LyX can be configured using GNU autoconf utility which attempts to guess
103 the configuration needed to suit your system. The standard way to use it
104 is described in the file INSTALL.autoconf. In most cases you will be able
105 to create the Makefile by typing
109 For more complicated cases, LyX configure takes the following specific
112 o --with-extra-lib=DIRECTORY that specifies the path where LyX will find
113 extra libraries (Xpm, xforms) it needs. Defaults to NONE (i.e. search
114 in standard places). You can specify several directories, separated
117 o --with-extra-inc=DIRECTORY that gives the place where LyX will find
118 xforms headers. Defaults to NONE (i.e. search in standard places).
119 You can specify several directories, separated by colons.
121 o --with-extra-prefix[=DIRECTORY] that is equivalent to
122 --with-extra-lib=DIRECTORY/lib --with-extra-inc=DIRECTORY/include
123 If DIRECTORY is not specified, the current prefix is used.
125 o --with-lyxname=STRING sets the name of the installed LyX binary and
126 of the LyX library directory to STRING. This may be used to
127 compile lyx as lyx-1.1 and avoid clashes with earlier/later
128 versions. Default is "lyx".
131 There are also flags to control the internationalization support in
134 o --disable-nls suppresses all internationalization support,
135 yielding a somewhat smaller code.
137 o --with-included-gettext forces the use of the included GNU gettext
138 library, although you might have another one installed.
140 o --with-catgets allows to use the catget() functions which can
141 exist on your system. This can cause problems, though. Use with
144 o You can also set the environment variable LINGUAS to a list of
145 language in case ou do not want to install all the translation
146 files. For example, if you are only interested in German and
147 Finnish, you can type (with sh or bash)
148 export LINGUAS='de fi'
149 before running configure.
151 Moreover, the following generic configure flags may be useful:
153 o --prefix=DIRECTORY specifies the root directory to use for
154 installation. [defaults to where lyx has already been installed or
157 o --datadir=DIRECTORY gives the directory where all extra LyX
158 files (lyxrc example, documentation, templates and layouts
159 definitions) will be installed.
160 [defaults to ${prefix}/share/lyx${program_suffix}]
162 o --bindir=DIRECTORY gives the directory where the lyx binary
163 will be installed. [defaults to ${prefix}/bin]
165 o --mandir=DIRECTORY gives the directory where the man pages will go.
166 [defaults to ${prefix}/man]
168 Note that the --with-extra-* commands are not really robust when it
169 comes to use of relative paths. If you really want to use a relative path
170 here, you can prepend it with "`pwd`/".
172 If you do not like the default compile flags used (-g -O2 on gcc), you can
173 set CXXFLAGS variable to other values as follows:
175 o CXXFLAGS='-O2' (sh, bash)
176 o setenv CXXFLAGS '-O2' (csh, tcsh)
178 Similarly, if you want to force the use of some specific compiler, you can
179 give a value to the CXX variable.
181 If you encounter problems, please read the section 'Problems' at the end of
184 In particular, the following options could be useful in some
187 o --with-warnings that make the compiler output more warnings during
188 the compilation of LyX. Opposite is --without-warnings. By default,
189 this flag is on for development versions only.
191 o --enable-assertions that make the compilier generater run-time
192 code which checks that some variables have sane values. Opposite
193 is --disable-assertions. By default, this flag is on for
194 development versions only.
196 o --with-broken-headers that provides prototypes to replace functions
197 not correctly defined in SunOS4 and SCO header files. Its only effect is
198 to suppress a few warnings. It is autodetected by default.
200 o --without-latex-config that disables the automatic detection of your
201 latex configuration. This detection is automatically disabled if
202 latex cannot be found. If you find that you have to use this
203 flag, please report it as a bug.
205 o --without-liberty suppresses the detection of the -liberty library
206 (see the section 'Problems').
209 Compiling and installing LyX
210 ----------------------------
212 Once you've got the Makefile created, you just have to type:
219 Since the binaries with debug information tend to be huge (although
220 this does not affect the run-time memory footprint), you maight want
221 to strip the lyx binary. In this case replace "make install" with
225 BTW: in the images subdirectory there is also a small icon "lyx.xpm",
226 that can be used to display lyx-documents in filemanagers.
228 If configure fails for some strange reason
229 ------------------------------------------
231 Even when configure fails, it creates a Makefile. You always can check
232 the contents of this file, modify it and run 'make'.
234 Compiling For Multiple Architectures
235 ------------------------------------
237 You can compile LyX for more than one kind of computer at the same
238 time, by placing the object files for each architecture in their own
239 directory. To do this, you must use a version of `make' that supports
240 the `VPATH' variable, such as GNU `make'. `cd' to the directory where
241 you want the object files and executables to go and run the
242 `configure' script. `configure' automatically checks for the source
243 code in the directory that `configure' is in and in `..'.
245 If you have to use a `make' that does not supports the `VPATH'
246 variable, you have to compile LyX for one architecture at a time in
247 the source code directory. After you have installed LyX for one
248 architecture, use `make distclean' before reconfiguring for another
251 Preparing a binary distribution for the use of others
252 ------------------------------------------------------
254 o Compile LyX with the right compiler switches for your
255 architecture. In particular you might want to ensure that
256 libraries like xforms and xpm are statically linked. To this end,
257 you can use a command like
259 make LYX_LIBS='/foo/libforms.a /bar/libXpm.a'
261 Moreover, make sure you use the --without-latex-config switch
262 of configure, since others might not be interested by your
265 o Create a file README.bin describing your distribution and
266 referring to *you* if problems arise. As a model, you can use the
267 file development/tools/README.bin.example, which can be a good
270 o Type `make bindist'. This will create a file
271 lyx-1.xx.yy-bin.tar.gz. Rename it to reflect you architecture
272 and the peculiarities of your build (e.g. static vs. dynamic).
274 o Check that everything is correct by unpacking the distribution
275 in some private place and running it. In particular, check the
276 output of `ldd lyx' to know which libraries are really needed.
278 o Upload your binary file to ftp.devel.lyx.org:/pub/incoming, and
279 notify larsbj@lyx.org.
285 This section provides several hints that have been submitted by LyX
286 team member or users to help compiling on some particular
287 architectures. If you find that some of this hints are wrong, please
290 o If you have problems indicating that configure cannot find a part of
291 the xforms or Xpm library, use the --with-extra-lib and --with-extra-inc
292 options of configure to specify where these libraries reside.
294 o Configure will seemingly fail to find xpm.h and forms.h on linux if
295 you did a 'make mrproper' in the kernel directory, because this
296 removes some symbolic links that are needed for compilation. A 'make
297 symlinks' in linux kernel sources fixes that.
299 o If you have GNU gettext installed on your system (e.g. on linux),
300 you will get tons of warnings like:
302 bullet_forms.C:101: warning: passing `char *' to argument 1 of
303 `__builtin_constant_p(int)' lacks a cast
305 These are in harmless warnings caused by a bug in libintl.h, but
306 will be solved if you use --with-included-gettext when configuring
309 o It is possible to compile lyx with Digital Unix cxx compiler
310 version 6.1 (and presumably compaq C++ 6.2 on both Tru64 unix and
311 linux/alpha, when this will be available), provided one uses
313 CXXFLAGS='-ptr /tmp/lyx_cxx_repository -std strict_ansi -g -O'
315 Note that this will not work when compiling directly from the cvs
316 repository, due to the tricks used by automake for dependencies. Ask
317 Jean-Marc.Lasgouttes@inria.fr for a workaround.
319 o On Digital Unix with cxx, you may have a compilation error in
320 lyx_main.C if you have GNU gettext installed. This is due to a bug
321 in gettext. To solve this, you can either (1) configure with
322 --with-included-gettext or (2) add -D__STDC__ to cxx flags.
324 o The configure script seems to hang while it is checking the LaTeX setup.
325 We think that this is not a real problem, but rather a symptom of the
326 fact that the ec-fonts are being rendered. This process can take quite
327 some time, so the remedy is simply to have patience. (The fonts need to
328 be rendered at some point to be usable anyways.)
330 o According to John Collins <collins@phys.psu.edu>, on SunOS 4.1.3 you may
331 find two sets of X libraries, and they are of course incompatible :-)
332 One is the set provided as part of OpenWindows, and one is the standard
333 X distribution (e.g., X11R5). If you encounter problems (or if, for
334 some obscure reasons configure cannot find your X libraries) you can
335 use the following options:
337 o --x-libraries=DIRECTORY that indicates where the X libraries reside.
339 o --x-includes=DIRECTORY that indicate where the X include files reside.
341 The standard X11R5 libraries should work when the OpenWindows ones
344 o Some systems lack functions that LyX needs. To fix this, configure
345 tries to link against the -liberty library, if it is available.
346 If you experience problems with missing symbols at link time, you
347 could try to install libiberty.a, which comes with several GNU
348 packages (in particular libg++). In any case, please report your
349 problems to lyx-devel@lists.lyx.org.
351 The option --without-liberty disable the detection of -liberty. It
352 is meant for debugging purpose only.
354 o According to David Sundqvist <David_Sundqvist@vd.volvo.se>, some
355 changes are needed to compile with aCC on HP-UX 10.20. These are the
356 relevant changes in the makefile (with comments tagged on):
358 CXX = /opt/aCC/bin/aCC
359 CXXFLAGS = -O +inst_none # The aCC compiler tries to run instantiations
360 # which currently break.
362 LIBS = -lforms -lXpm -lSM -lICE -lc -lm -lX11 -lCsup # must link with Csup
363 LDFLAGS = -L/opt/aCC/lib # perhaps not needed.
366 o On Digital Unix with gcc, you can get warnings like
368 warning, LyXFamilyNames not found in original or external symbol tables, value defaults to 0
370 These concern symbols beginning with an uppercase letter and seems
371 to be harmless. Similarly, the compilation can end with the
375 Warning: Linking some objects which contain exception information sections
376 and some which do not. This may cause fatal runtime exception handling
377 problems (last obj encountered without exceptions was ../intl/libintl.a).
380 You can safely ignore it.