[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Why BOOST_USE_WINDOWS_H defined by default in

From: Tony Theodore
Subject: Re: [Mingw-cross-env-list] Why BOOST_USE_WINDOWS_H defined by default in MXE patch?
Date: Fri, 25 Dec 2015 20:57:29 +1100

Welcome Arseniy,

On 24 Dec 2015, at 12:40, Arseniy Shestakov <address@hidden> wrote:

I recently find out about MXE and start using it for project I work on. In process I'm got multiple conflicts with constant and struct names that didn't happen for other developer. More details available there:

I'd recently back to it and find out that reason of conflicts was BOOST_USE_WINDOWS_H set by default in MXE boost patch: https://github.com/mxe/mxe/blob/a8df43d1324294522bde66f2c5d5f9f6d43476e6/src/boost-1-fixes.patch

Then I get rid of that part of patch and successfully built everything without BOOST_USE_WINDOWS_H and it's worked fine for me. I tried to find out why that was needed, but didn't manage to find any details on github.

So I now wonder why BOOST_USE_WINDOWS_H was needed in interlocked.hpp? Is it still needed?

Mingw-w64 has since been updated so it’s possible that isn’t needed anymore. Boost is also due for an update [1] and the latest version seems to require less patching so far - that patch is one that’s been removed.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]