- Boost-users - lists.boost.org

[accumulators] Moving mean expiry
by Michael Powell 08 Sep '13

08 Sep '13

Hello, I am looking for a moving window mean accumulator. Could roll my own, but I know there's a pretty good one in Boost. Need to know, does it comprehend the notion of Expiration? That is, values dropping off after a predetermined window of time? Preferably depending on the boost::chrono::high_resolution_clock. Thank ye... Regards, Michael Powell

1 1

[Serialization and possibly others] Serialization library built with Clang symbol export errors on link
by Kim 07 Sep '13

07 Sep '13

Hey guys, I'm trying to link my program to the boost serialization library built using clang w/ the mingw STL headers on Windows and I get a lot of symbol not found errors. Any help is most appreciated since I really want to get this working with Clang. If I need to provide more information please let me know. C:\MinGW\bin>g++ -shared script.o libboost_serialization-clang34-mt-1_54.lib -o script.dll Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_iarchiveEEEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_13text_oarchiveEEEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonINS_7archive6detail12extra_detail3mapINS2_19naked_text_iarchiveEEEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_13typeid_system27extended_type_info_typeid_0ENS3_12type_compareESaIS6_EEE8instanceE: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE12get_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE12is_destroyedEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE18get_const_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE20get_mutable_instanceEv: symbol not found Cannot export __ZN5boost13serialization9singletonISt8multisetIPKNS0_18extended_type_infoENS0_6detail11key_compareESaIS5_EEE8instanceE: symbol not found collect2.exe: error: ld returned 1 exit status C:\MinGW\bin>

1 1

[spirit] Qi-adapted-struct light bulb
by Michael Powell 07 Sep '13

07 Sep '13

Hello, A light bulb went on for me with regard to adapting structs into Qi parser grammars. Feel free to correct me if I'm wrong. The key is adapting a struct into your grammer's parser(s) using the BOOST_FUSION_ADAPT_STRUCT, which identifies the type (struct) and fields you are synthesizing out of the grammar. It doesn't mean that there can't be other (presumably) public variables, functions, etc, in the struct. It also doesn't mean there can't be private or protected or even a hierarchy of members. It just means that those are the *adapted* fields into which values will be synthesized. Need a style feedback as well. I am finding that I define both the struct and its parser grammar in the same header/source. Is there any reason to separate the two, really? Other than perhaps not everything needs to know about the grammer, just the struct, type thing. Thank you... Regards, Michael Powell

1 0

Boost program option parsing issue.
by Vivek Anand 07 Sep '13

07 Sep '13

Hi All, I am using program option for my program. Here is my code snippet string inputFile, outputFile; /* Populate command line arguments */ po::options_description desc("Usage: KDMGenerator [OPTIONS]"); { desc.add_options() ("help", "prints this message") ( "input-file", po::value<string>(&inputFile), "input file name" ) ( "output-file", po::value<string>(&outputFile), "output file name"); } po::variables_map vm; po::store(po::parse_command_line(argc, argv, desc), vm); po::notify(vm); if (vm.count("help") || !vm.size()) { cout <<desc; return 0; } if(vm.count("input-file")) { cout << "Input file :" << inputFile << '\n'; } if(vm.count("output-file")) { cout << outputFile << '\n'; } The issue I am facing is that if i I call my program without passing value for input file, something like ./myapp --input-file --output-file out.txt I get Input file: --output-file i.e the value "--output-file" get stored in inputFile and vm.count("output-file") returns zero. Is this the desired behavior? Is there any workaround for this? -- Vivek,

2 4

[spirit] qi pheonix struct adaptation
by Michael Powell 06 Sep '13

06 Sep '13

Hello, Need a little guidance when it comes to adapting structs. Let's say I've got a simple struct: struct data_t { int a; int b; int c; }; When I adapt it, I need to specify the fields into which the values are being consumed and subsequently synthesized? What happens for optional consumers, in one use-case? In another use-case, what happens if one value or another value or a third value can be consumed for that field? So, something like this, pardoning the pseudo-code: using qi::int_; using qi::lit; qi::rule<Iterator, data_t()> rule_; //a is optional, followed by b is mandatory, followed by c can be 1 | 2 | 3 rule_ %= -( int_ ) >> lit(',') >> int_ >> lit('.') >> ( int_(1) | int_(2) | int_(3) ); This is applying into a GPS NMEA parser domain, so along these lines for things like geo-spacial-coordinates, latitude/longitude, time, etc. Thank you... Regards, Michael Powell

1 0

compilation error
by Николай Кинаш 06 Sep '13

06 Sep '13

Hello all! My programm: `--# cat test_boost.hpp #include <boost/graph/adjacency_list.hpp> #include <boost/graph/rmat_graph_generator.hpp> #include <boost/random/linear_congruential.hpp> typedef boost::adjacency_list<>Graph; typedef boost::unique_rmat_iterator<boost::minstd_rand, Graph> RMATGen; int main() { boost::minstd_rand gen; // Create graph with 100 nodes and 400 edges Graph g(RMATGen(gen, 100, 400, 0.57, 0.19, 0.19, 0.05), RMATGen(), 100); return 0; } `--# mpic++ test_boost.hpp -I./boost/boost/graph/ -I./boost/ -I./boost/boost/random/ -o test_boost /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/crt1.o: In function `_start': (.text+0x20): undefined reference to `main' collect2: error: ld returned 1 exit status what's wrong ?

2 1

[filesystem] path destructor crash
by Patrick Steele 06 Sep '13

06 Sep '13

boost = 1.54 IDE = Visual Studio 2005 / 2012 OS = Windows 7 Hi, I have a 32-bit application that I am upgrading from Visual Studio 2005 to 2012. If I place the following code at the beginning of the application: { //test 1 boost::filesystem::path blahPath; } { //test 2 boost::filesystem::path blahPath = _T( "C:\\ProgramData\\blah" ); } { //test 3 boost::filesystem::path blahPath; std::wstring text = _T( "C:\\ProgramData\\blah" ); blahPath = text; } then it works fine in Visual Studio 2005, however test 3 crashes in Visual Studio 2012 with: --------------------------- Microsoft Visual C++ Runtime Library --------------------------- Debug Assertion Failed! File: f:\dd\vctools\crt_bld\self_x86\crt\src\dbgdel.cpp Line: 52 Expression: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse) and this callstack: msvcr110d.dll!operator delete(void * pUserData) Line 52 C++ boost_filesystem-vc110-mt-gd-1_54.dll!std::allocator<wchar_t>::deallocate(wchar_t * _Ptr, unsigned int __formal) Line 586 C++ boost_filesystem-vc110-mt-gd-1_54.dll!std::_Wrap_alloc<std::allocator<wchar_t> >::deallocate(wchar_t * _Ptr, unsigned int _Count) Line 888 C++ boost_filesystem-vc110-mt-gd-1_54.dll!std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >::_Tidy(bool _Built, unsigned int _Newsize) Line 2265 C++ boost_filesystem-vc110-mt-gd-1_54.dll!std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >::~basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >() Line 965 C++ boost_filesystem-vc110-mt-gd-1_54.dll!boost::filesystem::path::~path() C++ blah.exe!CPlanarApp::InitInstance() Line 152 C++ mfc110ud.dll!AfxWinMain(HINSTANCE__ * hInstance, HINSTANCE__ * hPrevInstance, wchar_t * lpCmdLine, int nCmdShow) Line 37 C++ blah.exe!wWinMain(HINSTANCE__ * hInstance, HINSTANCE__ * hPrevInstance, wchar_t * lpCmdLine, int nCmdShow) Line 26 C++ blah.exe!__tmainCRTStartup() Line 528 C blah.exe!wWinMainCRTStartup() Line 377 C kernel32.dll!75ce33aa() Unknown [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll] ntdll.dll!76f09ef2() Unknown ntdll.dll!76f09ec5() Unknown The boost::filesystem::path destructor is being called and is causing a crash. I do not understand how the first two tests can pass yet there is a problem with the third test. Is there something that I am doing wrong here or does anyone have any advice please? Thanks, Patrick

3 7

[BGL] Having a cost function as weight map
by Maxime van Noppen 06 Sep '13

06 Sep '13

Hi, I can't find how to do this pretty basic thing : having a function instead of a field to compute the cost of edges for various path finding algorithms. I couldn't find the answer in the documentation and Google was of no help. Did I miss something obvious ? Example : ------------------- #include <boost/graph/dijkstra_shortest_paths.hpp> #include <boost/graph/graph_traits.hpp> #include <boost/graph/adjacency_list.hpp> struct my_edge { double cost() const { return cost_ * 2; } double cost_; }; struct my_node { }; int main() { typedef boost::adjacency_list< boost::vecS, boost::vecS, boost::directedS, my_node, my_edge > graph_t; typedef boost::graph_traits<graph_t>::vertex_descriptor vertex_t; graph_t graph; vertex_t v /*= ... */; using boost::weight_map; // Works : boost::dijkstra_shortest_paths(graph, v, weight_map(boost::get(&my_edge::cost_, graph))); // Doesn't compile : //boost::dijkstra_shortest_paths(graph, v, // weight_map(boost::get(&my_edge::cost, graph))); } ------------------- Thanks ! -- Maxime

4 8

How to build Boost binary libraries on Windows X64 using GCC
by guxiaobo1982 06 Sep '13

06 Sep '13

Hi, We are trying to develop a custom R package, which will utilize Boost and RCPP. We are using R 3.0.1 64bit, and the corresponding RTools3 toolchain, which can be downloaded from CRAN, such as http://cran.at.r-project.org/bin/windows/Rtools/Rtools31.exe. Upon our environment we can build test R packages which with C++ srouces and without any other third-part denpendencies, and can use Eclipse C++ IDE to develop demo C++ programes. When comes to Boost, there is a problem to build the binary libraries such as regex, we found a guide at http://fischerlaender.de/development/using-boost-c-libraries-with-gcc-g-und…, it only tells how to use a pre-built Boost binary, and we have tried the steps at http://stackoverflow.com/questions/5299468/unable-to-build-boost-libraries-… 1. cd to toos\build\v2\engine (there is not a src directory) 2. build.bat gcc 3. put the new bjam.exe and b2.exe into the root the boost 4. execute b2 under root of boost It seems boost still looks for cl (which is from the visual studio toolchain) So do you have a pre-built boost library for windows and gcc, or what's the wright way? Thanks. Xiaobo Gu

1 0

[spirit] Qi rule for GPS NMEA
by Michael Powell 06 Sep '13

06 Sep '13

Hello, I'm digging into a qi rule for GPS NMEA and want to approach it as a kind of 2-pass parser. First pass to extract the message and hex-formatted checksum. Next pass to parse out the actual messages from the message. I believe I comprehend how to go about the second pass. For the first pass, I want to parse $XYZ*HH\r\n. That's the literal '$', and everything between there and the literal '*', followed by the two hex characters, as a complete field, followed by the terminal CR+LF. How do I express the "all characters excluding '*'" for the NMEA message? Then the hex field? Thanks... Regards, Michael Powell

3 9