July 2017 - Boost-users - lists.boost.org

[serialization] unable to link on OS X when MACOSX_DEPLOYMENT_TARGET=10.7
by Pavol Juhas 06 Jul '17

06 Jul '17

Hello, I'd like to build the boost_serialization library with a compatibility setup for Mac OS X version 10.7, because I need to use it with Anaconda Python binaries, which are built for OS X 10.7. The OS X compatibility version can be set either by passing `-mmacosx-version-min=10.7` as a compile and link option or by setting environment variable MACOSX_DEPLOYMENT_TARGET=10.7. If I do so, the boost_serialization library builds without complaints, however I am not able to link it with my test program. Here are the steps I take to compile boost_serialization and the test program starting from a fresh boost 1.64.0 tree: # -------------------------------------------------------------- $ export MACOSX_DEPLOYMENT_TARGET=10.7 $ ./bootstrap.sh $ ./b2 -j4 variant=release link=shared --with-serialization stage # The stage/lib directory now contains libboost_serialization.dylib. # Use it to build a test program from tarchive.cpp: $ c++ tarchive.cpp -I. -Lstage/lib -lboost_serialization Undefined symbols for architecture x86_64: "boost::archive::basic_binary_oprimitive<boost::archive::binary_oarchive, char, std::char_traits<char> >::init()", referenced from: boost::archive::binary_oarchive_impl<boost::archive::binary_oarchive, char, std::char_traits<char> >::init(unsigned int) in tarchive-5e24a9.o "boost::archive::basic_binary_oprimitive<boost::archive::binary_oarchive, char, std::char_traits<char> >::save(std::string const&)", referenced from: void boost::archive::save_access::save_primitive<boost::archive::binary_oarchive, std::string>(boost::archive::binary_oarchive&, std::string const&) in tarchive-5e24a9.o ... # -------------------------------------------------------------- The only thing the test program (attached) does is to instantiate the boost::archive::binary_oarchive class. The procedure above works fine when MACOSX_DEPLOYMENT_TARGET is set to 10.9 or higher. Am I missing some option that would fix the failed linking when building for OS X 10.7? I suppose this could be related to object visibility options as the serialization library is compiled with "-fvisibility=hidden" and "-fvisibility-inlines-hidden" options. Thank you, Pavol

2 3

[review][beast] Five-days Remaining
by Michael Caisse 05 Jul '17

05 Jul '17

Hi all - We are half-way through the review and have some great involvement and exchanges and a few reviews already. I hope if you haven't written a review yet that you still will. Please provide whatever effort you can afford toward the review process. Boost depends on community involvement. You might have noticed that I have solicited input from you regardless of your experience with the domain. I personally think it is a mistake to have input only from domain experts. True innovation often comes from "outsiders". If you have no experience with Asio or with HTTP, how approachable is this library? Were you able to understand the documents? Could you use the examples? Were you able to build something of your own? Domain experts -- you know the dark corners of the domain. The hard parts that have caused you hours of lost sleep and the need to hack around an existing library or to write your own. How does Beast address your concerns and the problems you have experienced in the past? Is it flexible enough to be put into your tool chest? So far we have reviews from: * Marcel Ebmer * Peter Dimov * Artyom Beilis * Zach Lain * Nik Bougalis * Klemens Morgenstern * Glen Fernandes If I missed a review from you, please let me know! Happy Coding! michael -- Michael Caisse Ciere Consulting ciere.com

1 0

performance tuning on boost version 1_64_0
by Connie Zhang 05 Jul '17

05 Jul '17

Hello, I recently upgrade boost version of a visual C++ program from an old version of 1_58_0 to 1_64_0. Compared to the original executable, the newly upgraded one runs very slow (more than 6 times longer) even I disable the debug mode and set the optimization to /ox in visual environment. The other difference between the old and the upgrade ones is the visual studio version. The old one is on 2010 and the new one 2013. Anyone has any idea for why it behaves like this? Which kind of performance tuning I need to look into? Thank you so much for your help! Connie Sent from Yahoo Mail. Get the app

4 4

[serialization]Nans and infinity in wide xml archive
by Elizabeta 04 Jul '17

04 Jul '17

Hi I am using wide xml boost serialization archive. Because of the problem with loading of nans and infinities I tried the nonfinite facet as in the code snippet. This works, expect it messes with the encoding of the xml arhive which is no longer UTF-8 like before the using the facet, and I believe it is because of the no_codecvt flag which is passed to the archive. But without this flag the loading of nans/infinity does not work. How to use the facet and keep the wanted UTF-8 encoding ? float d = std::numeric_limits<float>::quiet_NaN; { std::wofstream oss("C:\\test.xml"); std::locale locale1(oss.getloc(), new boost::math::nonfinite_num_put<wchar_t>); oss.imbue(locale1); xml_woarchive oar(oss, no_codecvt); oar << BOOST_SERIALIZATION_NVP(d); } { float d; std::wifstream iss("C:\\test.xml"); std::locale locale1(iss.getloc(), new boost::math::nonfinite_num_get<wchar_t>); iss.imbue(locale1); xml_wiarchive iar(iss, no_codecvt); iar >> BOOST_SERIALIZATION_NVP(d); std::cout << d << std::endl; } -- View this message in context: http://boost.2283326.n4.nabble.com/serialization-Nans-and-infinity-in-wide-… Sent from the Boost - Users mailing list archive at Nabble.com.

3 5

Log: Coloring logging output
by Florian Lindner 03 Jul '17

03 Jul '17

Hello, I try to create a formatter that can display logging messages (or just prints the severity level in different colors). Given a format string like: default_formatter = "%SeverityFormat% %Message%"; /// A custom formatter that handles the Severity formatting class severity_formatter_factory : public boost::log::formatter_factory<char> { public: formatter_type create_formatter(boost::log::attribute_name const& name, args_map const& args) { namespace expr = boost::log::expressions; return expr::stream << "|" << "\033[32m" << expr::attr<boost::log::trivial::severity_level >("Severity") << "|"; } }; and register with bl::register_formatter_factory("SeverityFormat", boost::make_shared<severity_formatter_factory>()); it basically works, i.e. the output is colored (all green) and the severity name is printed. But how can I get the actual severity of the message that is about to be formatted inside the formatter? So I can act on that and color warn messages red and info messages green? What I found on the internets, e.g. https://stackoverflow.com/questions/38309479/how-to-add-color-coding-to-boo… http://www.boost.org/doc/libs/1_64_0/libs/log/doc/html/log/tutorial/formatt… was using the sink->set_formatter method, which gives me, afaik, no possbility to configure using a format string. But I'm open to any ideas... Thanks, Florian

1 0

Why cannot asio tcp socket server detect TCP disconnection when the client device lost power?
by jupiter 03 Jul '17

03 Jul '17

Hi, The asio tcp server can detect the disconnection when the client program stop. But I have small device when it lost power, the server won't be able to detect the TCP disconnection. Does the boost socket has TCP timeout? What is an effective way to handle this situation other than running heartbeat in user level? Thank you. Kind regards, - j

6 10

[review][beast] Review of Beast starts today : July 1 - July 10
by Michael Caisse 01 Jul '17

01 Jul '17

The formal review of Vinnie Falco’s Beast library will take place from July 1 through July 10, 2017. Please consider participating in this review. The success of Boost is partially a result of the quality review process which is conducted by the community. You are part of the Boost community. I will be grateful to receive a review based on whatever level of effort or time you can devote. Beast is a C++ header-only library serving as a foundation for writing interoperable networking libraries by providing low-level HTTP/1, WebSocket, and networking protocol vocabulary types and algorithms using the consistent asynchronous model of Boost.Asio. Beast is designed for: * Symmetry: Algorithms are role-agnostic; build clients, servers, or both. * Ease of Use: Boost.Asio users will immediately understand Beast. * Flexibility: Users make the important decisions such as buffer or thread management. * Performance: Build applications handling thousands of connections or more. * Basis for Further Abstraction: Components are well-suited for building upon. A branch has been made for the review. You can find Beast for review at these links: * Documentation : <http://vinniefalco.github.io/stage/beast/review/> * Source code : <https://github.com/vinniefalco/Beast/tree/review> * The FAQ answers real questions that come up : <http://vinniefalco.github.io/stage/beast/review/beast/design_choices/faq.ht…> A lightning talk from CppCon 2016 introducing Beast can be found here: <https://www.youtube.com/watch?v=uJZgRcvPFwI> Please provide in your review whatever information you think is valuable to understand your final choice of ACCEPT or REJECT including Beast as a Boost library. Please be explicit about your decision. Some other questions you might want to consider answering: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With which compiler(s)? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? More information about the Boost Formal Review Process can be found here: <http://www.boost.org/community/reviews.html> Thank you for your effort in the Boost community. Happy coding - michael -- Michael Caisse Ciere Consulting ciere.com

1 0