Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Uwe Stöhr]

Am 15.06.2012 11:53, schrieb Vincent van Ravesteijn:


  Sorry, there was a response, but it just didn't convince me.


And that's why you reverted it. I still don't understand your concerns but OK, I'm tired of 
fighting. I updated it with the help of Peter, so 2 developers worked on getting the description up 
to date. I don't see why your opinion is stronger then the one of 2 others. If I remember correctly 
you mostly don't like Peter's add-on to CMake. But his version is exactly CMake plus two files extra.


Uwe

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 21-6-2012 13:18, Uwe Stöhr schreef:

Am 15.06.2012 11:53, schrieb Vincent van Ravesteijn:


  Sorry, there was a response, but it just didn't convince me.


And that's why you reverted it. I still don't understand your concerns 
but OK, I'm tired of fighting. I updated it with the help of Peter, so 
2 developers worked on getting the description up to date. I don't see 
why your opinion is stronger then the one of 2 others. If I remember 
correctly you mostly don't like Peter's add-on to CMake. But his 
version is exactly CMake plus two files extra.


Uwe


I think I clearly explained by now why I don't like the change. I guess 
my opinion is stronger, because I'm just sticking to the way it always 
was, and not forcing my fellow developers to change to something that is 
worse without any discussion and/or reasoning.


Concerning the 2 developers: 1 left us, the other one has no clue about 
CMake.


Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Uwe Stöhr]

Am 15.06.2012 11:53, schrieb Vincent van Ravesteijn:


  Sorry, there was a response, but it just didn't convince me.


And that's why you reverted it. I still don't understand your concerns but OK, I'm tired of 
fighting. I updated it with the help of Peter, so 2 developers worked on getting the description up 
to date. I don't see why your opinion is stronger then the one of 2 others. If I remember correctly 
you mostly don't like Peter's add-on to CMake. But his version is exactly CMake plus two files extra.


Uwe

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 21-6-2012 13:18, Uwe Stöhr schreef:

Am 15.06.2012 11:53, schrieb Vincent van Ravesteijn:


  Sorry, there was a response, but it just didn't convince me.


And that's why you reverted it. I still don't understand your concerns 
but OK, I'm tired of fighting. I updated it with the help of Peter, so 
2 developers worked on getting the description up to date. I don't see 
why your opinion is stronger then the one of 2 others. If I remember 
correctly you mostly don't like Peter's add-on to CMake. But his 
version is exactly CMake plus two files extra.


Uwe


I think I clearly explained by now why I don't like the change. I guess 
my opinion is stronger, because I'm just sticking to the way it always 
was, and not forcing my fellow developers to change to something that is 
worse without any discussion and/or reasoning.


Concerning the 2 developers: 1 left us, the other one has no clue about 
CMake.


Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 19-3-2012 10:00, Vincent van Ravesteijn schreef:

Op 18-3-2012 23:59, uwesto...@lyx.org schreef:

Author: Uwe Stöhruwesto...@lyx.org
Date: Sun, 18 Mar 2012 23:59:03 +0100
New Commit: eeda1c099ed55d6883f8f4f59accd61fc8a4fc64
URL: 
http://git.lyx.org/?p=lyx.git;a=commit;h=eeda1c099ed55d6883f8f4f59accd61fc8a4fc64


Log:
- INSTALL.Win32: revise and update the description because since Qt 
4.8 it mustn't be compiled (and can currently also not without a lot 
of hacking). Moreover we have now a build script that does all the 
configuration in one step and we can benefit from the fast Ninja 
compilation


Signed-off-by: Uwe Stöhruwesto...@lyx.org

 4  Install CMake

-   Install the latest CMake from http://www.cmake.org
+   Install the latest CMakescript from
+   
http://sourceforge.net/projects/cmakescript/files/latest/download


 5  Configure

-   - Run the CMake GUI.
+   Open the script file build.bat that you find in your LyX folder
+   C:\LyX\lyx-20\development\cmake
+   with a text editor. Now:

-   - Set the source code path to C:\LyX\lyx-20
- Set the build path to C:\LyX\lyx-20-build
- Click Configure and set the generator to Visual Studio 10.
-
-   - Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
- Pre-compiled dependencies will automatically be downloaded.
+   - Change there D:\Qt\bin to the path where you installed Qt

-   - Set QT_QMAKE_EXECUTABLE to e.g.
- C:\Qt\qt-everywhere-opensource-src-4.7.1\bin\qmake.exe
- and Configure again.
-
-   - Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
- C:\LyX\lyx-20-install and click Configure.
-
-   - Check the Advanced checkbox.
- Set GETTEXT_MSGFMT_EXECUTABLE to
- 
C:\LyX\lyx-20-build\msvc2010-deps\deps20\gettext-tools\msgfmt.exe,

- and do the same for the other gettext tools.
-
-   - Click Generate.
+   - Set the GNUWIN32_DIR to C:\LyX\lyx-20\msvc2010-deps
+ (or wherever you have copied the LyX dependencies)
+   - Set the LYX_SOURCE to C:\LyX\lyx-20
+ (or wherever you have copied the LyX source files)
+   - Set the LYX_BUILD to C:\LyX\lyx-20-build
+ (or wherever you want to store the compilation result)
+
+   (- If you don't want to use the fast compilation mode for 
debug builds,

+  remove the statement -GNinja.)

 6  Compile

-   A Microsoft Visual C++ solution should have been generated at
-   C:\LyX\lyx-20-build\lyx.sln
-   Compile the INSTALL project to get a LyX installation in
-   C:\LyX\lyx-20-install
-
-7   Copy dependencies
-
-Copy
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\bin
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\imagemagick
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\python
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\ghostscript
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\Resources
-   to C:\LyX\lyx-20-install
+   - Open a MSVC Command prompt via Windows' start menu and switch
+ to the folder
+ C:\LyX\lyx-20\development\cmake
+   - To build LyX with debugging information for development, 
execute

+ the build script with the command
+ build devel
+   - To build LyX for a release, execute
+ the script with the command
+ build install
+
+7  Copy dependencies
+
+   Copy
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\bin
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\imagemagick
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\python
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\ghostscript
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\Resources
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)

And copy from the Qt bin directory
-   (e.g. C:\Qt\qt-everywhere-opensource-src-4.7.1\bin)
+   (e.g. C:\Qt\bin)
QtCore4.dll
QtGui4.dll
QtCore4d.dll (if compiling Debug version)
QtGui4d.dll (if compiling Debug version)
-   to C:\LyX\lyx-20-install\bin
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)




Why did you change this ?

IMHO the description is incomplete and not easier. It suddenly 
requires CMakeScript, it doesn't generate a Visual studio file, it 
doesn't download the dependencies automatically. And instead of 
changing the options in the CMake GUI you suddenly prefer to modify a 
batch file. This means that people won't see the options that can be 
changed by a single mouseclick.


You should have discussed this before changing it completely.

Vincent




Apparently I did notice this change, and I complained about it, but 
there was no response. Then I just forgot to revert this change.


Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 15-6-2012 11:52, Vincent van Ravesteijn schreef:

Op 19-3-2012 10:00, Vincent van Ravesteijn schreef:

Op 18-3-2012 23:59, uwesto...@lyx.org schreef:

Author: Uwe Stöhruwesto...@lyx.org
Date: Sun, 18 Mar 2012 23:59:03 +0100
New Commit: eeda1c099ed55d6883f8f4f59accd61fc8a4fc64
URL: 
http://git.lyx.org/?p=lyx.git;a=commit;h=eeda1c099ed55d6883f8f4f59accd61fc8a4fc64


Log:
- INSTALL.Win32: revise and update the description because since Qt 
4.8 it mustn't be compiled (and can currently also not without a lot 
of hacking). Moreover we have now a build script that does all the 
configuration in one step and we can benefit from the fast Ninja 
compilation


Signed-off-by: Uwe Stöhruwesto...@lyx.org

 4  Install CMake

-   Install the latest CMake from http://www.cmake.org
+   Install the latest CMakescript from
+   
http://sourceforge.net/projects/cmakescript/files/latest/download


 5  Configure

-   - Run the CMake GUI.
+   Open the script file build.bat that you find in your LyX folder
+   C:\LyX\lyx-20\development\cmake
+   with a text editor. Now:

-   - Set the source code path to C:\LyX\lyx-20
- Set the build path to C:\LyX\lyx-20-build
- Click Configure and set the generator to Visual Studio 10.
-
-   - Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
- Pre-compiled dependencies will automatically be downloaded.
+   - Change there D:\Qt\bin to the path where you installed Qt

-   - Set QT_QMAKE_EXECUTABLE to e.g.
- C:\Qt\qt-everywhere-opensource-src-4.7.1\bin\qmake.exe
- and Configure again.
-
-   - Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
- C:\LyX\lyx-20-install and click Configure.
-
-   - Check the Advanced checkbox.
- Set GETTEXT_MSGFMT_EXECUTABLE to
- 
C:\LyX\lyx-20-build\msvc2010-deps\deps20\gettext-tools\msgfmt.exe,

- and do the same for the other gettext tools.
-
-   - Click Generate.
+   - Set the GNUWIN32_DIR to C:\LyX\lyx-20\msvc2010-deps
+ (or wherever you have copied the LyX dependencies)
+   - Set the LYX_SOURCE to C:\LyX\lyx-20
+ (or wherever you have copied the LyX source files)
+   - Set the LYX_BUILD to C:\LyX\lyx-20-build
+ (or wherever you want to store the compilation result)
+
+   (- If you don't want to use the fast compilation mode for 
debug builds,

+  remove the statement -GNinja.)

 6  Compile

-   A Microsoft Visual C++ solution should have been generated at
-   C:\LyX\lyx-20-build\lyx.sln
-   Compile the INSTALL project to get a LyX installation in
-   C:\LyX\lyx-20-install
-
-7   Copy dependencies
-
-Copy
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\bin
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\imagemagick
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\python
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\ghostscript
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\Resources
-   to C:\LyX\lyx-20-install
+   - Open a MSVC Command prompt via Windows' start menu and switch
+ to the folder
+ C:\LyX\lyx-20\development\cmake
+   - To build LyX with debugging information for development, 
execute

+ the build script with the command
+ build devel
+   - To build LyX for a release, execute
+ the script with the command
+ build install
+
+7  Copy dependencies
+
+   Copy
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\bin
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\imagemagick
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\python
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\ghostscript
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\Resources
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)

And copy from the Qt bin directory
-   (e.g. C:\Qt\qt-everywhere-opensource-src-4.7.1\bin)
+   (e.g. C:\Qt\bin)
QtCore4.dll
QtGui4.dll
QtCore4d.dll (if compiling Debug version)
QtGui4d.dll (if compiling Debug version)
-   to C:\LyX\lyx-20-install\bin
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)




Why did you change this ?

IMHO the description is incomplete and not easier. It suddenly 
requires CMakeScript, it doesn't generate a Visual studio file, it 
doesn't download the dependencies automatically. And instead of 
changing the options in the CMake GUI you suddenly prefer to modify a 
batch file. This means that people won't see the options that can be 
changed by a single mouseclick.


You should have discussed this before changing it completely.

Vincent




Apparently I did notice this change, and I complained about it, but 
there was no response. Then I just forgot to revert this change.


Vincent


 Sorry, there was a response, but it just didn't convince me.

Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 19-3-2012 10:00, Vincent van Ravesteijn schreef:

Op 18-3-2012 23:59, uwesto...@lyx.org schreef:

Author: Uwe Stöhr
Date: Sun, 18 Mar 2012 23:59:03 +0100
New Commit: eeda1c099ed55d6883f8f4f59accd61fc8a4fc64
URL: 
http://git.lyx.org/?p=lyx.git;a=commit;h=eeda1c099ed55d6883f8f4f59accd61fc8a4fc64


Log:
- INSTALL.Win32: revise and update the description because since Qt 
4.8 it mustn't be compiled (and can currently also not without a lot 
of hacking). Moreover we have now a build script that does all the 
configuration in one step and we can benefit from the fast Ninja 
compilation


Signed-off-by: Uwe Stöhr

 4  Install CMake

-   Install the latest CMake from http://www.cmake.org
+   Install the latest CMakescript from
+   
http://sourceforge.net/projects/cmakescript/files/latest/download


 5  Configure

-   - Run the CMake GUI.
+   Open the script file build.bat that you find in your LyX folder
+   C:\LyX\lyx-20\development\cmake
+   with a text editor. Now:

-   - Set the source code path to C:\LyX\lyx-20
- Set the build path to C:\LyX\lyx-20-build
- Click Configure and set the generator to Visual Studio 10.
-
-   - Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
- Pre-compiled dependencies will automatically be downloaded.
+   - Change there "D:\Qt\bin" to the path where you installed Qt

-   - Set QT_QMAKE_EXECUTABLE to e.g.
- C:\Qt\qt-everywhere-opensource-src-4.7.1\bin\qmake.exe
- and Configure again.
-
-   - Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
- C:\LyX\lyx-20-install and click Configure.
-
-   - Check the Advanced checkbox.
- Set GETTEXT_MSGFMT_EXECUTABLE to
- 
C:\LyX\lyx-20-build\msvc2010-deps\deps20\gettext-tools\msgfmt.exe,

- and do the same for the other gettext tools.
-
-   - Click Generate.
+   - Set the GNUWIN32_DIR to "C:\LyX\lyx-20\msvc2010-deps"
+ (or wherever you have copied the LyX dependencies)
+   - Set the LYX_SOURCE to "C:\LyX\lyx-20"
+ (or wherever you have copied the LyX source files)
+   - Set the LYX_BUILD to "C:\LyX\lyx-20-build"
+ (or wherever you want to store the compilation result)
+
+   (- If you don't want to use the fast compilation mode for 
debug builds,

+  remove the statement "-GNinja".)

 6  Compile

-   A Microsoft Visual C++ solution should have been generated at
-   C:\LyX\lyx-20-build\lyx.sln
-   Compile the INSTALL project to get a LyX installation in
-   C:\LyX\lyx-20-install
-
-7   Copy dependencies
-
-Copy
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\bin
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\imagemagick
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\python
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\ghostscript
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\Resources
-   to C:\LyX\lyx-20-install
+   - Open a MSVC Command prompt via Windows' start menu and switch
+ to the folder
+ C:\LyX\lyx-20\development\cmake
+   - To build LyX with debugging information for development, 
execute

+ the build script with the command
+ build devel
+   - To build LyX for a release, execute
+ the script with the command
+ build install
+
+7  Copy dependencies
+
+   Copy
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\bin
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\imagemagick
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\python
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\ghostscript
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\Resources
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)

And copy from the Qt bin directory
-   (e.g. C:\Qt\qt-everywhere-opensource-src-4.7.1\bin)
+   (e.g. C:\Qt\bin)
QtCore4.dll
QtGui4.dll
QtCore4d.dll (if compiling Debug version)
QtGui4d.dll (if compiling Debug version)
-   to C:\LyX\lyx-20-install\bin
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)




Why did you change this ?

IMHO the description is incomplete and not easier. It suddenly 
requires CMakeScript, it doesn't generate a Visual studio file, it 
doesn't download the dependencies automatically. And instead of 
changing the options in the CMake GUI you suddenly prefer to modify a 
batch file. This means that people won't see the options that can be 
changed by a single mouseclick.


You should have discussed this before changing it completely.

Vincent




Apparently I did notice this change, and I complained about it, but 
there was no response. Then I just forgot to revert this change.


Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 15-6-2012 11:52, Vincent van Ravesteijn schreef:

Op 19-3-2012 10:00, Vincent van Ravesteijn schreef:

Op 18-3-2012 23:59, uwesto...@lyx.org schreef:

Author: Uwe Stöhr
Date: Sun, 18 Mar 2012 23:59:03 +0100
New Commit: eeda1c099ed55d6883f8f4f59accd61fc8a4fc64
URL: 
http://git.lyx.org/?p=lyx.git;a=commit;h=eeda1c099ed55d6883f8f4f59accd61fc8a4fc64


Log:
- INSTALL.Win32: revise and update the description because since Qt 
4.8 it mustn't be compiled (and can currently also not without a lot 
of hacking). Moreover we have now a build script that does all the 
configuration in one step and we can benefit from the fast Ninja 
compilation


Signed-off-by: Uwe Stöhr

 4  Install CMake

-   Install the latest CMake from http://www.cmake.org
+   Install the latest CMakescript from
+   
http://sourceforge.net/projects/cmakescript/files/latest/download


 5  Configure

-   - Run the CMake GUI.
+   Open the script file build.bat that you find in your LyX folder
+   C:\LyX\lyx-20\development\cmake
+   with a text editor. Now:

-   - Set the source code path to C:\LyX\lyx-20
- Set the build path to C:\LyX\lyx-20-build
- Click Configure and set the generator to Visual Studio 10.
-
-   - Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
- Pre-compiled dependencies will automatically be downloaded.
+   - Change there "D:\Qt\bin" to the path where you installed Qt

-   - Set QT_QMAKE_EXECUTABLE to e.g.
- C:\Qt\qt-everywhere-opensource-src-4.7.1\bin\qmake.exe
- and Configure again.
-
-   - Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
- C:\LyX\lyx-20-install and click Configure.
-
-   - Check the Advanced checkbox.
- Set GETTEXT_MSGFMT_EXECUTABLE to
- 
C:\LyX\lyx-20-build\msvc2010-deps\deps20\gettext-tools\msgfmt.exe,

- and do the same for the other gettext tools.
-
-   - Click Generate.
+   - Set the GNUWIN32_DIR to "C:\LyX\lyx-20\msvc2010-deps"
+ (or wherever you have copied the LyX dependencies)
+   - Set the LYX_SOURCE to "C:\LyX\lyx-20"
+ (or wherever you have copied the LyX source files)
+   - Set the LYX_BUILD to "C:\LyX\lyx-20-build"
+ (or wherever you want to store the compilation result)
+
+   (- If you don't want to use the fast compilation mode for 
debug builds,

+  remove the statement "-GNinja".)

 6  Compile

-   A Microsoft Visual C++ solution should have been generated at
-   C:\LyX\lyx-20-build\lyx.sln
-   Compile the INSTALL project to get a LyX installation in
-   C:\LyX\lyx-20-install
-
-7   Copy dependencies
-
-Copy
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\bin
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\imagemagick
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\python
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\ghostscript
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\Resources
-   to C:\LyX\lyx-20-install
+   - Open a MSVC Command prompt via Windows' start menu and switch
+ to the folder
+ C:\LyX\lyx-20\development\cmake
+   - To build LyX with debugging information for development, 
execute

+ the build script with the command
+ build devel
+   - To build LyX for a release, execute
+ the script with the command
+ build install
+
+7  Copy dependencies
+
+   Copy
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\bin
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\imagemagick
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\python
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\ghostscript
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\Resources
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)

And copy from the Qt bin directory
-   (e.g. C:\Qt\qt-everywhere-opensource-src-4.7.1\bin)
+   (e.g. C:\Qt\bin)
QtCore4.dll
QtGui4.dll
QtCore4d.dll (if compiling Debug version)
QtGui4d.dll (if compiling Debug version)
-   to C:\LyX\lyx-20-install\bin
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)




Why did you change this ?

IMHO the description is incomplete and not easier. It suddenly 
requires CMakeScript, it doesn't generate a Visual studio file, it 
doesn't download the dependencies automatically. And instead of 
changing the options in the CMake GUI you suddenly prefer to modify a 
batch file. This means that people won't see the options that can be 
changed by a single mouseclick.


You should have discussed this before changing it completely.

Vincent




Apparently I did notice this change, and I complained about it, but 
there was no response. Then I just forgot to revert this change.


Vincent


 Sorry, there was a response, but it just didn't convince 

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Uwe Stöhr]

Am 20.03.2012 10:04, schrieb Vincent van Ravesteijn:


What is incomplete?
I changed it because it didn't work anymore. With Qt 4.8 things have changed 
and Peter did a good
job with the script so that the former manual settings are now automatically 
set.


It still worked perfectly for me. What didn't work anymore ?


You cannot compile Qt 4.8 as described. First you will stumble over the problem that a window pops 
up telling you that you have to install Perl. This is a known bug of the Qt package. But even if you 
put in the workaround fix, you will stumble over compilation errors for which one can again find 
workarounds. Finally I found out that the precompiled Qt 4.8.0 comes already with all you need and 
now supports MSVC 2010. So in fact handling Qt is now as simple as installing a program with a few 
clicks.



Which settings had to be set manually
which are now set automatically ?


The CMAKE variable settings, see the diff of my change for a list of them. (All 
;-) )


At some point you say where you copied the dependencies to. I have no idea 
what you mean with this.


This  was also not clear in the old version. I now added a further step:


It suddenly requires CMakeScript


This is the official CMake release plus a script that is provided directly by 
Peter. So we have
the maintainer in our team.


I'm not sure whether Peter is still in our team.


I think yes.


If you were a CMake expert, ok. But if there is a CMake problem, you come to 
the list and ask others
to fix it. Now suddenly you promote tools which are only used by yourself.


Peter suggested it and it works much faster, in my opinio this is an advantage. If you don#t like 
the script, you still can either use CMAKE without the script of the version I linked and remove the 
ninja option as I described. For security reasons the build script doesn't use it for release 
builds. (However I could find an issue.)


The Install.Win32 file is for new developers. I guess existing developers will never read it as they 
already have their setup. So I tried to make it as simple as possible.



No other developer have
ever heard of CMakeScript before, let alone about Ninja. You nowhere even 
explains what Ninja is ?


It is an alternative to Make. I also don't know the details how it internally sets up filelists and 
dependencies and don't want to. But what I see is that compiling LyX using Ninja is much faster and 
thus saves a lot of time. Just check it out.



Have you tried it? It generates studio files and solutions for debugging too.


No,


Why are you then telling it does not?


but you don't mention it at all in the file.


I'm using MSVC since the beginning and I would not have accepted it if I could not debug with MSVC. 
Why should I explicitly mention the solution files? I can but for just compiling LyX you don't need 
them. If you want to debug LyX you will but the Install-Win32 file was not about debugging LyX. But 
if you like I can add a section about this.


 I'm afraid that this will generate a merged build by default which is rather 
useless to use in
 MSVC.

Please test and then be afraid.


Why do you then have to manually supply the path to the dependencies ? The 
previous workflow did
this automatically.


If you don't have then or the path to them is not correct they will be downloaded. But it might be 
that you already have them. Then you don't need them twice. For example I started compiling master 
and got the dependencies. But when compiling branch they would be downloaded again. But to save disk 
space I changed the build script in my branch checkout to the folder of the dependencies that were 
downloaded once for master.
Maybe my description is not clear enough or I indeed have a bug in the script, thus please test and 
I'll fix it or you can change the description to make things more clear.



In what way do you have to be a CMake expert to use the GUI ? Start the gui, 
browse to the correct
folder, and check some options. What is difficult ?


Maybe you remember that I had to ask on the list how this is done. And when switching to branch or 
from branch I had to do this again.



CMake searched for Qt, so if it could find it,
there was no need to supply it manually. The GNUWin32 directory was set 
automatically.


Not on my setup.


So, you
prefer to do this all manually ?


You only have to set the path once and never again when switching between branches. This is much, 
much easier and I don't need to learn the different names of Cmake variables.



Why wouldn't the CMake GUI allow you to compile master and branch parallel ?


I never managed to get this and on this list I was told that this doesn't work and so a script was 
proposed.



It doesn't make sense
that you would want to compile both with the same settings.


I do this since 2 years. Why should I use different settings? I only need to distinguish between 
release and debug builds, but for this you can call the build script with different 

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Uwe Stöhr]

Am 20.03.2012 10:04, schrieb Vincent van Ravesteijn:


What is incomplete?
I changed it because it didn't work anymore. With Qt 4.8 things have changed 
and Peter did a good
job with the script so that the former manual settings are now automatically 
set.


It still worked perfectly for me. What didn't work anymore ?


You cannot compile Qt 4.8 as described. First you will stumble over the problem that a window pops 
up telling you that you have to install Perl. This is a known bug of the Qt package. But even if you 
put in the workaround fix, you will stumble over compilation errors for which one can again find 
workarounds. Finally I found out that the precompiled Qt 4.8.0 comes already with all you need and 
now supports MSVC 2010. So in fact handling Qt is now as simple as installing a program with a few 
clicks.



Which settings had to be set manually
which are now set automatically ?


The CMAKE variable settings, see the diff of my change for a list of them. (All 
;-) )


At some point you say "where you copied the dependencies to". I have no idea 
what you mean with this.


This  was also not clear in the old version. I now added a further step:


It suddenly requires CMakeScript


This is the official CMake release plus a script that is provided directly by 
Peter. So we have
the maintainer in our team.


I'm not sure whether Peter is still in our team.


I think yes.


If you were a CMake expert, ok. But if there is a CMake problem, you come to 
the list and ask others
to fix it. Now suddenly you promote tools which are only used by yourself.


Peter suggested it and it works much faster, in my opinio this is an advantage. If you don#t like 
the script, you still can either use CMAKE without the script of the version I linked and remove the 
ninja option as I described. For security reasons the build script doesn't use it for release 
builds. (However I could find an issue.)


The Install.Win32 file is for new developers. I guess existing developers will never read it as they 
already have their setup. So I tried to make it as simple as possible.



No other developer have
ever heard of CMakeScript before, let alone about Ninja. You nowhere even 
explains what Ninja is ?


It is an alternative to Make. I also don't know the details how it internally sets up filelists and 
dependencies and don't want to. But what I see is that compiling LyX using Ninja is much faster and 
thus saves a lot of time. Just check it out.



Have you tried it? It generates studio files and solutions for debugging too.


No,


Why are you then telling it does not?


but you don't mention it at all in the file.


I'm using MSVC since the beginning and I would not have accepted it if I could not debug with MSVC. 
Why should I explicitly mention the solution files? I can but for just compiling LyX you don't need 
them. If you want to debug LyX you will but the Install-Win32 file was not about debugging LyX. But 
if you like I can add a section about this.


> I'm afraid that this will generate a merged build by default which is rather 
useless to use in
> MSVC.

Please test and then be afraid.


Why do you then have to manually supply the path to the dependencies ? The 
previous workflow did
this automatically.


If you don't have then or the path to them is not correct they will be downloaded. But it might be 
that you already have them. Then you don't need them twice. For example I started compiling master 
and got the dependencies. But when compiling branch they would be downloaded again. But to save disk 
space I changed the build script in my branch checkout to the folder of the dependencies that were 
downloaded once for master.
Maybe my description is not clear enough or I indeed have a bug in the script, thus please test and 
I'll fix it or you can change the description to make things more clear.



In what way do you have to be a CMake expert to use the GUI ? Start the gui, 
browse to the correct
folder, and check some options. What is difficult ?


Maybe you remember that I had to ask on the list how this is done. And when switching to branch or 
from branch I had to do this again.



CMake searched for Qt, so if it could find it,
there was no need to supply it manually. The GNUWin32 directory was set 
automatically.


Not on my setup.


So, you
prefer to do this all manually ?


You only have to set the path once and never again when switching between branches. This is much, 
much easier and I don't need to learn the different names of Cmake variables.



Why wouldn't the CMake GUI allow you to compile master and branch parallel ?


I never managed to get this and on this list I was told that this doesn't work and so a script was 
proposed.



It doesn't make sense
that you would want to compile both with the same settings.


I do this since 2 years. Why should I use different settings? I only need to distinguish between 
release and debug builds, but for this you can call the build script with different 

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 20-3-2012 1:01, Uwe Stöhr schreef:

Am 19.03.2012 10:00, schrieb Vincent van Ravesteijn:


Why did you change this ?
IMHO the description is incomplete and not easier.


What is incomplete?
I changed it because it didn't work anymore. With Qt 4.8 things have 
changed and Peter did a good job with the script so that the former 
manual settings are now automatically set.


It still worked perfectly for me. What didn't work anymore ? Which 
settings had to be set manually which are now set automatically ?


At some point you say where you copied the dependencies to. I have no 
idea what you mean with this.





It suddenly requires CMakeScript


This is the official CMake release plus a script that is provided 
directly by Peter. So we have the maintainer in our team.


I'm not sure whether Peter is still in our team.

If you were a CMake expert, ok. But if there is a CMake problem, you 
come to the list and ask others to fix it. Now suddenly you promote 
tools which are only used by yourself. No other developer have ever 
heard of CMakeScript before, let alone about Ninja. You nowhere even 
explains what Ninja is ? What it does ? And it's strange to enable this 
by default. I guess this has something to do with a merged build, but 
this oftenly gets broken and needs repairing. I don't believe you know 
what to do if a merged build fails ? I find it strange to officially 
recommend a workflow by using tools that the developers themselves have 
not heard about.



, it doesn't generate a Visual studio file,


Have you tried it? It generates studio files and solutions for 
debugging too.


No, but you don't mention it at all in the file. I'm afraid that this 
will generate a merged build by default which is rather useless to use 
in MSVC.





it doesn't download the dependencies automatically.


Not true, it downloads them by default, please try.


Why do you then have to manually supply the path to the dependencies ? 
The previous workflow did this automatically.






And instead of
changing the options in the CMake GUI you suddenly prefer to modify a 
batch file. This means that

people won't see the options that can be changed by a single mouseclick.


If you are a CMake expert you don't need to use the script (especially 
you was opposed to it), but for new developers and people like me who 
are not familiar with CMake, the script is a huge progress. It also 
allows you to compile master and branch parallel without resetting 
several CMake options. Now you only need to set 3 folders in the 
script one time and that is it; no further change is necessary.


In what way do you have to be a CMake expert to use the GUI ? Start the 
gui, browse to the correct folder, and check some options. What is 
difficult ? CMake searched for Qt, so if it could find it, there was no 
need to supply it manually. The GNUWin32 directory was set 
automatically. So, you prefer to do this all manually ?


Why wouldn't the CMake GUI allow you to compile master and branch 
parallel ? It doesn't make sense that you would want to compile both 
with the same settings.





You should have discussed this before changing it completely.


Sure, ashes on me. I had some discussions with Peter and getting Qt 
4.8 took me several hours 


Why would getting Qt 4.8 takes you several hours ? You must have been 
doing something wrong. Apparently your discussions are in private, fine 
with me. But that's not a good reason to change things without notiying 
anyone else.


so that I originally would only have changed the Qt part. 


I really have no clue what changed about the Qt part. Other than that 
you can download precompiled binaries since Qt 4.8. This only makes it 
easier me thinks.


Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 20-3-2012 1:01, Uwe Stöhr schreef:

Am 19.03.2012 10:00, schrieb Vincent van Ravesteijn:


Why did you change this ?
IMHO the description is incomplete and not easier.


What is incomplete?
I changed it because it didn't work anymore. With Qt 4.8 things have 
changed and Peter did a good job with the script so that the former 
manual settings are now automatically set.


It still worked perfectly for me. What didn't work anymore ? Which 
settings had to be set manually which are now set automatically ?


At some point you say "where you copied the dependencies to". I have no 
idea what you mean with this.





It suddenly requires CMakeScript


This is the official CMake release plus a script that is provided 
directly by Peter. So we have the maintainer in our team.


I'm not sure whether Peter is still in our team.

If you were a CMake expert, ok. But if there is a CMake problem, you 
come to the list and ask others to fix it. Now suddenly you promote 
tools which are only used by yourself. No other developer have ever 
heard of CMakeScript before, let alone about Ninja. You nowhere even 
explains what Ninja is ? What it does ? And it's strange to enable this 
by default. I guess this has something to do with a merged build, but 
this oftenly gets broken and needs repairing. I don't believe you know 
what to do if a merged build fails ? I find it strange to officially 
recommend a workflow by using tools that the developers themselves have 
not heard about.



, it doesn't generate a Visual studio file,


Have you tried it? It generates studio files and solutions for 
debugging too.


No, but you don't mention it at all in the file. I'm afraid that this 
will generate a merged build by default which is rather useless to use 
in MSVC.





it doesn't download the dependencies automatically.


Not true, it downloads them by default, please try.


Why do you then have to manually supply the path to the dependencies ? 
The previous workflow did this automatically.






And instead of
changing the options in the CMake GUI you suddenly prefer to modify a 
batch file. This means that

people won't see the options that can be changed by a single mouseclick.


If you are a CMake expert you don't need to use the script (especially 
you was opposed to it), but for new developers and people like me who 
are not familiar with CMake, the script is a huge progress. It also 
allows you to compile master and branch parallel without resetting 
several CMake options. Now you only need to set 3 folders in the 
script one time and that is it; no further change is necessary.


In what way do you have to be a CMake expert to use the GUI ? Start the 
gui, browse to the correct folder, and check some options. What is 
difficult ? CMake searched for Qt, so if it could find it, there was no 
need to supply it manually. The GNUWin32 directory was set 
automatically. So, you prefer to do this all manually ?


Why wouldn't the CMake GUI allow you to compile master and branch 
parallel ? It doesn't make sense that you would want to compile both 
with the same settings.





You should have discussed this before changing it completely.


Sure, ashes on me. I had some discussions with Peter and getting Qt 
4.8 took me several hours 


Why would getting Qt 4.8 takes you several hours ? You must have been 
doing something wrong. Apparently your discussions are in private, fine 
with me. But that's not a good reason to change things without notiying 
anyone else.


so that I originally would only have changed the Qt part. 


I really have no clue what changed about the Qt part. Other than that 
you can download precompiled binaries since Qt 4.8. This only makes it 
easier me thinks.


Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 18-3-2012 23:59, uwesto...@lyx.org schreef:

Author: Uwe Stöhruwesto...@lyx.org
Date: Sun, 18 Mar 2012 23:59:03 +0100
New Commit: eeda1c099ed55d6883f8f4f59accd61fc8a4fc64
URL: 
http://git.lyx.org/?p=lyx.git;a=commit;h=eeda1c099ed55d6883f8f4f59accd61fc8a4fc64

Log:
- INSTALL.Win32: revise and update the description because since Qt 4.8 it 
mustn't be compiled (and can currently also not without a lot of hacking). 
Moreover we have now a build script that does all the configuration in one step 
and we can benefit from the fast Ninja compilation

Signed-off-by: Uwe Stöhruwesto...@lyx.org

 4  Install CMake

-   Install the latest CMake from http://www.cmake.org
+   Install the latest CMakescript from
+   http://sourceforge.net/projects/cmakescript/files/latest/download

 5  Configure

-   - Run the CMake GUI.
+   Open the script file build.bat that you find in your LyX folder
+   C:\LyX\lyx-20\development\cmake
+   with a text editor. Now:

-   - Set the source code path to C:\LyX\lyx-20
- Set the build path to C:\LyX\lyx-20-build
- Click Configure and set the generator to Visual Studio 10.
-
-   - Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
- Pre-compiled dependencies will automatically be downloaded.
+   - Change there D:\Qt\bin to the path where you installed Qt

-   - Set QT_QMAKE_EXECUTABLE to e.g.
- C:\Qt\qt-everywhere-opensource-src-4.7.1\bin\qmake.exe
- and Configure again.
-
-   - Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
- C:\LyX\lyx-20-install and click Configure.
-
-   - Check the Advanced checkbox.
- Set GETTEXT_MSGFMT_EXECUTABLE to
- 
C:\LyX\lyx-20-build\msvc2010-deps\deps20\gettext-tools\msgfmt.exe,

- and do the same for the other gettext tools.
-
-   - Click Generate.
+   - Set the GNUWIN32_DIR to C:\LyX\lyx-20\msvc2010-deps
+ (or wherever you have copied the LyX dependencies)
+   - Set the LYX_SOURCE to C:\LyX\lyx-20
+ (or wherever you have copied the LyX source files)
+   - Set the LYX_BUILD to C:\LyX\lyx-20-build
+ (or wherever you want to store the compilation result)
+
+   (- If you don't want to use the fast compilation mode for 
debug builds,

+  remove the statement -GNinja.)

 6  Compile

-   A Microsoft Visual C++ solution should have been generated at
-   C:\LyX\lyx-20-build\lyx.sln
-   Compile the INSTALL project to get a LyX installation in
-   C:\LyX\lyx-20-install
-
-7   Copy dependencies
-
-Copy
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\bin
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\imagemagick
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\python
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\ghostscript
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\Resources
-   to C:\LyX\lyx-20-install
+   - Open a MSVC Command prompt via Windows' start menu and switch
+ to the folder
+ C:\LyX\lyx-20\development\cmake
+   - To build LyX with debugging information for development, execute
+ the build script with the command
+ build devel
+   - To build LyX for a release, execute
+ the script with the command
+ build install
+
+7  Copy dependencies
+
+   Copy
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\bin
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\imagemagick
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\python
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\ghostscript
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\Resources
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)

And copy from the Qt bin directory
-   (e.g. C:\Qt\qt-everywhere-opensource-src-4.7.1\bin)
+   (e.g. C:\Qt\bin)
QtCore4.dll
QtGui4.dll
QtCore4d.dll (if compiling Debug version)
QtGui4d.dll (if compiling Debug version)
-   to C:\LyX\lyx-20-install\bin
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)




Why did you change this ?

IMHO the description is incomplete and not easier. It suddenly requires 
CMakeScript, it doesn't generate a Visual studio file, it doesn't 
download the dependencies automatically. And instead of changing the 
options in the CMake GUI you suddenly prefer to modify a batch file. 
This means that people won't see the options that can be changed by a 
single mouseclick.


You should have discussed this before changing it completely.

Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Uwe Stöhr]

Am 19.03.2012 10:00, schrieb Vincent van Ravesteijn:


Why did you change this ?
IMHO the description is incomplete and not easier.


What is incomplete?
I changed it because it didn't work anymore. With Qt 4.8 things have changed and Peter did a good 
job with the script so that the former manual settings are now automatically set.



It suddenly requires CMakeScript


This is the official CMake release plus a script that is provided directly by Peter. So we have the 
maintainer in our team.



, it doesn't
generate a Visual studio file,


Have you tried it? It generates studio files and solutions for debugging too.


it doesn't download the dependencies automatically.


Not true, it downloads them by default, please try.


And instead of
changing the options in the CMake GUI you suddenly prefer to modify a batch 
file. This means that
people won't see the options that can be changed by a single mouseclick.


If you are a CMake expert you don't need to use the script (especially you was opposed to it), but 
for new developers and people like me who are not familiar with CMake, the script is a huge 
progress. It also allows you to compile master and branch parallel without resetting several CMake 
options. Now you only need to set 3 folders in the script one time and that is it; no further change 
is necessary.



You should have discussed this before changing it completely.


Sure, ashes on me. I had some discussions with Peter and getting Qt 4.8 took me several hours so 
that I originally would only have changed the Qt part. But as I was at it I just did it completely. 
(A bit forcing indeed ;-) but much less forcing than the change to Git.)


regards Uwe

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Vincent van Ravesteijn]

Op 18-3-2012 23:59, uwesto...@lyx.org schreef:

Author: Uwe Stöhr
Date: Sun, 18 Mar 2012 23:59:03 +0100
New Commit: eeda1c099ed55d6883f8f4f59accd61fc8a4fc64
URL: 
http://git.lyx.org/?p=lyx.git;a=commit;h=eeda1c099ed55d6883f8f4f59accd61fc8a4fc64

Log:
- INSTALL.Win32: revise and update the description because since Qt 4.8 it 
mustn't be compiled (and can currently also not without a lot of hacking). 
Moreover we have now a build script that does all the configuration in one step 
and we can benefit from the fast Ninja compilation

Signed-off-by: Uwe Stöhr

 4  Install CMake

-   Install the latest CMake from http://www.cmake.org
+   Install the latest CMakescript from
+   http://sourceforge.net/projects/cmakescript/files/latest/download

 5  Configure

-   - Run the CMake GUI.
+   Open the script file build.bat that you find in your LyX folder
+   C:\LyX\lyx-20\development\cmake
+   with a text editor. Now:

-   - Set the source code path to C:\LyX\lyx-20
- Set the build path to C:\LyX\lyx-20-build
- Click Configure and set the generator to Visual Studio 10.
-
-   - Enable LYX_DEPENDENCIES_DOWNLOAD and click Configure.
- Pre-compiled dependencies will automatically be downloaded.
+   - Change there "D:\Qt\bin" to the path where you installed Qt

-   - Set QT_QMAKE_EXECUTABLE to e.g.
- C:\Qt\qt-everywhere-opensource-src-4.7.1\bin\qmake.exe
- and Configure again.
-
-   - Enable the LYX_INSTALL option, set CMAKE_INSTALL_PREFIX to
- C:\LyX\lyx-20-install and click Configure.
-
-   - Check the Advanced checkbox.
- Set GETTEXT_MSGFMT_EXECUTABLE to
- 
C:\LyX\lyx-20-build\msvc2010-deps\deps20\gettext-tools\msgfmt.exe,

- and do the same for the other gettext tools.
-
-   - Click Generate.
+   - Set the GNUWIN32_DIR to "C:\LyX\lyx-20\msvc2010-deps"
+ (or wherever you have copied the LyX dependencies)
+   - Set the LYX_SOURCE to "C:\LyX\lyx-20"
+ (or wherever you have copied the LyX source files)
+   - Set the LYX_BUILD to "C:\LyX\lyx-20-build"
+ (or wherever you want to store the compilation result)
+
+   (- If you don't want to use the fast compilation mode for 
debug builds,

+  remove the statement "-GNinja".)

 6  Compile

-   A Microsoft Visual C++ solution should have been generated at
-   C:\LyX\lyx-20-build\lyx.sln
-   Compile the INSTALL project to get a LyX installation in
-   C:\LyX\lyx-20-install
-
-7   Copy dependencies
-
-Copy
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\bin
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\imagemagick
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\python
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\ghostscript
-   - C:\LyX\lyx-20-build\msvc2010-deps\deps20\Resources
-   to C:\LyX\lyx-20-install
+   - Open a MSVC Command prompt via Windows' start menu and switch
+ to the folder
+ C:\LyX\lyx-20\development\cmake
+   - To build LyX with debugging information for development, execute
+ the build script with the command
+ build devel
+   - To build LyX for a release, execute
+ the script with the command
+ build install
+
+7  Copy dependencies
+
+   Copy
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\bin
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\imagemagick
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\python
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\ghostscript
+   - C:\LyX\lyx-20\msvc2010-deps\deps20\Resources
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)

And copy from the Qt bin directory
-   (e.g. C:\Qt\qt-everywhere-opensource-src-4.7.1\bin)
+   (e.g. C:\Qt\bin)
QtCore4.dll
QtGui4.dll
QtCore4d.dll (if compiling Debug version)
QtGui4d.dll (if compiling Debug version)
-   to C:\LyX\lyx-20-install\bin
+   to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
+   or to C:\LyX\lyx-20-build\bin\Debug (debug build)




Why did you change this ?

IMHO the description is incomplete and not easier. It suddenly requires 
CMakeScript, it doesn't generate a Visual studio file, it doesn't 
download the dependencies automatically. And instead of changing the 
options in the CMake GUI you suddenly prefer to modify a batch file. 
This means that people won't see the options that can be changed by a 
single mouseclick.


You should have discussed this before changing it completely.

Vincent

Re: [lyx/refs/heads/master] - INSTALL.Win32: revise and update the description because since Qt 4.8 it mustn't be compiled (and can currently also not without a lot of hacking). Moreover we have now a

[Uwe Stöhr]

Am 19.03.2012 10:00, schrieb Vincent van Ravesteijn:


Why did you change this ?
IMHO the description is incomplete and not easier.


What is incomplete?
I changed it because it didn't work anymore. With Qt 4.8 things have changed and Peter did a good 
job with the script so that the former manual settings are now automatically set.



It suddenly requires CMakeScript


This is the official CMake release plus a script that is provided directly by Peter. So we have the 
maintainer in our team.



, it doesn't
generate a Visual studio file,


Have you tried it? It generates studio files and solutions for debugging too.


it doesn't download the dependencies automatically.


Not true, it downloads them by default, please try.


And instead of
changing the options in the CMake GUI you suddenly prefer to modify a batch 
file. This means that
people won't see the options that can be changed by a single mouseclick.


If you are a CMake expert you don't need to use the script (especially you was opposed to it), but 
for new developers and people like me who are not familiar with CMake, the script is a huge 
progress. It also allows you to compile master and branch parallel without resetting several CMake 
options. Now you only need to set 3 folders in the script one time and that is it; no further change 
is necessary.



You should have discussed this before changing it completely.


Sure, ashes on me. I had some discussions with Peter and getting Qt 4.8 took me several hours so 
that I originally would only have changed the Qt part. But as I was at it I just did it completely. 
(A bit forcing indeed ;-) but much less forcing than the change to Git.)


regards Uwe