> You need to set a few environment variables. TEXMF is the important one.
> I just used export TEXMF=/progra~1/texmf
> VARTEXFONTS is useful if you have a localtexmf tree.
>
> Alternatively you can set TEXMFCNF to point to a texmf.cnf file that has
> the paths in.
>
> Alternatively you can symlink your MikTex root to /usr/local/texmf (the
> default)
>
> I have tried all three ways and they work for me. How about anybody else?
It doesn't work, no matter what you set TEXMF to... Symlinks don't seem to
work correctly anymore, at least not with the latest cygwin1.dll/lily
combination. It seems that paths in cygwin are handled differently... From
the FAQ:
How can I access other drives?
------------------------------
You have some flexibility here.
Cygwin has a builtin "cygdrive prefix" for drives that are not mounted. You
can access any drive, say Z:, as '/cygdrive/z/'.
In some applications (notably bash), you can use the familiar windows
<drive>:/path/, using posix forward-slashes ('/') instead of Windows
backward-slashes ('\'). (But see the warning below!) This maps in the
obvious way to the Windows path, but will be converted internally to use the
Cygwin path, following mounts (default or explicit). For example:
bash-2.03$ cd C:/Windows
bash-2.03$ pwd
/cygdrive/c/Windows
and
bash-2.03$ cd C:/cygwin
bash-2.03$ pwd
/
for a default setup. (You could also use backward-slashes in the Windows
path, but these would have to be escaped from the shell.)
Warning: There is some ambiguity in going from a Windows path to the posix
path, because different posix paths, through different mount points, could
map to the same Windows directory. This matters because different mount
points may be binmode or textmode, so the behaviour of Cygwin apps will vary
depending on the posix path used to get there.
You can avoid the ambiguity of Windows paths, and avoid typing "/cygdrive",
by explicitly mounting drives to posix paths. For example:
bash$ mkdir /c
bash$ mount c:/ /c
bash$ ls /c
Note that you only need to mount drives once. The mapping is kept in the
registry so mounts stay valid pretty much indefinitely. You can only get rid
of them with umount (or the registry editor).
The '-b' option to mount mounts the mountpoint in binary mode ("binmode")
where text and binary files are treated equivalently. This should only be
necessary for badly ported Unix programs where binary flags are missing from
open calls. It is also the setting for /, /usr/bin and /usr/lib in a default
Cygwin installation. The default for new mounts is text mode ("textmode"),
which is also the mode for all "cygdrive" mounts.
I'm stumped. Anyone have any ideas?
-- Shamus
