In comp.lang.lisp Aaron Sloman See text for reply address <Aaron.Sloman.XX@cs.bham.ac.uk> wrote:
:> The easiest solution would be to compile poplog not as a
:> stand-alone Windows app but within a Unix emulation
:> environment like Cygwin, U/Win or Interix. Within these
:> XFree86 and Motif are available and porting Unix apps
:> is no harder than porting them to another Unix variant.
: If anyone else has tried installing and running linux poplog in
: one of these unix emulations, please let me know.
cygwin is very stable now. apps are quite hard to port, mostly because of
the win specific filesystem and bad tools to build it. (autoconf is quite
okay, but most have only hand-crafted makefiles). pipes, threads and signals
caused headaches in the past, but are okay now. you don't have that much
signals as in unix and there are still major drawbacks. it also became
very slow in the last months.
the cygwin w32api headers also had a major revamp in the last month. I
cannot see the light there yet, but that's only a minor problem.
XFree86 apps are much easier to port, just recently the system became
quite usable. it just doesn't parse the .XConfig files yet, everything
is builtin so far. gnome is on the way. gtk is not quite stable,
but usable.
I would try U/Win. I don't know Interix.
A native port with msvc would get the best API support and performance.
--
Reini Urban
http://xarch.tu-graz.ac.at/acadwiki/AutoLispFaq
|