Re: [Mingw-cross-env-list] MemoryBarrier needed for dbus

[Tony Theodore]

On 24 September 2011 00:52, Mark Brand <address@hidden> wrote:
> Just updated dbus [1].
>
> Dbus now uses MemoryBarrier which is in the Windows API but not in MinGW, so
> I patched it [2] into the relevant dbus source file. This is not a
> particularly elegant solution, but I'm not sure we want to patch our
> windows.h just for this one case.
>
> Feedback is welcome.
>
> Mark
>
> [1] http://hg.savannah.gnu.org/hgweb/mingw-cross-env/rev/8bfc6d601bb1
> [2]
> http://lists-archives.org/mingw-users/15935-missing-definition-of-memorybarrier.html

Hi Mark,

Somewhat related, this is an interesting edge case. Driving home
tonight, trying to formulate the mingw-64 proposal in my mind, I
decided that any patches should apply to all targets. The author of
message [2] above, is one of the leads in the mingw-64 project, so I
imagine that that runtime already has support for this function.

In the hypothetical multi-target scenario, how would we apply such a
patch? In this case, it would seem to make sense to patch windows.h
from w32api for the i686 target (assuming the x86_64 target does have
this) instead of in dbus.

Cheers,

Tony