- Boost-users - lists.boost.org

boost 1.54: problem with building documentation.
by Paul K 22 Feb '16

22 Feb '16

Hallo people. I need to have documentation in man pages format on my ubuntu 14.04. Unfortunatelly, I fail with this task. The following are the steps I've performed. In step 11 I do "../b2" instead "../b2 man" just to highlight that the problem is not related to building the man pages. Of course "../b2 man" fails as well Could You please help me with it? 1. install following packages for man pages build. lubuntu.14.04$ sudo apt-get install xsltproc lubuntu.14.04$ sudo apt-get install doxygen 2. lubuntu.14.04$ dpkg --list | grep libboost-all ii libboost-all-dev 1.54.0.1ubuntu1 i386 Boost C++ Libraries development files (ALL) (default version) 3. download boost_1_54_0.tar.bz2, unpack to ~/ 4. cd ~/boost_1_54_0 5. ./bootstrap prepares build configuration and puts it to project-config.jam. 6. ./b2 builds whole the boost libraries, but does not install them into the system. 7. lubuntu.14.04$ export BOOST_ROOT=/home/userp/boost_1_54_0 8. lubuntu.14.04$ cd ~/boost.doc/ 9. lubuntu.14.04$ ~/boost_1_54_0/tools/boostbook/setup_boostbook.sh Downloading DocBook XSLT Stylesheets version 1.75.2... Expanding DocBook XSLT Stylesheets into /home/userp/boost.doc/docbook-xsl-1.75.2...done. Downloading DocBook XML DTD version 4.2... Expanding DocBook XML DTD into /home/userp/boost.doc/docbook-dtd-4.2... done. Searching for xsltproc... /usr/bin/xsltproc. Searching for Doxygen... /usr/bin/doxygen. Searching for Java... /usr/bin/java. Downloading FOP distribution version 0.94... Expanding FOP distribution into /home/userp/boost.doc/fop-0.94... done. Updating Boost.Jam configuration in /home/userp/user-config.jam... done. Done! Execute "bjam --v2" in a documentation directory to generate documentation with BoostBook. If you have not already, you will need to compile Boost.Jam. 10. lubuntu.14.04$ cd ~/boost_1_54_0/doc 11. lubuntu.14.04$ ../b2 Performing configuration checks - has_icu builds : yes (cached) /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:1099: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p../bin.v2/libs/filesystem/build/gcc-4.9.3/release/link-static>libboost_filesystem.a error: previous virtual target { gcc%gcc.archive-libboost_filesystem.a.STATIC_LIB { gcc%gcc.compile.c++-codecvt_error_category.o.OBJ { codecvt_error_category.cpp.CPP } } { gcc%gcc.compile.c++-operations.o.OBJ { operations.cpp.CPP } } { gcc%gcc.compile.c++-path.o.OBJ { path.cpp.CPP } } { gcc%gcc.compile.c++-path_traits.o.OBJ { path_traits.cpp.CPP } } { gcc%gcc.compile.c++-portability.o.OBJ { portability.cpp.CPP } } { gcc%gcc.compile.c++-unique_path.o.OBJ { unique_path.cpp.CPP } } { gcc%gcc.compile.c++-utf8_codecvt_facet.o.OBJ { utf8_codecvt_facet.cpp.CPP } } { gcc%gcc.compile.c++-windows_file_codecvt.o.OBJ { windows_file_codecvt.cpp.CPP } } } error: created from ../libs/filesystem/build/boost_filesystem error: another virtual target { gcc%gcc.archive-libboost_filesystem.a.STATIC_LIB { gcc%gcc.compile.c++-codecvt_error_category.o.OBJ { codecvt_error_category.cpp.CPP } } { gcc%gcc.compile.c++-operations.o.OBJ { operations.cpp.CPP } } { gcc%gcc.compile.c++-path.o.OBJ { path.cpp.CPP } } { gcc%gcc.compile.c++-path_traits.o.OBJ { path_traits.cpp.CPP } } { gcc%gcc.compile.c++-portability.o.OBJ { portability.cpp.CPP } } { gcc%gcc.compile.c++-unique_path.o.OBJ { unique_path.cpp.CPP } } { gcc%gcc.compile.c++-utf8_codecvt_facet.o.OBJ { utf8_codecvt_facet.cpp.CPP } } { gcc%gcc.compile.c++-windows_file_codecvt.o.OBJ { windows_file_codecvt.cpp.CPP } } } error: created from ../libs/filesystem/build/boost_filesystem error: added properties: <auto-index-internal>off <auto-index-no-duplicates>off <auto-index-section-names>on <auto-index-verbose>off <auto-index>off <format>docbook error: removed properties: <format>html /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:484: in actualize-no-scanner from module object(file-target)@3468 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3468 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:836: in actualize-sources from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:834: in actualize-sources from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:834: in actualize-sources from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build-system.jam:720: in load from module build-system /home/userp/boost_1_54_0/tools/build/v2/kernel/modules.jam:289: in import from module modules /home/userp/boost_1_54_0/tools/build/v2/kernel/bootstrap.jam:139: in boost-build from module /home/userp/boost_1_54_0/boost-build.jam:17: in module scope from module regards

1 0

boost::any constructors
by David 22 Feb '16

22 Feb '16

Hi, boost::any has a perfect forward constructor declared as: template<typename ValueType> any(ValueType&& value , typename boost::disable_if<boost::is_same<any&, ValueType> >::type* = 0 // disable if value has type `any&` , typename boost::disable_if<boost::is_const<ValueType> >::type* = 0) // disable if value has type `const ValueType&&` : content(new holder< typename decay<ValueType>::type >(static_cast<ValueType&&>(value))) {} The is_const SFINAE exclusion forces const types to the regular copy constructor: template<typename ValueType> any(const ValueType & value) : content(new holder< BOOST_DEDUCED_TYPENAME remove_cv<BOOST_DEDUCED_TYPENAME decay<const ValueType>::type>::type >(value)) {} What is different about how the regular copy constructor treats a constant value than what the perfect forward construct would do if the is_const exclusion were removed? Thanks, David

2 1

Nested BOOST_FOREACH crash
by peyman＠ausdia.com 22 Feb '16

22 Feb '16

Good Day Boosters! I am experiencing sporadic crashes that look like memory problem when I have nested (2 level) BOOST_FOREACH loops. Reason I say it looks like memory problem is because slightest change will make it crash or not crash. For example, adding a simple cout would change it! I cannot provide a testcase. So I am just wondering if anybody has experienced the same, or know what could be going on. I am using Boost 1.57. Cheers, Peyman

2 1

Need help when adapting boost 1.59.0 to WinRT
by Nguyễn Trung Duy 22 Feb '16

22 Feb '16

Dear Boost team, I need your help with adapting boost 1.59 to WinRT. I am working on boost and reSIProcate. I built boost and integrated it with reSIProcate project. However, when build reflow project, I got stuck with bellow bugs. I wonder with your great experiences, could you please give me some advice. The error happens at line 96 : #if defined(BOOST_ASIO_WINDOWS_RUNTIME) const int max_addr_v4_str_len = 256; const int max_addr_v6_str_len = 256; typedef unsigned __int32 u_long_type; typedef unsigned __int16 u_short_type; struct in4_addr_type { u_long_type s_addr; }; // error at here And the logs: *\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3927: '->': trailing return type is not allowed after a non-function declarator (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3484: syntax error: expected '->' before the return type (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3613: missing return type after '->' ('int' assumed) (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3646: 'S_addr': unknown override specifier (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3927: '->': trailing return type is not allowed after a non-function declarator (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3484: syntax error: expected '->' before the return type (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3613: missing return type after '->' ('int' assumed) (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3646: 'Byte': unknown override specifier (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ',' before '[' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ')' before ';' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ';' before ')' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2059: syntax error: ')' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(61): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(147): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(153): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)* Thanks you so much!!!! *--* *Best Regards,* *NGUYEN TRUNG DUY* *Android Developer* *Mobile*: (+84)977 46 12 23 *Skype :* trungduy150388 *Website*: http://nguyentrungduy.com/ *Blog*: http://dbox.nguyentrungduy.com/ *Github*: https://github.com/nguyentrungduy

2 2

Newbie
by Shan Wijesinghe 22 Feb '16

22 Feb '16

Hi all, I'm a new member to C++ boost and I have a fairly good knowledge in programming in C++. I'm very much excited to join this group and I need directions from the senior members on how to start myself. Please help me here. Thanks in advance. regards, DilSHAN.

6 11

Query on Boost.DLL
by Leo Carreon 21 Feb '16

21 Feb '16

Hi, I have been reading the Boost.DLL documentation. Can a single plugin support multiple API’s? If yes, when the multiple API’s are used at the same time; will there be only one instance of the plugin loaded or will there be multiple instances loaded? Regards, Leo

2 1

Boost.DLL
by Leo Carreon 21 Feb '16

21 Feb '16

Hi, Can anyone please let me know what the status of the Boost.DLL library is? Regards, Leo

2 1

[coroutine] - only std exceptions are caught from coroutines
by Tamas.Ruszkai＠leica-geosystems.com 21 Feb '16

21 Feb '16

3 4

[Interprocess] Communication between x86 and x64 issue
by Toni Neubert 19 Feb '16

19 Feb '16

I want to communicate between different platforms using boost interprocess. I am using vc12 and boost 1.58 on windows 7. My code below is a very simple example, that should work. But it doesn't for communications between different platforms... If I create it in x64 and open in win32, the process stuck at a lock at function try_based_lock in boost/int/sync/detail/common_algorithms.hpp In the other way around: win32 create, x64 open: the process crashes at name_length in segment_manager_helper.hpp while trying to find the name in index (priv_generic_find in segment_manager). #include <iostream> #include <boost/interprocess/managed_shared_memory.hpp> int main() { namespace bip = boost::interprocess; // open in WIN32, create in x64 #ifdef _WIN32 bip::managed_shared_memory msm(bip::open_only, "TestIPC"); #elsif X64 bip::shared_memory_object::remove("TestIPC"); bip::managed_shared_memory msm(bip::create_only, "TestIPC", 4096); msm.construct<uint32_t>("Data")[1](10); #endif // Get Data and print it auto data = msm.find<uint32_t>("Data"); if (data.second == 1) { std::cout << *data.first << std::endl; } std::cin.ignore(); return 0; } Does anybody have experience in this? Thank you in advance!

3 2

Re: [Boost-users] [Serialization] This compiles; but does it work?
by Bjorn Reese 19 Feb '16

19 Feb '16

On 02/19/2016 04:20 AM, Merrill Cornish wrote: > Can anyone tell me if this will work, or do I need to implement the > serialize() function? When you are doing different things for the input and output archives then it is better to split serialization into load and save: #include <boost/filesystem/path.hpp> #include <boost/serialization/split_free.hpp> namespace boost { namespace serialization { template <typename Archive> void serialize(Archive& ar, filesystem::path& p, const unsigned int version) { split_free(ar, p, version); } template<class Archive> void save(Archive & ar, const filesystem::path& p, unsigned int version) { ar << p.string(); } template<class Archive> void load(Archive & ar, filesystem::path& p, unsigned int version) { std::string data; ar >> data; p = data; } }}

2 1