Michael Gerz wrote:
> Angus Leeming wrote:
>
>>Let's be clear: it's a kludge to get decent compile times using the MinGW
>>compiler. Let's also be clear: compile times are better for you, but not
>>significantly better for me.
>>
>>Uniting the scripts is a different issue. I'm sure that it's not beyond
>>the wit of man to modify development/Win32/packaging/build_lyxwin.sh so
>>that there are both static and dynamic routes. Usage:
>>
>>
> Angus, I don't think we have to support both static and dynamic linking.
> Maintaing one solution is enough. Let's keep it simple.
Shrug. What's hard about it. A little refactoring of a shell script is all
that's required.
> My problem is that dynamic linking doesn't real work on my machine (at
> least it didn't when I tried last time; I will check eventually whether
> things have improved recently). If you are able to provide us with a
> 1.4.X installer with a shared qtwin lib, I won't complain :-)
I'm afraid that I won't able to provide you with anything other than
advice.
> BTW: What will happen if you install a 1.4 package on a machine that
> already has 1.3 installed? Will your installer remove the old version or
> can both versions live on the same machine (beside the fact that LyX
> files are associated to one of the two versions). Does the
> deinstallation routine cope with two versions?
At the moment, you can't.
As far as I can see, the only problem is the fact that
~\Application Data\LyX
has the same name for both packages. If it were called
~\Application Data\LyX\1.3.x
or
~\Application Data\LyX\1.4.x
then you could install both painlessly.
If you were to do that, you'd probably want a third package containing only
C:\Program Files\LyXxtras\bin
dt2dv.exe
dv2dt.exe
libiconv-2.dll
mingwm10.dll
qt-mt3.dll
and have the lyx.bat in the 1.3 and 1.4 versions of the LyX package add
this directory to the PATH before launching lyx.exe.
Hey, wait a minute: isn't that a reason to have the Qt library linked
dynamically? ;-)
--
Angus
