> Lars Jensen wrote:
> Is there a specific site where the latest win32 port can always be
> found? I noticed that www.lyx.org has a link to v.1.0.4, while others on
> the mailing list appear to have v.1.1.4.
It seems that Steven van Dijk has released the 'official' win32 port for
LyX. I Don't know why, but this is fpr a long time 1.0.4 developed and
prepared for WinNT. Because of many bugfixes and new features I started to
'port' it for myself beginning with 1.1.2 ;-) Now one can fetch LyX 1.1.4
from
http://www.fh-hannover.de/mbau/tim/hentschel/pub/lyx114.zip
> Lars Jensen wrote another time:
> I downloaded your 1.14 port, and it works fine, except fore the View
> Postscript feature. I get a "wap" error from Ghostscript (or Ghostview).
> Do you have any idea what might cause this?
The main problem with LyX on win32 is, that it is based on the cygnus
environment. With this LyX isn't a native win32 application but depends on
the port of most of the unix system calls, i.e. on cygwin.dll instead of
CRTDLL.DLL or MSVCRT.DLL which are part of windows itself!
The main bug in cygwin seems to be the process creation when forking a new
process. This doesn't work within LyX. So you can mention, that for example
when starting the dvi viewer on win32 the last character of the command
shown in the mini buffer is a #-sign instaed of a &-sign to create a
background process. This was changed by me! (The #-sign has no function! It
is only for degugging purposes, to detect calls which I have forget to patch
8-)
Most of all process generation in Lyx is implemented by calling the system()
system call, i.e. by calling a shell subprocess! All of these calls I have
patched as described above. The patch works, because I call shell script
files which will create the background process using the Win32 command
'start'! (BTW: In the LyX code a similar procedure is done for OS/2).
Inline viewing unfortunatly is done directly by calling a fork() system call
within LyX. This has to be done to redirect the ghostscript output streams
using them to place the figure in the right place of the document/screen.
This doesn't work (see above), so it could not be used on win32 platforms!!
But: On Steven van Dijk's system it works as he describes on his page. I've
contacted him many times and we compared all of our system configuration
(autoexec.bat .... register entries). Of course he does run WinNT and I do
run Win98. Maybe this is the reason for the different behaviour of
cygwin.dll!?!?!?
Hope that was of interest!
Claus
