This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: IPC for Win32
- To: GamerX_ at usa dot net
- Subject: Re: IPC for Win32
- From: Ludovic LANGE <llange at capgemini dot fr>
- Date: Sat, 16 May 1998 14:00:39 +0200
- CC: Cygnus Mailing List <gnu-win32 at cygnus dot com>, Philippe CHAPUY <pchapuy at capgemini dot fr>
- Organization: Cap Gemini Telecom France
- References: <000f01bd808b$be909dc0$8155a58e@hssktn129.sk.sympatico.ca>
Hello,
> Does this package require that once I write an application that uses these
> IPC functions, I also include the IPC-Daemon? I saw it mentioned in the
> readme file.
Yes, these IPC functions are not included in the cygwin32 ".dll" file. So
they need that this daemon 'ipc-daemon.exe' shall be included and runned
before you access any IPC function. This ipc-daemon is a console-less
application, so you can start it up at boot time. (you'll have to comment out
a "printf" function in the main() function, because when it loads ok, the
daemon says "daemon loaded ok..." which can annoy you at boot. Please do.)
This package is just a temporary way to have IPC running with CygWin32. It is
nothing more than a "quick and dirty" hack, in no way optimized, but it works.
As the header files are quite standardized (they originally come from Linux I
have been told) this allow our projects to compile and run with CygWin32.
When CygWin32 have the native IPC support, this package won't be useful any
more, and your application will have to be relinked (compilation should not be
necessary...)
Please Note that I do NOT plan to hack the CygWin32 tree in order to give it
native IPC support : I have far too much work for the moment. If the situation
had not changed in 3 or more months, I'll consider the question...
--
--- Ludovic LANGE
--- Ingénieur d'études chez Cap Gemini Telecom France
--- mailto:llange@capgemini.fr
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".