X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 12 Nov 2008 11:15:47 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Using POSIX_SHM Message-ID: <20081112101547.GG17719@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <006301c944aa$32fcfee0$4001a8c0 AT mycomputer> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <006301c944aa$32fcfee0$4001a8c0@mycomputer> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Nov 12 09:36, John Emmas wrote: > A project I'm working on is available for both Linux and Windows. The > Linux > version uses a preprocessor directive called USE_POSIX_SHM which (I think) > configures it to use POSIX's shared memory model. The project can also be > built for Windows in which case, USE_POSX_SHM isn't defined. I just > wondered whether I should enable or disable this directive when building > for > Cygwin? Not yet. POSIX shared memory isn't available in the current Cygwin release 1.5.25. It will be available in the next major version 1.7.0. It doesn't exactly look like we will be able to release this in 2008, but I'm still hopeful it's not too far away... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/