boostorg / geometry

Boost.Geometry - Generic Geometry Library | Requires C++14 since Boost 1.75
http://boost.org/libs/geometry
Boost Software License 1.0
450 stars 214 forks source link

Can't build with geometry.hpp in CLR project #1228

Open Sungjun4 opened 8 months ago

Sungjun4 commented 8 months ago

Visual Studio 2022(2019 as well) ISO C++ 14, 17, 20 boost: 1.84.0, 1.81.0

I create a new project, CLR class Library(.NET Framework) or CLR console App(.Net Framework), and install the Boost NuGet package(1.84.0)

And include the boost header, even not adding any source code, just including headers.

And build a solution.

Followings are no problem to build

include <boost/foreach.hpp>

include <boost/property_tree/ptree.hpp>

include <boost/property_tree/ptree_fwd.hpp>

include <boost/geometry/arithmetic/cross_product.hpp>

include <boost/geometry/geometries/geometries.hpp>

But if I add

include <boost/geometry.hpp>

Then I got the error.

Error C1189 #error: "This library now requires a C++11 or later compiler - this message was generated as a result of BOOST_NO_CXX11_REF_QUALIFIERS being set"

Is this a bug? or do I need any setting for using geometry.hpp in CLR?

Sungjun4 commented 8 months ago

It is OK with 1.76.0 but error from the 1.77.0

awulkiew commented 7 months ago

It seems that this error is generated by Boost.MultiPrecision: https://github.com/boostorg/multiprecision/blob/develop/include/boost/multiprecision/detail/check_cpp11_config.hpp#L33 becasue BOOST_NO_CXX11_REF_QUALIFIERS is defined in Boost.Config probably somewhere in this file: https://github.com/boostorg/config/blob/develop/include/boost/config/compiler/visualc.hpp This macro is set when

The compiler does not support ref-qualifiers on member functions as described in N2439.

(see documentation)

So the question is, does the compiler support ref-qualifiers for member functions? Here you can find some info and example code: https://akrzemi1.wordpress.com/2014/06/02/ref-qualifiers/ If it doesn't then the error is correct. If it does then it's a bug in Boost.Config and should rather be reported there.