There is a problem: to collect a project under Windows. It connects linuhovaya f-I mkfifo. It seems like there is its description in MS Windows Services for UNIX . But so all static libraries * .so! What to do, which way to dig at all? Or is it easier to rewrite to Win PIPE?

  • MS Windows Services for UNIX - is SFU (Interix)? Does it work now? I got the last time with her in SP2 (she refused to work in SP3 (I don’t remember why already) and did not try at 7). @Afftobus, if this is it and it works, please inform. - avp
  • I under sp2. And I did not understand how to build on it and what it is, porting from Linux to Windows or vice versa. Tell me, pliz, what do you need to do there? Threat like, yes, this is it. - Afftobus
  • From Linux (generally bsd-based SFU) to Windows. Just compile the C sources in it (gcc) and basically everything worked. Plus unix commands, shell, etc. I really liked ... - avp
  • I have a project for the studio. Wants mkfifo. In heders it is, and how to connect to * .so project? Or is it necessary to use makefiles? - Afftobus
  • Well, it's clear that the studio will not work with gcc. It should be used either by hand or by makefile. - cy6erGn0m

1 answer 1

You can try to build in dev-c ++, it uses Cygwin, which allows you to collect nix code for wines.

  • dev-c ++ to collect linuksovy? - Afftobus
  • Already some Sygwin appeared? In cygwin (www.cygwin.com), mkfifo was like. Uses most likely screw named pipes. But if Honduras is concerned with licensing, then we must bear in mind that cygwin1.dll is under GPLv3 +. And since the development of the package tried to ensure compatibility with linux more than compatibility with posix. You can collect it under Linux, but at the cost of additional gestures (installing packages). Under cygwin, it's easier. - alexlz
  • Cygwin, of course, poked the wrong key. - Skegg