-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to build with Boost 1.69 (develop snapshot) #2308
Comments
Looks like it will affect 0.4.8 as well. |
I thought the signals dependency was removed some time ago. Does this just require a change to a CMakeLists.txt ? Perhaps to change a default from signals to signals2 ? |
Has this been fixed sufficiently by #2310? Can we close it as resolved? |
Seemingly yes |
After boostorg/serialization@af46ac2da3e9 (post-Beta1) build fails. See error log. Including In file included from combat/CombatEvent.cpp:1:
combat/CombatEvent.h:42:25: error: implicit instantiation of undefined template 'std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >'
virtual std::string CombatLogDetails(int viewing_empire_id) const
^
/usr/include/c++/v1/iosfwd:193:32: note: template is declared here
class _LIBCPP_TEMPLATE_VIS basic_string;
^
In file included from combat/CombatEvent.cpp:1:
combat/CombatEvent.h:43:14: error: implicit instantiation of undefined template 'std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >'
{ return std::string(""); }
^
/usr/include/c++/v1/iosfwd:193:32: note: template is declared here
class _LIBCPP_TEMPLATE_VIS basic_string;
^ |
As in that pull request? |
Include to address Boost build issue in comment: #2308 (comment)
After boostorg/boost#189 build fails, see error log and missing files
Note, according to Boost calendar 1.69 release is planned sometime in December.
The text was updated successfully, but these errors were encountered: