[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash-dev] What's up with MIT-SHM ?
From: |
strk |
Subject: |
Re: [Gnash-dev] What's up with MIT-SHM ? |
Date: |
Tue, 24 Jun 2008 23:44:58 +0200 |
On Tue, Jun 24, 2008 at 05:11:58PM -0400, Dossy Shiobara wrote:
> Bastiaan Jacques wrote:
> >Okay, but why was it necessary to undef ENABLE_MIT_SHM?
>
> I shouldn't have - I should have fixed configure to make sure
> gnashconfig.h was generated correctly. In gnashconfig.h on Win32, I see:
>
> /* Use MIT-SHM X extension if available */
> #define ENABLE_MIT_SHM 1
>
> So, either:
>
> 1) autoconf needs adjustment to not define that on Win32, or
>
> 2) Win32 builds need to work with ENABLE_MIT_SHM defined
>
> Sorry about the hasty #undef - I must have left it in while hacking the
> Win32 build back to life.
>
> Should Win32 builds use MIT-SHM? Given that the resulting binaries are
> not meant to run under Cygwin X11, I would guess the answer should be
> "no" - am I understanding correctly?
Just a note: there no real "detection" code in ./configure.
Is just an optional thing, default to on, --disable-mit-shm to disable.
Runtime check should exist anyway, so I guess (2) would be the one to
follow.
--strk;