Warning C4575 when compiled as a C++/CLI .Net Core project with Visual Studio 2019 v16.8

[mw4853]

If you include a boost header (such as boost/algorithm/string.hpp) that ultimately includes is_funcion_cxx_11.hpp in a C++/CLI .NET Core (NOT the normal .NET Framework) project, you will see a series of compiler warnings similar to the following:

boost-1.74\boost\type_traits\detail\is_function_cxx_11.hpp(114,4): warning C4575: '__vectorcall' incompatible with the '/clr' option: converting to '__stdcall'

type_traits/include/boost/type_traits/detail/is_function_cxx_11.hpp

Line 114 in c6c7ff1

struct is_function<Ret __vectorcall(Args...)BOOST_TT_NOEXCEPT_DECL> : public true_type {};

There is no warning here if the C++/CLI project is compiled as .NET Framework instead. It looks like __CLR_VER is defined when building as .NET Framework, but not when building as .NET Core?

How to convert your C++/CLI project to build as .NET Core (instead of the normal .NET Framework):
https://docs.microsoft.com/en-us/dotnet/core/porting/cpp-cli

[mw4853]

Maybe __CLR_VER should be replaced with _MANAGED ?
https://docs.microsoft.com/en-us/cpp/preprocessor/predefined-macros?view=msvc-160

[millerrt3]

@mw4853 I believe that this is effectively a duplicate of #123 (even though the specific warning is different in your case, the underlying cause is the same). I filed PR #130 to fix #123 a while back, but there doesn't seem to be much movement towards merging it (or any other fix for the issue).

[mw4853]

@bionicOnion - Darn. I was really hoping to avoid modifying my local copy of Boost, but, it looks like that is what I am going to have to do.

[erikeldh]

boost\type_traits\detail\is_member_function_pointer_cxx_11.hpp(121,4): warning C4561: '__fastcall' incompatible with the '/clr' option: converting to '__stdcall' boost\type_traits\detail\is_member_function_pointer_cxx_11.hpp(121,113): error C2953: 'boost::is_member_function_pointer<Ret(__stdcall C::* )(Args...)>': class template has already been defined

I believe this still to be an issue with boost 1.75