diff --git a/doc/FAQ.html b/doc/FAQ.html
index d017cfe7..51dc2b19 100644
--- a/doc/FAQ.html
+++ b/doc/FAQ.html
@@ -11,6 +11,8 @@ a:hover { background-color: #CCCCCC; }
a:active { color: #551A8B; }
a:visited { color: #0000EE; }
.code { background-color: #EAEAEA; }
+.diff_del { color: #660000; background-color: #FF6666; }
+.diff_add { color: #006600; background-color: #66FF66; }
-->
@@ -61,7 +63,8 @@ a:visited { color: #0000EE; }
Where can I submit bug reports or feature requests?
What programming language is LameXP written in?
Where can I find the LameXP source code?
-What are the prerequisites to build LameXP from the sources?
+What are the prerequisites to build LameXP from the sources?
+How do I compile latest Qt as 'static' libraries?
@@ -926,7 +929,8 @@ LameXP is currently being developed using the following build environment:
- Run qtvars.bat (or qtenv2.bat) before launching Visual Studio in order to set up the Qt environment
- Visual Studio 2008 solution/project files are still provided for people targeting Windows 2000
-
- In order to make "fully static" builds of LameXP, you need to compile/download Qt as 'static' libraries
+
- Visual Studio 2012 solution/project files are now provided too, but make sure you installed "Update 1"
+
- In order to make "fully static" builds of LameXP, you'll need Qt as 'static' libraries (see below!)
- The Windows Platform SDK v6.0A should work as well, but there may be a few limitations
- Only the "fully static" builds may still run on Windows 2000, due to workarounds we implemented
- Support for the GNU Toolchain (GCC/MinGW + Make) is planned for a future version
@@ -941,31 +945,44 @@ In order to use the LameXP deployment scripts you need the following tools:
<
Aero plug-in
UPX - the Ultimate Packer for eXecutables
MPRESS - high-performance executable packer for PE32/PE32+
-GnuPG - the GNU Privacy Guard v1.4.x
+GnuPG - the GNU Privacy Guard v1.4.x
NOTE: Copy buildenv.template.txt to buildenv.txt and edit the paths as needed!
+
+
+
+How do I compile latest Qt as 'static' libraries?
-Instructions to build Qt as 'static' libraries:
-- Make sure Visual Studio 2010 and Strawberry Perl for Windows are installed
-
- Download and extract the Qt 4.8.x source code package
-
- Open a new command window (cmd.exe)
+In order to make "fully static" builds of LameXP, i.e. builds that don't depend pn any DLL's except for the
+obligatory operating system DLL's, you'll need to compile Qt as 'static' libraries. The following simple
+instructions should make it easy to build Qt from the sources and as "static" libraries:
+- Make sure Visual Studio 2010 with Service Pack 1 or Visual Studio 2012 with Update 1 are installed
+
- Make sure Strawberry Perl for Windows and Python 2.7 are installed
+
- Download and extract the Qt 4.8.x source code package (e.g. to C:\QtSources\4.8.x)
+
- Edit the file mkspecs\win32-msvc2010\qmake.conf from your Qt Sources directory as follows:
+- Old: QMAKE_CFLAGS_RELEASE = -O2 -MD
New: QMAKE_CFLAGS_RELEASE = -O2 -MT <more optimization flags here>
+ - Old: QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MD -Zi
New: QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MT -Zi <more optimization flags here>
+ - Open a new command window (cmd.exe) - use this very same console for all upcoming steps!
- Add Strawberry Perl to your PATH (e.g. set PATH=C:\strawberry\perl\bin;%PATH%)
-
- Now run vcvarsall.bat form your Visual C++ install directory - within the same console!
+
- Add Python 2.7 to your PATH (e.g. set PATH=C:\python27;%PATH%)
+
- Run vcvarsall.bat x86 form your Visual C++ install directory - within the same console!
- Change the current directory to the Qt Sources path (e.g. C:\QtSources\4.8.x)
-
- Finally run configure.exe -release -static -ltcg <more options> and wait for completion
-
- You can now open and build the solution files (e.g. src\corelib\QtCore.sln in Visual Studio
-
- Make sure you select the "Release" configuration for your builds!
-
- It is also required to change "Code Generation ⇒ Runtime Library" to "/MT" for all projects!
-
- Libraries you need to build for LameXP include the following:
+- Run configure.exe -release -static -ltcg -qt-zlib -qt-libpng -qt-libjpeg -qt-libtiff -qt-libmng
+- Hint: For Visual Studio 2012 you currently need to add -platform win32-msvc2010 too
+ - Now the makefiles should have been generated, so simply enter nmake /B and be patient - voilà!
+
- The build process is going to take good amount of time. Once done, make sure you got all needed libs
+
- Libraries you'll need to build LameXP as a "static" binary include the following:
- lib\qtmain.lib
- lib\QtCore.lib
- lib\QtGui.lib
- lib\QtSvg.lib
- lib\QtXml.lib
-
- plugins\imageformats\qgif.lib
- plugins\imageformats\qico.lib
-
- plugins\imageformats\qsvg.lib
- - Put the static *.lib files into the 'LameXP\etc\Prerequisites\qt4_static\lib' directory
-
- ImageFormat plugins go to 'LameXP\etc\Prerequisites\qt4_static\plugins\imageformats'
+ - plugins\imageformats\qsvg.lib
+
- plugins\imageformats\qtga.lib
+ - Put all the static *.lib files into the 'LameXP\etc\Prerequisites\qt4_static\lib' directory
+
- ImageFormat plugins go to 'LameXP\etc\Prerequisites\qt4_static\plugins\imageformats'
+
- Congratulations, you should now be prepared to build the Release_Static configuration of LameXP :-)
+
- NOTE: Static libraries only work with the same compiler (version) they were built with!
eof