+ Install Qt 4 and make sure qmake is found.
+ Add the folder with qmake to the environment variable PATH.
+ If you've compiled Qt by yourself or qmake is not found after
+ installing Qt fix PATH,
+ Linux/Unix: export PATH=<your path to qt>/bin:$PATH
+ Windows : set PATH=<your path to qt>\bin;%PATH%
+
+ When you wanna run LyX without installing from a out-of-source
+ build directory you have to set the environment variable LYX_DIR_20x
+ and it must point to the lib dir in the source tree.
+ Linux/Unix: export LYX_DIR_20x=<lyx-source>/lib
+ Windows : set LYX_DIR_20x=<lyx-source>\lib
+
+ Windows specific
+
+ On Windows install the supplementary modules:
+ * Visual Studio 2008: ftp://ftp.lyx.org/pub/lyx/contrib/lyx-windows-deps-msvc2008.zip
+ * Visual Studio 2010: ftp://ftp.devel.lyx.org/pub/contrib/windows/bin
+ or use the option LYX_DEPENDENCIES_DOWNLOAD, then you have to add
+ these paths to your PATH variable:
+ <build-dir>\msvc2010-deps\deps20\bin
+ <build-dir>\msvc2010-deps\deps20\python
+ <build-dir>\msvc2010-deps\deps20\imagemagick
+ <build-dir>\msvc2010-deps\deps20\ghostscript
+ <build-dir>\msvc2010-deps\deps20\gettext-tools
+
+ If cmake couldn't find these modules set GNUWIN32_DIR, eg.
+ -DGNUWIN32_DIR=c:\gnuwin32. By default cmake searches in your
+ program folder. Or use the cmake GUI to set the GNUWIN32_DIR path.
+
+ The build process tries to find aspell on Windows
+ in %ProgramFiles%/GnuWin32/ and in /usr/ or in /usr/local
+ under Linux. If it could not find aspell, spell checking
+ will be disabled.
+
+
+
+Generating build system files
+------------------------------
+
+ CMake is a build system file generator. On all systems it could
+ generate files for several build systems, for instance Makefiles
+ for make, project files for Visual Studio, Xcode, Eclipse.
+
+ Running cmake without any argument lists all supported build
+ systems on your system. Passing one of them as -G"<build system name>"
+ argument when running cmake selects this.
+
+
+
+Building out-of-source
+-----------------------
+
+ The standard way of using CMake is to build in a folder which doesn't resides
+ in the source tree. This has the advantage, that a complete fresh build could
+ be done by simply deleting all files in the build folder and to re-run cmake
+ again.
+
+ Another benefit of out-of-source builds is that several builds (debug, release,
+ command-line builds, IDE project files) could all use the same source tree.
+
+ Therefore when using cmake create a folder outside of the source tree and
+ select this folder when using CMake's GUI, cmake-gui, or go into this folder
+ when you call cmake from the shell.
+
+
+
+Using cmake
+------------
+
+ When calling cmake you must pass the path to the source tree (absolute are relative)
+ and optionally the generator (each system has its own default). Additional arguments
+ could be passed with the -D prefix.
+
+ Here some examples, assuming the build folder is in the same folder as the source tree:
+
+ * Makefiles on Linux
+ cmake ../trunk/development/cmake
+
+ * Project files for QtCreator:
+ Open the trunk/development/cmake/CMakeLists.txt file and select the build folder
+ or create the files in the command line using the -G"CodeBlocks *" option, eg
+ cmake ../trunk/development/cmake -G"CodeBlocks - Unix Makefiles"
+
+ * Project files for Xcode
+ cmake ../trunk/development/cmake -GXcode
+
+ * Project files for Visual Studio 10
+ cmake ..\trunk\development\cmake -G"Visual Studio 10"
+
+ * NMake files for Visual Studio
+ cmake ..\trunk\development\cmake -G"NMake Makefiles"
+
+ * Makefiles for MinGW
+ cmake ..\trunk\development\cmake -G"MinGW Makefiles"
+
+
+ Daily work:
+
+ * Re-running cmake is simple
+ cmake .
+
+ * Adding new files
+ The cmake build system scans the directories, so no need to update any file,
+ just re-run cmake. Also the mocing rules are generated.