troubles compiling swi-prolog 5.4.2 on cygwin

Hello,
I'm a long time user of swi and since I have to work on Windows 2000 I
missed the unix version of swi, so I tried to compile it and everything
is fine except the modules compilation...
Can someone give me hint, tips or help in order to achieve the whole
process ?



thanks a lot



Djamé

ps : my email is djame D O T  seddah   A T  FREE  D O T  FR   (sorry for
the inconvenience but everyday's spamm makes me miss good old days where
1 spamm a w was a terrible intrusion into my mailbox)

In article <416a58bb$0$6246$636a15ce@news.free.fr>,
djame@jamais-de-la-vie.com wrote:
> Hello,
> I'm a long time user of swi and since I have to work on Windows 2000 I
> missed the unix version of swi, so I tried to compile it and everything
> is fine except the modules compilation...
> Can someone give me hint, tips or help in order to achieve the whole
> process ?

Send error messages to the SWI-Prolog mailinglist, I'd guess.  SWI-Prolog
on Cygwin is a bit of a dead project though.  I'm happy to include patches
for it into the main branch, but I do not suggest using it.

The emulation causes file and directory access to be way slower than
using the thin emulation layer used by the Windows version. Graphics
(XPCE) does not run under Cygwin. When I did the port I did manage to
get it compiled, but I was stuck getting event handling to work
properly. Guess it can be done though if you really wanted.  All in
all the only thing the Cygwin version can and the Windows version
can't is fork/1 from the clib package, but even than the Cygwin fork()
is so slow you do not want that.  Finally, of course, the Cygwin version
can load Cygwin shared objects, but I guess you can also create DLLs that
work with the Windows version using MinGW and I understood you can get
a commandline version of Microsoft MSVC for free.

Of course you can run plwin.exe and plcon.exe from the bash shell.

Cheers --- Jan

Jan Wielemaker a écrit :
> In article <416a58bb$0$6246$636a15ce@news.free.fr>,
> djame@jamais-de-la-vie.com wrote:
> 
>
>
> Send error messages to the SWI-Prolog mailinglist, I'd guess.  SWI-Prolog
> on Cygwin is a bit of a dead project though.  I'm happy to include patches
> for it into the main branch, but I do not suggest using it.
>
> The emulation causes file and directory access to be way slower than
> using the thin emulation layer used by the Windows version. Graphics
> (XPCE) does not run under Cygwin. When I did the port I did manage to
> get it compiled, but I was stuck getting event handling to work
> properly. Guess it can be done though if you really wanted.  All in
> all the only thing the Cygwin version can and the Windows version
> can't is fork/1 from the clib package, but even than the Cygwin fork()
> is so slow you do not want that.  Finally, of course, the Cygwin version
> can load Cygwin shared objects, but I guess you can also create DLLs that
> work with the Windows version using MinGW and I understood you can get
> a commandline version of Microsoft MSVC for free.
>
> Of course you can run plwin.exe and plcon.exe from the bash shell.
>
> 	Cheers --- Jan
Thanks a lot, i'm giving up with the cygwin version....  in the cywgin
distro I used, the swi version is 4 something, maybe someone could send
them a compiled binary for cygwin ?


Cheers,


Djamé