Luis Rivera wrote: > Angus, > > After the astounding success of late night's compilation under cygwin, > I just read your emails and decided to give it another shot. I grabbed > os_cygwin.C from viewcvs on lyx, as you suggest, and put everything > back in place.
Note that I fixed src/support/Makefile.am in the CVS repository so os_cygwin.C is now packaged in the distribution. > Again, with cygwin, no problem. Runs perfectly on win95 (using > cygwin1.dll and cygz.dll, as I said before). > > However, when I patched your make_tex2lyx_dist.sh to > make_tex2lyx_mingw32.sh and added two specifications to the ./configure > line: --build=i686-pc-mingw32 --target=i686-pc-mingw32 (that's the way > I compile my `native' win32 console apps on cygwin), the compiler > failed on > > package.C:384: error: `GetLongPathName' undeclared (first use of this > function) Failed in compilation? Ouch! > I guess it's all my fault, since I'm using pretty old sources. I found > tortoiseCVS, and if I find my way through it, I'll try the cvs sources > next week. I may even try to build LyX on cygwin. I read > INSTALL.win32, and correct me if I'm wrong, I only need to build the Qt > libraries prior to compile the source code. Wish me luck. Good luck! Meanwhile, you might like to grab tex2lyx_win32_11Sep05.zip from http://wiki.lyx.org/LaTeX/LatexToLyx. I guess you'll have to go by way of the "Upload Files" page, navigating to the LaTeX/tex2lyx directory by clicking on the directory names. (Username is lyx and password is LyXers) I linked the executable explicitly against shfolder.dll, in an attempt to get SHGetFolderPath to work on Win98. > Note that, this far, I haven't noticed any difference between > commenting out the conditional call to os_cygwin.C in os.C, and adding > the file to the sources. The executable changes a little, but seems to > be functionally equivalent. The big difference must be the way it > calls file paths (slash/\backslash and spaces included?) from within > MS's shell (aka command prompt). I'll be doing more testing as I use > the programs, though. That's correct. -- Angus
