What do you mean by "a real Windows executable"?
cygwin does just that - it produces a real executable.
On NT, the problem with inlined figures is not the forking, forking maybe a kludge but
it
seems to actually work, the problem is, that you need a ghostscript executable with X11
support. Alladin for Windows has gswin32c which is a
commandline ghostscript interpreter, but it does not have X11 support.
Otoh it is not really worth spending much time on this, because the whole procedure is
a
kludge and nothing else.
It took months to get it halfway reliable on Linux and sometimes I still notice
hanging gs
clients ...
It will have to be rewritten - and as I know these guys here - it will be rewritten.
Roland
Andre Poenitz wrote:
> > I tried to use the mingw32 environment on Win98, too to produce a real
>Win-Executable.
>
> *scratch head* I'd like to try that, too... but:
> How does one specify the usage of a certain compiler when running ./configure?
>
> For my own project I use mingw32 for crosscompiling from Linux to
> Windows, but I handle that using hard-coded paths to the respective
> compilers (standard gcc for Linux->Linux, /..../mingw32/..gcc for
> Linux->Windows) in the (handwritten) Makefile.
>
> When I configure LyX, naturally the standard compiler
> is found (the other is not even in the $PATH). So how to I access
> my mingw32 "properly"?
>
> If someone could enlighten me, please ;-)
>
> Andre'
>
> --
> André Pönitz ......................... [EMAIL PROTECTED]
