That is a well-known problem in X.h.
From experience it has many (many) more of these and it's not some other library's fault. It should be fixed in X.h.
I've tried to comb through corporate headers to work with X.h after GPU code was introduced in headers. The only working solution in the end was (a) to hide all use of X.h from headers (b) even creating platform specific minified headers for GPU-aware parts of the code base. I remember seeing mozilla/firefox tickets about this exact problem with these ancient headers. Perhaps they have more detailed strategies to deal with it in your project. It's annoying, but it clearly has little to do with Boost or Boost JSON. Regards, Seth On Fri, Nov 11, 2022, at 5:59 PM, Rainer Deyke via Boost wrote:
On 10.11.22 18:00, Marshall Clow via Boost wrote:
Available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/
The SHA256 checksums are as follows:
6b6b95fde0ec9c6c0e1584f35c6c2dc4eb6c8629c9635e844b8e6a9ad9594da1 boost_1_81_0_b1_rc1.tar.gz 9f2ce5d1cefb8f6b7e8cfcabc73632f348958e7cba2604dcb3688fecf6463d67 boost_1_81_0_b1_rc1.tar.bz2 e7547a789339499c6fc582a96ffb8989d97074f107520ddebc1ed5f30a0d6964 boost_1_81_0_b1_rc1.zip 758af4ae4f4224b6f2bd8f05fe0109d1f248c0377ee2dce03ccbeb30d82fb8b4 boost_1_81_0_b1_rc1.7z
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
I am getting compile errors when using the beta. It seems that Boost.Json uses the identifier Opposite as a template argument, but X.h (from X11) contains the following line:
#define Opposite 4
This is a regression from Boost version 1.80.0.
-- Rainer Deyke (rainerd@eldwood.com)
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost