Re: Problem with INSTALL.Win32 -
[EMAIL PROTECTED] wrote: I think INSTALL.Win32 is seriously out of date and needs to be looked over by someonw who knows this stuff... Here's a patch where I'm *guessing* - it should *not* be applied as it is. I changed 'MinSYS' be changed into 'MSYS', is that correct? Does the procedure described in this file even work? Maybe the file should refer to the Windows installers that exist? /Christian Christian, Angus, Uwe, today I managed to compile LyX 1.4.0 using MinGW (as usual...). Ok, I had to use cygwin's automake but this won't be a problem for the final LyX 1.4 tar package. I cleaned up and updated my compile instructions (see attachment). If you like to, you can have a look at my file and update INSTALL.Win32 accordingly (sorry, I will have no time before next weekend). Please note that my compile instructions differ in two ways from what is described in INSTALL.Win32 and supported by the build scripts in ./development/Win32/...: - I link the Qt library statically rather than dynamically (link times are below 4 minutes on my 3 GHz machine). - I use Aspell 0.60.4 rather than 0.50.X (much fewer problems when building with MinGW) There seems to be an apparent bug in ./development/Win32/packaging/package_lyxwin.sh: AFAICS, LyX 1.4 no longer has a lyx directory in Resources. The script should be fixed independently from INSTALL.Win32. Does anybody volunteer? Michael 1 MinGW MSYS 1.1 Download the following packages from http://www.mingw.org/download.shtml binutils-2.16.91-...tar.gz gcc-core-3.4.5-...tar.gz gcc-g++-3.4.5-...tar.gz mingw32-make-3.80.0-3.tar.gz mingw-runtime-3.9.tar.gz mingw-utils-0.3.tar.gz MSYS-1.0.11-...exe msys-autoconf-2.59.tar.bz2 msys-automake-1.8.2.tar.bz2 msysDTK-1.0.1.exe msys-libtool-1.5.tar.bz2 w32api-3.6.tar.gz 1.2 Install in C:\MinGW binutils, gcc-core, gcc-g++, mingw32-make, mingw-runtime, mingw-utils, w32api 1.3 Install in C:\msys MSYS, msys-autoconf, msys-automake, msysDTK, msys-libtool -- 2. Gettext Libiconv 2.1 Download the following packages from http://www.gnu.org/software/gettext/gettext.html gettext-tools-0.13.1.bin.woe32.zip gettext-runtime-0.13.1.bin.woe32.zip libiconv-1.9.1.bin.woe32.zip 2.2 Extract the three packages in C:\MinGW -- 3 qtwin 3.1 Get the latest CVS version Open the MSYS window/bash. In your home directory, enter cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/qtwin login return (no password) cvs -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/qtwin co \ -r QT_WIN32_3_3_BRANCH qt-3 3.2 Compile a static (!) QT library (dynamic linking with MinGW causes nightmares!) Open Window command line (run cmd.exe) and enter cd path_to_your_qtwin_dir set QMAKESPEC=win32-g++ setenv.bat configure.bat -release -static -- 4. Aspell 4.1 Download the following packages from http://aspell.net/ aspell-0.60.4.tar.gz aspell6-en-6.0-0.tar.bz2 aspell6-de-20030222-1.tar.bz2 4.2 Extract all files in your MSYS home directory 4.3 Enter cd aspell-0.60.4 4.4 Edit file ./common/file_util.cpp: Add before line 29 #include asc_ctype.hpp 4.5 Enter ./configure --enable-static --disable-shared --prefix=c:/Programme/Aspell-0.60.4 make make install 4.6 Compile the German dictionary cd ../aspell6-de-20030222-1 export PATH=/c/Programme/Aspell-0.60.4/bin:$PATH ./configure make make install 4.7 Repeat 4.6 for the English dictionary -- 5. Compile the LyX sources (given as tar package) 5.1 Enter export LDFLAGS=-L/home/user/qt-3/lib -lqtmain -lqt-mt -lopengl32 -lglu32 -lkernel32 -luser32 -lgdi32 -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -limm32 -lwinmm -lwsock32 -lwinspool 5.2 Edit file ./configure: - Search for string -DQT_DLL; remove the complete line - Search for string -lqt-mt; 6 lines above, move conftest.$ac_ext in front of $CXXFLAGS ac_link='$CXX -o conftest$ac_exeext conftest.$ac_ext $CXXFLAGS $CPPFLAGS $LDFLAGS $LIBS 5' 5.3 Configure LyX export PATH=/c/Programme/Python23:$PATH (you need Python!) ./configure --without-x --with-aspell --with-extra-prefix=/c/Programme/Aspell-0.60.4 \ --with-frontend=qt --disable-maintainer-mode --disable-debug --enable-optimization \ --with-qt-dir=/home/user/qt-3 --prefix=/c/Programme/LyX-1.4 --disable-pch \ --disable-concept-checks --disable-stdlib-debug 5.4 Build LyX make make install 5.5 Create DTL tools cd ./development/Win32/packaging/dtl make 5.6
Re: Problem with INSTALL.Win32 -
Michael Gerz wrote: I cleaned up and updated my compile instructions (see attachment). If you like to, you can have a look at my file and update INSTALL.Win32 accordingly (sorry, I will have no time before next weekend). Thanks for these detailed instructions. Maybe it would be a good idea to update the old build_lyxwin script to automate parts of the process. If this is not going to happen, make sure that it's removed so it won't confuse people. Joost
Re: Problem with INSTALL.Win32 -
Joost Verburg [EMAIL PROTECTED] writes: Thanks for these detailed instructions. Maybe it would be a good idea to update the old build_lyxwin script to automate parts of the process. If this is not going to happen, make sure that it's removed so it won't confuse people. I'll try and do so tomorrow. Angus ps Michael, Vielen Dank!
Re: Problem with INSTALL.Win32 -
[EMAIL PROTECTED] wrote: I think INSTALL.Win32 is seriously out of date and needs to be looked over by someonw who knows this stuff... Here's a patch where I'm *guessing* - it should *not* be applied as it is. I changed 'MinSYS' be changed into 'MSYS', is that correct? Does the procedure described in this file even work? Maybe the file should refer to the Windows installers that exist? /Christian Christian, Angus, Uwe, today I managed to compile LyX 1.4.0 using MinGW (as usual...). Ok, I had to use cygwin's automake but this won't be a problem for the final LyX 1.4 tar package. I cleaned up and updated my compile instructions (see attachment). If you like to, you can have a look at my file and update INSTALL.Win32 accordingly (sorry, I will have no time before next weekend). Please note that my compile instructions differ in two ways from what is described in INSTALL.Win32 and supported by the build scripts in ./development/Win32/...: - I link the Qt library statically rather than dynamically (link times are below 4 minutes on my 3 GHz machine). - I use Aspell 0.60.4 rather than 0.50.X (much fewer problems when building with MinGW) There seems to be an apparent bug in ./development/Win32/packaging/package_lyxwin.sh: AFAICS, LyX 1.4 no longer has a "lyx" directory in "Resources". The script should be fixed independently from INSTALL.Win32. Does anybody volunteer? Michael 1 MinGW & MSYS 1.1 Download the following packages from http://www.mingw.org/download.shtml binutils-2.16.91-...tar.gz gcc-core-3.4.5-...tar.gz gcc-g++-3.4.5-...tar.gz mingw32-make-3.80.0-3.tar.gz mingw-runtime-3.9.tar.gz mingw-utils-0.3.tar.gz MSYS-1.0.11-...exe msys-autoconf-2.59.tar.bz2 msys-automake-1.8.2.tar.bz2 msysDTK-1.0.1.exe msys-libtool-1.5.tar.bz2 w32api-3.6.tar.gz 1.2 Install in C:\MinGW binutils, gcc-core, gcc-g++, mingw32-make, mingw-runtime, mingw-utils, w32api 1.3 Install in C:\msys MSYS, msys-autoconf, msys-automake, msysDTK, msys-libtool -- 2. Gettext & Libiconv 2.1 Download the following packages from http://www.gnu.org/software/gettext/gettext.html gettext-tools-0.13.1.bin.woe32.zip gettext-runtime-0.13.1.bin.woe32.zip libiconv-1.9.1.bin.woe32.zip 2.2 Extract the three packages in C:\MinGW -- 3 qtwin 3.1 Get the latest CVS version Open the MSYS window/bash. In your home directory, enter cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/qtwin login (no password) cvs -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/qtwin co \ -r QT_WIN32_3_3_BRANCH qt-3 3.2 Compile a static (!) QT library (dynamic linking with MinGW causes nightmares!) Open Window command line (run cmd.exe) and enter cd set QMAKESPEC=win32-g++ setenv.bat configure.bat -release -static -- 4. Aspell 4.1 Download the following packages from http://aspell.net/ aspell-0.60.4.tar.gz aspell6-en-6.0-0.tar.bz2 aspell6-de-20030222-1.tar.bz2 4.2 Extract all files in your MSYS home directory 4.3 Enter cd aspell-0.60.4 4.4 Edit file ./common/file_util.cpp: Add before line 29 #include "asc_ctype.hpp" 4.5 Enter ./configure --enable-static --disable-shared --prefix=c:/Programme/Aspell-0.60.4 make make install 4.6 Compile the German dictionary cd ../aspell6-de-20030222-1 export PATH=/c/Programme/Aspell-0.60.4/bin:$PATH ./configure make make install 4.7 Repeat 4.6 for the English dictionary -- 5. Compile the LyX sources (given as tar package) 5.1 Enter export LDFLAGS="-L/home/user/qt-3/lib -lqtmain -lqt-mt -lopengl32 -lglu32 -lkernel32 -luser32 -lgdi32 -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -limm32 -lwinmm -lwsock32 -lwinspool" 5.2 Edit file ./configure: - Search for string "-DQT_DLL"; remove the complete line - Search for string "-lqt-mt"; 6 lines above, move "conftest.$ac_ext" in front of "$CXXFLAGS" ac_link='$CXX -o conftest$ac_exeext conftest.$ac_ext $CXXFLAGS $CPPFLAGS $LDFLAGS $LIBS >&5' 5.3 Configure LyX export PATH=/c/Programme/Python23:$PATH (you need Python!) ./configure --without-x --with-aspell --with-extra-prefix=/c/Programme/Aspell-0.60.4 \ --with-frontend=qt --disable-maintainer-mode --disable-debug --enable-optimization \ --with-qt-dir=/home/user/qt-3 --prefix=/c/Programme/LyX-1.4 --disable-pch \ --disable-concept-checks --disable-stdlib-debug 5.4 Build LyX make make install 5.5 Create DTL tools cd ./development/Win32/packaging/dtl make 5.6 Package
Re: Problem with INSTALL.Win32 -
Michael Gerz wrote: > I cleaned up and updated my compile instructions (see attachment). If > you like to, you can have a look at my file and update INSTALL.Win32 > accordingly (sorry, I will have no time before next weekend). Thanks for these detailed instructions. Maybe it would be a good idea to update the old build_lyxwin script to automate parts of the process. If this is not going to happen, make sure that it's removed so it won't confuse people. Joost
Re: Problem with INSTALL.Win32 -
Joost Verburg <[EMAIL PROTECTED]> writes: > Thanks for these detailed instructions. Maybe it would be a good idea to > update the old build_lyxwin script to automate parts of the process. If > this is not going to happen, make sure that it's removed so it won't > confuse people. I'll try and do so tomorrow. Angus ps Michael, Vielen Dank!
Re: Problem with INSTALL.Win32 -
Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus, do you have any plans to work on the Win32 build scripts? IIRC the 1.3.7 and 1.4.0 files are not in sync. Angus I don't think that the 1.4 stuff has ever worked, because I Angus never ever could build LyX 1.4 with mingw/msys. Also, I think the instructions for win32 should be for tar.gz release, not svn. Of course, there should be additional instructions for people who build from svn. JMarc
Re: Problem with INSTALL.Win32 -
Paul a écrit : I've never used automake before (I don't do much in the way of programming) but I noticed that version 1.9.4 is available here: http://gnuwin32.sourceforge.net/packages/automake.htm Hum, this is a perl script not an executable. I installed it in the mingw directory and tried (under msys) to launch 'autogen.sh' from trunk svn. It stops with: Using automake (GNU automake) 1.9.4 Using autoconf (GNU Autoconf) 2.59 Locating GNU m4... /bin/m4 Generate acinclude.m4... done. aclocal not found -- aborting Someone has an idea? Thanks in advance, Abdel.
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes [EMAIL PROTECTED] writes: http://gnuwin32.sourceforge.net/packages/automake.htm Hum, this is a perl script not an executable. I installed it in the mingw directory and tried (under msys) to launch 'autogen.sh' from trunk svn. It stops with: Using automake (GNU automake) 1.9.4 Using autoconf (GNU Autoconf) 2.59 Locating GNU m4... /bin/m4 Generate acinclude.m4... done. aclocal not found -- aborting Someone has an idea? Thanks in advance, Abdel. The autotools are perl scripts, yes. However, if you're feeding a native Windows tool a file path like /foo/bar then it's quite likely to interpret that as switches, no? In other words, expect problems if you use this this tool from an msys environment. The people best placed to help are the mingw/msys people themselves... Angus
Re: Problem with INSTALL.Win32 -
Angus Leeming a écrit : Abdelrazak Younes [EMAIL PROTECTED] writes: http://gnuwin32.sourceforge.net/packages/automake.htm Hum, this is a perl script not an executable. I installed it in the mingw directory and tried (under msys) to launch 'autogen.sh' from trunk svn. It stops with: Using automake (GNU automake) 1.9.4 Using autoconf (GNU Autoconf) 2.59 Locating GNU m4... /bin/m4 Generate acinclude.m4... done. aclocal not found -- aborting Someone has an idea? Thanks in advance, Abdel. The autotools are perl scripts, yes. However, if you're feeding a native Windows tool a file path like /foo/bar then it's quite likely to interpret that as switches, no? I don't know. I see that there is no 'aclocal.m4' in my SVN repository while there is one in my CVS repository so I thought it was a SVN problem. In other words, expect problems if you use this this tool from an msys environment. The people best placed to help are the mingw/msys people themselves... I know but I have to subscribe to the list before posting... So I have postponed doing this until I have another email address. Thanks, Abdel.
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes [EMAIL PROTECTED] writes: The autotools are perl scripts, yes. However, if you're feeding a native Windows tool a file path like /foo/bar then it's quite likely to interpret that as switches, no? I don't know. I see that there is no 'aclocal.m4' in my SVN repository while there is one in my CVS repository so I thought it was a SVN problem. aclocal.m4 is a generated file. Requires aclocal to be installed and working. Not sure if aclocal is part of autoconf or automake. Angus
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes wrote: Paul a écrit : I've never used automake before (I don't do much in the way of programming) but I noticed that version 1.9.4 is available here: http://gnuwin32.sourceforge.net/packages/automake.htm I tried this version of automake as well. No success. Probably a path problem (/c/foo/bar vs. c:\foo\bar). I think it is wise to stick with the tools in the MSYS realm. I will re-compile lyx 1.4.0svn tonight (assuming that automake has been executed before). Regards, Michael
Re: Problem with INSTALL.Win32 -
Paul wrote: http://gnuwin32.sourceforge.net/packages/automake.htm I tested this version some time ago but I ran into a problem (I don't remember the details). Let's assume that Lars or JM have run automake before LyX 1.4.0 is shipped. Michael
Re: Problem with INSTALL.Win32 -
Angus Leeming wrote: I don't think that the 1.4 stuff has ever worked, because I never ever could build LyX 1.4 with mingw/msys. Really? Why did we have all the dynamic vs. static Qt lib discussion if you never managed to build 1.4.0? Michael
Re: Problem with INSTALL.Win32 -
Am Montag, 27. Februar 2006 18:49 schrieb Michael Gerz: Let's assume that Lars or JM have run automake before LyX 1.4.0 is shipped. We don't need to assume that, it is a must, part of the corresponding makefile rule and has happened so far for every release. Georg
Re: Problem with INSTALL.Win32 -
Michael Gerz [EMAIL PROTECTED] writes: Angus Leeming wrote: I don't think that the 1.4 stuff has ever worked, because I never ever could build LyX 1.4 with mingw/msys. Really? Why did we have all the dynamic vs. static Qt lib discussion if you never managed to build 1.4.0? Maybe I'm confused. I think that I did build LyX 1.4 once or twice once I'd managed to turn off the g++ safe iterators but the link time was over one hour with dynamic linking and about 50 minutes with static linking. I then went on to use Asger's VS2003 solution file and built the entire thing from scratch in about 20 minutes. I don't think I went back after that. Anyway, the dynamic / static conversation was relevant also to LyX 1.3.x... Angus
Re: Problem with INSTALL.Win32 -
Angus Leeming wrote: Maybe I'm confused. I think that I did build LyX 1.4 once or twice once I'd managed to turn off the g++ safe iterators but the link time was over one hour with dynamic linking and about 50 minutes with static linking. I then went on to use Asger's VS2003 solution file and built the entire thing from scratch in about 20 minutes. I don't think I went back after that. Anyway, the dynamic / static conversation was relevant also to LyX 1.3.x... Angus It is indeed true that MinGW is extremely slow and building takes several hours. However, since some Visual C++ functions differ slightly from the MinGW functions I had problems like console windows popping up after building with Visual C++. Did you manage to solve that? Joost
Re: Problem with INSTALL.Win32 -
Joost Verburg [EMAIL PROTECTED] writes: It is indeed true that MinGW is extremely slow and building takes several hours. However, since some Visual C++ functions differ slightly from the MinGW functions I had problems like console windows popping up after building with Visual C++. Did you manage to solve that? Never tried to. I never did much more than check that the thing launched with LyX 1.4. Almost all of the changes that I introduced into the 1.3 code base slotted straight into the 1.4 tree. Asger supplied a few bits 'n' bobs for the 1.4 tree but usually I just committed his code. Regards, Angus
Re: Problem with INSTALL.Win32 -
Jean-Marc Lasgouttes wrote: So, what is the situation wrt windows? Who is planning to provide binaries? How? - Michael Gerz wrote: I can have a look at Angus' scripts and see if they still work (with the exception of automake). -- SH: I used both Gerz' instructions and the Angus instructions to successfully build LyX1.4.0_pre3 with Minsys. Angus originally wrote the howto included with that release but perhaps somebody else tested it. The Angus originated instructions are a bit easier for the user to follow, no editing. -- INSTALL.Win32 INSTALL for Win32 From 1.4.0pre3 3.2 Compile the QT library $ cat my_configure.bat set QTDIR=J:\MinSys\home\Angus\qt3 set MINGW=J:\MinGW ... Now go read the README in development/Win32/packaging. .../development/Win32/packaging/README Packaging LyX 1.3.6 for Window Angus Leeming, 14 July 2005 - Regards, Stephen
Re: Problem with INSTALL.Win32 -
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: >> Angus, do you have any plans to work on the Win32 build scripts? >> IIRC the 1.3.7 and 1.4.0 files are not in sync. Angus> I don't think that the 1.4 stuff has ever worked, because I Angus> never ever could build LyX 1.4 with mingw/msys. Also, I think the instructions for win32 should be for tar.gz release, not svn. Of course, there should be additional instructions for people who build from svn. JMarc
Re: Problem with INSTALL.Win32 -
Paul a écrit : I've never used automake before (I don't do much in the way of programming) but I noticed that version 1.9.4 is available here: http://gnuwin32.sourceforge.net/packages/automake.htm Hum, this is a perl script not an executable. I installed it in the mingw directory and tried (under msys) to launch 'autogen.sh' from trunk svn. It stops with: Using automake (GNU automake) 1.9.4 Using autoconf (GNU Autoconf) 2.59 Locating GNU m4... /bin/m4 Generate acinclude.m4... done. aclocal not found -- aborting Someone has an idea? Thanks in advance, Abdel.
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes <[EMAIL PROTECTED]> writes: > > http://gnuwin32.sourceforge.net/packages/automake.htm > > Hum, this is a perl script not an executable. I installed it in the > mingw directory and tried (under msys) to launch 'autogen.sh' from trunk > svn. It stops with: > > Using automake (GNU automake) 1.9.4 > Using autoconf (GNU Autoconf) 2.59 > Locating GNU m4... /bin/m4 > Generate acinclude.m4... done. > aclocal not found -- aborting > > Someone has an idea? > > Thanks in advance, > Abdel. The autotools are perl scripts, yes. However, if you're feeding a native Windows tool a file path like /foo/bar then it's quite likely to interpret that as switches, no? In other words, expect problems if you use this this tool from an msys environment. The people best placed to help are the mingw/msys people themselves... Angus
Re: Problem with INSTALL.Win32 -
Angus Leeming a écrit : Abdelrazak Younes <[EMAIL PROTECTED]> writes: http://gnuwin32.sourceforge.net/packages/automake.htm Hum, this is a perl script not an executable. I installed it in the mingw directory and tried (under msys) to launch 'autogen.sh' from trunk svn. It stops with: Using automake (GNU automake) 1.9.4 Using autoconf (GNU Autoconf) 2.59 Locating GNU m4... /bin/m4 Generate acinclude.m4... done. aclocal not found -- aborting Someone has an idea? Thanks in advance, Abdel. The autotools are perl scripts, yes. However, if you're feeding a native Windows tool a file path like /foo/bar then it's quite likely to interpret that as switches, no? I don't know. I see that there is no 'aclocal.m4' in my SVN repository while there is one in my CVS repository so I thought it was a SVN problem. In other words, expect problems if you use this this tool from an msys environment. The people best placed to help are the mingw/msys people themselves... I know but I have to subscribe to the list before posting... So I have postponed doing this until I have another email address. Thanks, Abdel.
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes <[EMAIL PROTECTED]> writes: > > The autotools are perl scripts, yes. However, if you're feeding a > > native Windows tool a file path like /foo/bar then it's quite likely > > to interpret that as switches, no? > I don't know. I see that there is no 'aclocal.m4' in my SVN repository > while there is one in my CVS repository so I thought it was a SVN problem. aclocal.m4 is a generated file. Requires aclocal to be installed and working. Not sure if aclocal is part of autoconf or automake. Angus
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes wrote: Paul a écrit : I've never used automake before (I don't do much in the way of programming) but I noticed that version 1.9.4 is available here: http://gnuwin32.sourceforge.net/packages/automake.htm I tried this version of automake as well. No success. Probably a path problem (/c/foo/bar vs. c:\foo\bar). I think it is wise to stick with the tools in the MSYS realm. I will re-compile lyx 1.4.0svn tonight (assuming that automake has been executed before). Regards, Michael
Re: Problem with INSTALL.Win32 -
Paul wrote: http://gnuwin32.sourceforge.net/packages/automake.htm I tested this version some time ago but I ran into a problem (I don't remember the details). Let's assume that Lars or JM have run automake before LyX 1.4.0 is shipped. Michael
Re: Problem with INSTALL.Win32 -
Angus Leeming wrote: I don't think that the 1.4 stuff has ever worked, because I never ever could build LyX 1.4 with mingw/msys. Really? Why did we have all the dynamic vs. static Qt lib discussion if you never managed to build 1.4.0? Michael
Re: Problem with INSTALL.Win32 -
Am Montag, 27. Februar 2006 18:49 schrieb Michael Gerz: > Let's assume that Lars or JM have run automake before LyX 1.4.0 is shipped. We don't need to assume that, it is a must, part of the corresponding makefile rule and has happened so far for every release. Georg
Re: Problem with INSTALL.Win32 -
Michael Gerz <[EMAIL PROTECTED]> writes: > > Angus Leeming wrote: > > >I don't think that the 1.4 stuff has ever worked, because I never ever could > >build LyX 1.4 with mingw/msys. > > > > > Really? Why did we have all the dynamic vs. static Qt lib discussion if > you never managed to build 1.4.0? Maybe I'm confused. I think that I did build LyX 1.4 once or twice once I'd managed to turn off the g++ safe iterators but the link time was over one hour with dynamic linking and about 50 minutes with static linking. I then went on to use Asger's VS2003 solution file and built the entire thing from scratch in about 20 minutes. I don't think I went back after that. Anyway, the dynamic / static conversation was relevant also to LyX 1.3.x... Angus
Re: Problem with INSTALL.Win32 -
Angus Leeming wrote: Maybe I'm confused. I think that I did build LyX 1.4 once or twice once I'd managed to turn off the g++ safe iterators but the link time was over one hour with dynamic linking and about 50 minutes with static linking. I then went on to use Asger's VS2003 solution file and built the entire thing from scratch in about 20 minutes. I don't think I went back after that. Anyway, the dynamic / static conversation was relevant also to LyX 1.3.x... Angus It is indeed true that MinGW is extremely slow and building takes several hours. However, since some Visual C++ functions differ slightly from the MinGW functions I had problems like console windows popping up after building with Visual C++. Did you manage to solve that? Joost
Re: Problem with INSTALL.Win32 -
Joost Verburg <[EMAIL PROTECTED]> writes: > It is indeed true that MinGW is extremely slow and building takes > several hours. However, since some Visual C++ functions differ slightly > from the MinGW functions I had problems like console windows popping up > after building with Visual C++. Did you manage to solve that? Never tried to. I never did much more than check that the thing launched with LyX 1.4. Almost all of the changes that I introduced into the 1.3 code base slotted straight into the 1.4 tree. Asger supplied a few bits 'n' bobs for the 1.4 tree but usually I just committed his code. Regards, Angus
Re: Problem with INSTALL.Win32 -
Jean-Marc Lasgouttes wrote: "So, what is the situation wrt windows? Who is planning to provide binaries? How?" - Michael Gerz wrote: "I can have a look at Angus' scripts and see if they still work (with the exception of automake)." -- SH: I used both Gerz' instructions and the Angus instructions to successfully build LyX1.4.0_pre3 with Minsys. Angus originally wrote the howto included with that release but perhaps somebody else tested it. The Angus originated instructions are a bit easier for the user to follow, no editing. -- INSTALL.Win32 INSTALL for Win32 From 1.4.0pre3 3.2 Compile the QT library $ cat my_configure.bat set QTDIR=J:\MinSys\home\Angus\qt3 set MINGW=J:\MinGW ... "Now go read the README in development/Win32/packaging." .../development/Win32/packaging/README "Packaging LyX 1.3.6 for Window Angus Leeming, 14 July 2005" - Regards, Stephen
Re: Problem with INSTALL.Win32 -
Michael Gerz [EMAIL PROTECTED] writes: Joost Verburg wrote: INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin. However, the Windows build scripts also do not work in the current state. The reason is that automake 1.9 is not yet available for Windows. Currently I can only get it to compile using automake in a Cygwin environment and a modified build script that doesn't call automake. Angus, do you have any plans to work on the Win32 build scripts? IIRC the 1.3.7 and 1.4.0 files are not in sync. I don't think that the 1.4 stuff has ever worked, because I never ever could build LyX 1.4 with mingw/msys. Angus
Re: Problem with INSTALL.Win32 -
I've never used automake before (I don't do much in the way of programming) but I noticed that version 1.9.4 is available here: http://gnuwin32.sourceforge.net/packages/automake.htm The website says: The GnuWin32 project provides Win32-versions of GNU tools, or tools with a similar open source licence. The ports are native ports, that is they rely only on libraries provided with any standard 32-bits MS-Windows operating system, such as MS-Windows 95 / 98 / ME / NT / 2000 / XP. Native ports do not rely on some kind of Unix emulation, such as CygWin or Msys, so that there is no need to install additional emulation libraries. At present, all developments have been done under MS-Windows 98 and XP, using the Mingw port of the GNU C and C++ (GCC) compilers.
Re: Problem with INSTALL.Win32 -
Michael Gerz <[EMAIL PROTECTED]> writes: > > Joost Verburg wrote: > > > INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin. > > > > However, the Windows build scripts also do not work in the current > > state. The reason is that automake 1.9 is not yet available for > > Windows. Currently I can only get it to compile using automake in a > > Cygwin environment and a modified build script that doesn't call > > automake. > > Angus, do you have any plans to work on the Win32 build scripts? IIRC > the 1.3.7 and 1.4.0 files are not in sync. I don't think that the 1.4 stuff has ever worked, because I never ever could build LyX 1.4 with mingw/msys. Angus
Re: Problem with INSTALL.Win32 -
I've never used automake before (I don't do much in the way of programming) but I noticed that version 1.9.4 is available here: http://gnuwin32.sourceforge.net/packages/automake.htm The website says: The GnuWin32 project provides Win32-versions of GNU tools, or tools with a similar open source licence. The ports are native ports, that is they rely only on libraries provided with any standard 32-bits MS-Windows operating system, such as MS-Windows 95 / 98 / ME / NT / 2000 / XP. Native ports do not rely on some kind of Unix emulation, such as CygWin or Msys, so that there is no need to install additional emulation libraries. At present, all developments have been done under MS-Windows 98 and XP, using the Mingw port of the GNU C and C++ (GCC) compilers.
Re: Problem with INSTALL.Win32 -
On Fri, Feb 24, 2006 at 11:48:20AM +0100, Joost Verburg wrote: However, the Windows build scripts also do not work in the current state. The reason is that automake 1.9 is not yet available for Windows. Why do we need automake 1.9 at all? I.e. waht crucial feature of 1.9 do we and need to use? Andre'
Re: Problem with INSTALL.Win32 -
Andre == Andre Poenitz [EMAIL PROTECTED] writes: Andre On Fri, Feb 24, 2006 at 11:48:20AM +0100, Joost Verburg wrote: However, the Windows build scripts also do not work in the current state. The reason is that automake 1.9 is not yet available for Windows. Andre Why do we need automake 1.9 at all? Andre I.e. waht crucial feature of 1.9 do we and need to use? The ability to create tar files with paths longer than 100 characters. These are used because the Mac LyX.app directory has a really nested structure. I know, it is not a very good reason. JMarc
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes wrote: Building of svn version with current MSYS DTK is not possible because of old automake. But I guess that automake is not required for building a released candidate. Reading the user list, I see that some people managed to use Cygwin for that task too (using Qtwin port without X). So it's up to the packager to choose that way of the other. If you have MinGW and cygwin on your machine, you can use cygwin's automake and switch back to MinGW afterwards. I guess users won't need automake if they download the 1.4.0 tar file, right? I will go and ask the MinGW people for a recent automake. Who is planning to provide binaries? Me (for Uwe), unless Angus does. Michael
Re: Problem with INSTALL.Win32 -
Joost Verburg wrote: INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin. However, the Windows build scripts also do not work in the current state. The reason is that automake 1.9 is not yet available for Windows. Currently I can only get it to compile using automake in a Cygwin environment and a modified build script that doesn't call automake. Angus, do you have any plans to work on the Win32 build scripts? IIRC the 1.3.7 and 1.4.0 files are not in sync. Michael
Re: Problem with INSTALL.Win32 -
Jean-Marc Lasgouttes wrote: So, what is the situation wrt windows? Who is planning to provide binaries? How? Up to now, I used my self-made recipe to generate LyX binaries (see former discussion on static vs. dynamic qt library). I can have a look at Angus' scripts and see if they still work (with the exception of automake). Michael
Re: Problem with INSTALL.Win32 -
Enrico Forestieri a écrit : Abdelrazak Younes [EMAIL PROTECTED] writes: For Msys/mingw binaries, I might be able to help if needed. Packaging is something else... Uwe might propose something and Angus might come out of his retirement . I can see some well positioned outsiders (Enrico? Michael?). It is my intention to provide a cygwin package. I have already done that in the past for distributing LyX to my colleagues and I have no problem sharing it. And will you need to install cygwin to use this package?
Re: Problem with INSTALL.Win32 -
Michael Gerz a écrit : Abdelrazak Younes wrote: Building of svn version with current MSYS DTK is not possible because of old automake. But I guess that automake is not required for building a released candidate. Reading the user list, I see that some people managed to use Cygwin for that task too (using Qtwin port without X). So it's up to the packager to choose that way of the other. If you have MinGW and cygwin on your machine, you can use cygwin's automake and switch back to MinGW afterwards. I guess users won't need automake if they download the 1.4.0 tar file, right? That is my understanding yes. I will go and ask the MinGW people for a recent automake. I have tried to compile am-1.9 from mingwport but it won't even configure (complains about MSYS make or something). It would be very nice if they could provide a MSYS package. Abdel.
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes [EMAIL PROTECTED] writes: Enrico Forestieri a écrit : Abdelrazak Younes abdelrazak.younes.m3system at ... writes: For Msys/mingw binaries, I might be able to help if needed. Packaging is something else... Uwe might propose something and Angus might come out of his retirement . I can see some well positioned outsiders (Enrico? Michael?). It is my intention to provide a cygwin package. I have already done that in the past for distributing LyX to my colleagues and I have no problem sharing it. And will you need to install cygwin to use this package? Yes, of course. However, I think that it can be of interest only to those already using cygwin. The native version is a much better option for all non-cygwin users and I expect that nobody will install cygwin only for using a cygwin version of LyX ;-) -- Enrico
Re: Problem with INSTALL.Win32 -
On Fri, Feb 24, 2006 at 11:48:20AM +0100, Joost Verburg wrote: > However, the Windows build scripts also do not work in the current > state. The reason is that automake 1.9 is not yet available for Windows. Why do we need automake 1.9 at all? I.e. waht crucial feature of 1.9 do we and need to use? Andre'
Re: Problem with INSTALL.Win32 -
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes: Andre> On Fri, Feb 24, 2006 at 11:48:20AM +0100, Joost Verburg wrote: >> However, the Windows build scripts also do not work in the current >> state. The reason is that automake 1.9 is not yet available for >> Windows. Andre> Why do we need automake 1.9 at all? Andre> I.e. waht crucial feature of 1.9 do we and need to use? The ability to create tar files with paths longer than 100 characters. These are used because the Mac LyX.app directory has a really nested structure. I know, it is not a very good reason. JMarc
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes wrote: Building of svn version with current MSYS DTK is not possible because of old automake. But I guess that automake is not required for building a released candidate. Reading the user list, I see that some people managed to use Cygwin for that task too (using Qtwin port without X). So it's up to the packager to choose that way of the other. If you have MinGW and cygwin on your machine, you can use cygwin's automake and switch back to MinGW afterwards. I guess users won't need automake if they download the 1.4.0 tar file, right? I will go and ask the MinGW people for a recent automake. Who is planning to provide binaries? Me (for Uwe), unless Angus does. Michael
Re: Problem with INSTALL.Win32 -
Joost Verburg wrote: INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin. However, the Windows build scripts also do not work in the current state. The reason is that automake 1.9 is not yet available for Windows. Currently I can only get it to compile using automake in a Cygwin environment and a modified build script that doesn't call automake. Angus, do you have any plans to work on the Win32 build scripts? IIRC the 1.3.7 and 1.4.0 files are not in sync. Michael
Re: Problem with INSTALL.Win32 -
Jean-Marc Lasgouttes wrote: So, what is the situation wrt windows? Who is planning to provide binaries? How? Up to now, I used my self-made recipe to generate LyX binaries (see former discussion on "static" vs. "dynamic" qt library). I can have a look at Angus' scripts and see if they still work (with the exception of automake). Michael
Re: Problem with INSTALL.Win32 -
Enrico Forestieri a écrit : Abdelrazak Younes <[EMAIL PROTECTED]> writes: For Msys/mingw binaries, I might be able to help if needed. Packaging is something else... Uwe might propose something and Angus might come out of his retirement . I can see some well positioned outsiders (Enrico? Michael?). It is my intention to provide a cygwin package. I have already done that in the past for distributing LyX to my colleagues and I have no problem sharing it. And will you need to install cygwin to use this package?
Re: Problem with INSTALL.Win32 -
Michael Gerz a écrit : Abdelrazak Younes wrote: Building of svn version with current MSYS DTK is not possible because of old automake. But I guess that automake is not required for building a released candidate. Reading the user list, I see that some people managed to use Cygwin for that task too (using Qtwin port without X). So it's up to the packager to choose that way of the other. If you have MinGW and cygwin on your machine, you can use cygwin's automake and switch back to MinGW afterwards. I guess users won't need automake if they download the 1.4.0 tar file, right? That is my understanding yes. I will go and ask the MinGW people for a recent automake. I have tried to compile am-1.9 from mingwport but it won't even configure (complains about MSYS make or something). It would be very nice if they could provide a MSYS package. Abdel.
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes <[EMAIL PROTECTED]> writes: > > Enrico Forestieri a écrit : > > Abdelrazak Younes ...> writes: > > > >> For Msys/mingw binaries, I might be able to help if needed. Packaging is > >> something else... Uwe might propose something and Angus might come out > >> of his retirement . I can see some well positioned outsiders (Enrico? > >> Michael?). > > > > It is my intention to provide a cygwin package. I have already done that > > in the past for distributing LyX to my colleagues and I have no problem > > sharing it. > > And will you need to install cygwin to use this package? Yes, of course. However, I think that it can be of interest only to those already using cygwin. The native version is a much better option for all non-cygwin users and I expect that nobody will install cygwin only for using a cygwin version of LyX ;-) -- Enrico
Re: Problem with INSTALL.Win32 -
[EMAIL PROTECTED] wrote: Hi, I think INSTALL.Win32 is seriously out of date and needs to be looked over by someonw who knows this stuff... Here's a patch where I'm *guessing* - it should *not* be applied as it is. INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin. However, the Windows build scripts also do not work in the current state. The reason is that automake 1.9 is not yet available for Windows. Currently I can only get it to compile using automake in a Cygwin environment and a modified build script that doesn't call automake. Joost
Re: Problem with INSTALL.Win32 -
christian == christian ridderstrom [EMAIL PROTECTED] writes: christian Hi, I think INSTALL.Win32 is seriously out of date and christian needs to be looked over by someonw who knows this stuff... christian Here's a patch where I'm *guessing* - it should *not* be christian applied as it is. Well, it seems to make sense. Could some windows person comment? christian PS. The patch seems difficult for me to read, so if there's christian some magical options I need to give to 'svn diff', please christian let me know! No, it's OK. JMarc
Re: Problem with INSTALL.Win32 -
Joost == Joost Verburg [EMAIL PROTECTED] writes: Joost However, the Windows build scripts also do not work in the Joost current state. The reason is that automake 1.9 is not yet Joost available for Windows. Currently I can only get it to compile Joost using automake in a Cygwin environment and a modified build Joost script that doesn't call automake. So, what is the situation wrt windows? Who is planning to provide binaries? How? JMarc
Re: Problem with INSTALL.Win32 -
Jean-Marc Lasgouttes a écrit : Joost == Joost Verburg [EMAIL PROTECTED] writes: Joost However, the Windows build scripts also do not work in the Joost current state. The reason is that automake 1.9 is not yet Joost available for Windows. Currently I can only get it to compile Joost using automake in a Cygwin environment and a modified build Joost script that doesn't call automake. So, what is the situation wrt windows? Building of svn version with current MSYS DTK is not possible because of old automake. But I guess that automake is not required for building a released candidate. Reading the user list, I see that some people managed to use Cygwin for that task too (using Qtwin port without X). So it's up to the packager to choose that way of the other. Who is planning to provide binaries? For Msys/mingw binaries, I might be able to help if needed. Packaging is something else... Uwe might propose something and Angus might come out of his retirement ;-). I can see some well positioned outsiders (Enrico? Michael?). Abdel.
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes [EMAIL PROTECTED] writes: For Msys/mingw binaries, I might be able to help if needed. Packaging is something else... Uwe might propose something and Angus might come out of his retirement . I can see some well positioned outsiders (Enrico? Michael?). It is my intention to provide a cygwin package. I have already done that in the past for distributing LyX to my colleagues and I have no problem sharing it. -- Enrico
Re: Problem with INSTALL.Win32 -
[EMAIL PROTECTED] wrote: Hi, I think INSTALL.Win32 is seriously out of date and needs to be looked over by someonw who knows this stuff... Here's a patch where I'm *guessing* - it should *not* be applied as it is. INSTALL.Win32 is indeed outdated. It also points to the old kde-cygwin. However, the Windows build scripts also do not work in the current state. The reason is that automake 1.9 is not yet available for Windows. Currently I can only get it to compile using automake in a Cygwin environment and a modified build script that doesn't call automake. Joost
Re: Problem with INSTALL.Win32 -
> "christian" == christian ridderstrom <[EMAIL PROTECTED]> writes: christian> Hi, I think INSTALL.Win32 is seriously out of date and christian> needs to be looked over by someonw who knows this stuff... christian> Here's a patch where I'm *guessing* - it should *not* be christian> applied as it is. Well, it seems to make sense. Could some windows person comment? christian> PS. The patch seems difficult for me to read, so if there's christian> some magical options I need to give to 'svn diff', please christian> let me know! No, it's OK. JMarc
Re: Problem with INSTALL.Win32 -
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes: Joost> However, the Windows build scripts also do not work in the Joost> current state. The reason is that automake 1.9 is not yet Joost> available for Windows. Currently I can only get it to compile Joost> using automake in a Cygwin environment and a modified build Joost> script that doesn't call automake. So, what is the situation wrt windows? Who is planning to provide binaries? How? JMarc
Re: Problem with INSTALL.Win32 -
Jean-Marc Lasgouttes a écrit : "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes: Joost> However, the Windows build scripts also do not work in the Joost> current state. The reason is that automake 1.9 is not yet Joost> available for Windows. Currently I can only get it to compile Joost> using automake in a Cygwin environment and a modified build Joost> script that doesn't call automake. So, what is the situation wrt windows? Building of svn version with current MSYS DTK is not possible because of old automake. But I guess that automake is not required for building a released candidate. Reading the user list, I see that some people managed to use Cygwin for that task too (using Qtwin port without X). So it's up to the packager to choose that way of the other. Who is planning to provide binaries? For Msys/mingw binaries, I might be able to help if needed. Packaging is something else... Uwe might propose something and Angus might come out of his retirement ;-). I can see some well positioned outsiders (Enrico? Michael?). Abdel.
Re: Problem with INSTALL.Win32 -
Abdelrazak Younes <[EMAIL PROTECTED]> writes: > For Msys/mingw binaries, I might be able to help if needed. Packaging is > something else... Uwe might propose something and Angus might come out > of his retirement . I can see some well positioned outsiders (Enrico? > Michael?). It is my intention to provide a cygwin package. I have already done that in the past for distributing LyX to my colleagues and I have no problem sharing it. -- Enrico
