>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I do believe that LyX 1.3.6 is looking like a realistic Angus> prospect :) What else is planned? Not much... Angus> I see that bugzilla comes up with five bugs in the 1.3.x Angus> series: http://tinyurl.com/7aghm Some of these would be very easy to fix. Angus> (Incidentally, Angus> http://bugzilla.lyx.org/buglist.cgi?target_milestone=1.3.6 Angus> comes up with only three bugs.) Because we do not plan to fix the others? Angus> I've managed to write a script to automate the process of Angus> producing a LyX/Win package. I describe below what it does; Angus> have I missed anything? It would be great to have an installer. I do not know how to do that, though. Angus> (I propose not to package python, perl or a shell environment. Angus> Instead I think we should tell people to go and get their own.) How big are these things? I think it would be better to package just what we need, like Ruurd did. This is much easier for users (unless the installer can grab the files for us). Angus> The script uses the MinGW/MinSYS environment and compiler. It Angus> asks whether the Qt and LyX cvs trees are up to date. (It's not Angus> easy to use TortoiseCVS from the command line.) It asks whether Angus> the Qt library has been compiled. (Qt/WinFree must be compiled Angus> from a cmd shell, not a mingw console.) It checks that Angus> qt-mt3.dll, libiconv-2.dll, mingw10.dll and clean_dvi.py exist. Angus> It compiles the dv2dt and dt2dv utilites. It compiles and Angus> installs the Aspell library. It compiles and installs LyX. It Angus> copies the dv2dt and dt2dv utilites, the .dlls and clean_dvi.py Angus> to the lyx package. It modifies the Resources/lyx/configure Angus> script to ensure that the generated .dvi file is usable. Looks good :) Why don't you compile qt as static? JMarc
