On 15-Jun-12 10:27 am, Vincent van Ravesteijn wrote:
Op 15-6-2012 11:04, Bogdan Roman schreef:
Why don't you use CMake directly ? That's the recommended way to compile
LyX on Windows.


Where's that recommendation? Right now the recommended way I see is
the INSTALL.Win32 file and other info pointing to it.

Yes, and this file reads: "5    Configure : Run the CMake GUI." The
build.bat script isn't mentioned in either INSTALL.Win32 or INSTALL.cmake.

The latest INSTALL.Win32 file that I pulled from Git is the one attached here. You can see how it reads and hence the confusion between our exchange. It's different than the one available in the SVN repo which was last updated 3 months ago (the last commit to the repo, not the install.win32 file), and which says to use CMake GUI. That's what I was trying to say.

I replied again previously and I think I responded to your other questions there (I agree re: arguments and editing the script).

Bogdan.


CMake GUI was used in the SVN era iirc,

Using CMake or not is independent of using SVN or git.

and it was quite cumbersome, having to manually fix several configure
stages. Ifyou're suggesting I use cmake from the command line then why
wouldn't I want to automate the arguments? The *nix scripts do ...

I don't understand. How can you automate arguments if these are
different for each user ?


This build.bat script is maintained by and tailored for a single
developer only and your patch is just making it work for you, but this
won't work in general. I vote for removing this script from the
repository completely.

The patch and comments are fixing general issues. Of course it will
work in general; the user needs to edit the paths to
qmake/build-dir/etc as indicated in the install.win32 file. With my
changes then the script will actually work when doing "build devel" or
"build install" rather than running into errors several times.


I don't understand. Why do you prefer to manually edit a batch file ?
CMake will ask you kindly when a path can't be found.

Vincent

Compiling LyX 2.0 for Win32 and creating Windows installer
==========================================================

It's recommended to compile LyX using Microsoft Visual C++ 2010 and CMake.
Pre-compiled packages with dependencies are provided for this environment.


Compiling with Microsoft Visual C++
===================================

        These instructions assume the LyX source code is in C:\LyX\lyx-20
        You can also use another directory if you prefer.

1       Install MSVC 2010

        If you don't have Visual C++ 2010 installed, get the free Express 
edition from
        http://www.microsoft.com/express/Downloads/

        (All dependencies are linked against the MSVC 2010 runtime and won't 
work in
        combination with MSVC 2008. You'll get crashes and other unexpected 
issues.)

2       Install Qt

        Download the latest Qt for Open Source C++ development on Windows 
(VS2010)
        from http://qt.nokia.com/downloads/windows-cpp-vs2010.

3       Install Python

        Install the latest Python 2.x version (not Python 3.x !) from
        http://www.python.org/download/

4       Install CMake

        Install the latest CMakescript from
        http://sourceforge.net/projects/cmakescript/files/latest/download

5       Configure

        Open the script file build.bat that you find in your LyX folder
        C:\LyX\lyx-20\development\cmake
        with a text editor. Now: 
         
        - Change there "D:\Qt\bin" to the path where you installed Qt
        
        - 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

        - 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\bin)
        QtCore4.dll
        QtGui4.dll
        QtCore4d.dll (if compiling Debug version)
        QtGui4d.dll (if compiling Debug version)
        to C:\LyX\lyx-20-build\LYX_INSTALLED\bin (install build)
        or to C:\LyX\lyx-20-build\bin\Debug (debug build)

8       Define path prefix

        Add the following line to C:\LyX\lyx-20-install\Resources\lyxrc.dist,
        so LyX will find the bundled tools such as Python, ImageMagick
        and Ghostscript:

        \path_prefix 
"$LyXDir\bin;$LyXDir\python;$LyXDir\imagemagick;$LyXDir\ghostscript"

        You may also add the location of your LaTeX installation if it's not on 
the
        system PATH, and the location of JabRef.

9       Start LyX

        C:\LyX\lyx-20-install\bin\lyx.exe


Creating the Installer
======================

        - Get NSIS from http://nsis.sourceforge.net
        - In the LyX source directory, go to 
development\Win32\packaging\installer
        - Check whether the file locations in settings.nsh match your setup.
        - Right-click on lyx.nsi and click "Compile NSIS Script".

Reply via email to