Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes a écrit :
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Enrico Forestieri a écrit :
| > | > On Sat, Apr 08, 2006 at 07:00:01PM +0200, Abdelrazak Younes wrote:
| > | >
| > | >> Enrico Forestieri a écrit :
| > | >>> All the necessary machinery to activate it is already present in
| > | >>> configure and configure.py, so this simple patch to os_win32.C
| > | >>> allows using the cygwin tetex with a native win32 LyX.
| > | >> Hi Enrico,
| > | >>
| > | >> Small question: if this patch was applied what would be missing in
| > | >> a native win32 compared to a cygwin one? If it's only for the posix
| > | >> path, then the too close are pretty close... aren't they?
| > | > Uhm, not quite. Named pipes and sockets (lyxclient) work with cygwin
| > | > but not with a native LyX. In general, whatever works on *nix, also
| > | > works on cygwin (that is the cygwin goal).
| > | | Hum, not sure about named pipes but sockets can be fixed.
| > not unixsockets... but we should ust use tcp instead. then we are
| > portable to anything with a netstack.
|
| Yes, I think there's something in boost for that.
That would be the async io I guess.
--
Lgb
