>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc Lasgouttes wrote: Interesting. I found that I had to Angus> start lyx from the /home/Angus/qt3/lib directory (so that Angus> qt333.dll was found; I could have changed my PATH variable but Angus> only found that out later) >> Well, in a normal operation, qt333.dll would be in the lyx >> directory, anyway. Angus> Why? I think I'll end up installing Qt in "C:\Program Files\Qt" Angus> and put the headers in "C:\Program Files\Qt\include". Things Angus> other than LyX can then use it... I don't think so. Either you put it in \windows\system (I think) where everybody can find it, or, if you want to distribute a binary LyX, you bundle a version of the library. It might be even better for size to link statically against qt (like LyX/Mac). Now, for your own installation, of course, you do as you prefer... Angus> I found that LyX would refuse to start if it couldn't find Angus> chkconfig.ltx (-sysdir) That's fair Angus> or textclass.lst (-userdir). That's surprising. Angus> My plan with Ruurd's stuff is to commit a few more bits and Angus> bobs from the linux machine and then to fire up the Windows Angus> machine, merge the remainder of the patch back into the local Angus> tree and try and get the thing to compile again. The primary Angus> goal is to get the sources to compile under Windows without Angus> needing to #include "os_win32.h" from os.h. (Individual .C Angus> files will still need os_win32.h.) OK JMarc
