>>>>> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
>> Your patch does not sound right. It says that under cygwin, all
>> programs should use dos-style paths. If this is the case, a simple
>> #ifdef __CYGWIN__ could be used to hardcode this into LyX...
Kayvan> No, it's the other way around. In my case, the teTeX that
Kayvan> comes with Cygwin does not need dos-style paths.
My point was that we should/could consider that LyX under cygwin uses
unix-style paths, while under mingw it uses dos-style path. Of course
this is probably too simple...
For example, what does ImageMagick do?
Kayvan> By the way, the test for whether or not we need path
Kayvan> correction already existed in $(srcdir)/lib/configure.m4 and I
Kayvan> merely added a way for LyX to make use of the information.
Kayvan> This is why the test must be run in lib/configure and not
Kayvan> hardcoded.
The relevant code says:
#### Adjust PATH for Win32 (Cygwin)
case `uname -s` in
CYGWIN*)
echo "configure: cygwin detected; path correction"
srcdir=`cygpath -w "${srcdir}" | tr '\\\\' /`
echo "srcdir=${srcdir}" ;;
esac
I do not see why in LyX code we cannot use a #ifdef __CYGWIN__ instead
of that. What's the difference?
Kayvan> My particular installation will work just fine if I switch
Kayvan> from tetex to MikTeX (which needs windows-style paths) after
Kayvan> doing Tools->Reconfigure. This would not be the case with a
Kayvan> hard-coded requirement (needing either Unix-style or
Kayvan> Windows-style paths).
I do not see where this test makes a difference between tetex and
miktex. But it may be because my night has been a bit too short.
JMarc
