Abdelrazak Younes <[EMAIL PROTECTED]> writes: > Yep I used 'c:/' like syntax. But the --with-extra-prefix never worked > for me, with either c:/ or /c/ style. configure just stops telling that > it cannot find 'c' directory even though it was there.
Unlike MSYS, when using Cygwin the /c thing should be activated by $ mount -f C: /c otherwise you have to use the /cygdrive/c style syntax. You have to issue the mount command only once as it will be stored in a mount table and used again next time. > > Another problem can arise when a path is autogenerated by configure. > > There is some code in the configure script that turns 'C:/Programs/LyX' > > into '/c/Programs/LyX' (or '/cygdrive/c/Programs/LyX', depending on your > > settings), so I had to add the following to the sed command I use for > > modifying configure: > > > > # Set locale and data dir in mixed rather than posix format > > /^ *LYX_ABS_INSTALLED/s/\(^ *\)/\1ac_val=`cygpath -m \"\$ac_val\"`\n\1/ > > > > otherwise I get '/c/Programs/LyX/Resources/locale' hardcoded into the > > executable instead of 'C:/Programs/LyX/Resources/locale', and the net > > effect would be that setting LANG to some locale doesn't work. > > > > Thinking about it, perhaps this is the reason (hardcoded path) why > > Angus reports that setting LANG seems not working in mingw builds. > > Wouldn't it make sense to fix it in svn instead of doing manually the > change? I am sure they would accept your patch. No, this is only needed when you want to build a native LyX but using the cygwin compiler. This is not supported and I don't ask that it is as I agree that it would make things more complicated than they are now. Anyway, I have my lyxconfig script that appropriately hacks 'configure' as needed, so this is not a problem for me. > > However, this is the only problem that I spotted. To be honest there > > was another one, but it was about the recognition of a multi-threaded > > Qt. For some reason the default test program used in configure: > > I have heard about this one from Michael Gerz IIRC. I am using Qt4 so > oviously I don't have this problem Likely, as when using -mno-cygwin the cygwin compiler really turns into the mingw one. > > I think that's all. The native LyX I compile using cygwin is fully > > functional and until now I have seen no side effects. > > IMHO cygwin is a much better environment than MSYS and we should switch > to that if we manage to fix those problems. I disagree, even if I do that ;-) You should have a good knowledge of the way cygwin works and be prepared to surprises. However, I may be wrong on this one. -- Enrico
