|
From: Joerg L. <jo...@us...> - 2003-04-13 12:57:00
|
Hi, On 11.04.03, Bent Andre Solheim wrote: > Of course you are right. I tried downloading and using the python > distribution that comes with CygWin for the build, and it compiles > smoothly. The reason; the compiler used is not cl.exe (Visual C++ > 6.0), > but gcc. The environment used is identified by distutils as CygWin, so > another compiler is used. Fine. > One problem still remains, though. It is my opionion that it should be > possible to build using Visual C++ aswell, so the users of PyX on > Windows do not have to use CygWin. It's a great library, and I know of > several LaTeX users on Windows that would enjoy it. However the > overhead > of installing and using CygWin-Python would not be considered "worth > the > effort" for most of them (qualified quess). You're right, that's not the optimal solution. > MikTex does not come with kpathsea-header and library files in a > standard installation (to my knowledge); only when downloading the > source from cvs, and then you have to build the library. Would it be > possible to supply, for VC++ users and python users using the > Python.org > distribution, the kpathsea library, as part of the PyX distribution? > My > compilation and build experience is limited, so I didn't manage to > build > the MikTex libraries propperly within a reasonable amount of time (I > gave up). I think that's not that easy. You really need kpathsea libraries that "know" of your MikTeX distribution - in the sense that they know where they find the suitable ls-R file. The location of this file of course depends on your local MikTeX configuration/installation. > The kpsewhich command works correctly, but it doesn't impact the VC++ > build process. I was only trying to say that you can also work with PyX without the _pykpathsea extension module. There is a fallback to kpsewhich which, while not being as efficient as the other solution, gives you the full functionality. Jörg |