>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:

Angus> Jean-Marc, could you move it to the ftp site and fix the link
Angus> at http://wiki.lyx.org/Windows/LyX14x to point to its new home?

Done.

Angus> I managed to fix the problems that people were having running
Angus> this with localized menus; it turned out that my renaming of
Angus> lyx14x.exe to lyx.exe broke everything, so I no longer do that
Angus> ;-)

Could you expand on that?

Angus> I had to change a few things. Patch attached. Please apply to
Angus> the 14x tree:

Angus> 1. operations_posix_windows.cpp: change needed to enable
Angus> compilation against NewAPIs.h. Ie, LyX 1.4 will work for Win98
Angus> users. The patch isn't applicable to LyX 1.5.x because Lars has
Angus> upgraded boost and the patch to use NewAPIs.h never made it
Angus> into the official boost sources.

Applied.

Angus> 3. lyx_configure.C: Using the --with-version-suffix means that
Angus> the execuatble is no longer called lyx.exe so we have to be a
Angus> little clever when generating lyx.bat. The .bat file now refers
Angus> to the first file that matches lyx*.exe; seems to work
Angus> perfectly.

I'd rather apply the following patch instead (leave lyx.exe alone).
What do you think of it?

Angus> 4. lyx_installer.nsi: Recent versions of NSIS have changed the
Angus> sematics of how to invoke really efficient compression. The
Angus> change ensures that we continue to apply compression to
Angus> everything in one go rather than on individual files.

Applied.

JMarc

Index: config/lyxinclude.m4
===================================================================
--- config/lyxinclude.m4	(revision 13647)
+++ config/lyxinclude.m4	(working copy)
@@ -594,7 +594,6 @@
 	   mandir='${datadir}/man' ;;
   windows) AC_DEFINE(USE_WINDOWS_PACKAGING, 1, [Define to 1 if LyX should use a Windows-style file layout])
 	   PACKAGE=LyX${version_suffix}
-	   program_suffix=$version_suffix
 	   default_prefix="C:/Program Files/${PACKAGE}"
 	   bindir='${prefix}/bin'
 	   libdir='${prefix}/Resources'

Reply via email to