October 2012 - Boost-users - lists.boost.org

question on multi_index_container
by John M. Dlugosz 31 Oct '12

31 Oct '12

I created a multi_index_container in a way to emulate and enhance a std::set. That is, ordered_unique on some key extraction I specified. Like a std::set, inserting a "duplicate" will not do the assignment at all and the old value remains. However, what I want is for the new item to replace the old with the same key. Is there an easy or straightforward way to configure multi_index_container to do this?

2 1

(no subject)
by Yiğit Çağrı Akkaya 31 Oct '12

31 Oct '12

Hi, I have an MFC application. There are plenty of dll's written by us. In one dll module, we use boost. However, on start up of application, it throws several assertions about loading dll. I know assertions are available only for debug mode, but we want to get rid of every small problem in order to provide a stable release. I made web search and I found this thread: http://lists.boost.org/threads-devel/2009/06/0476.php This belongs to 2009 and Boost 1.39. We use Boost 1.48 and Visual Studio 2008 SP1. Thread says that this happens when MFC application statically linked to boost. Probably, nothing changed up to 1.48 because I found that line and commented it out(extern BOOL (WINAPI * const _pRawDllMain)(HANDLE, DWORD, LPVOID)=&dll_callback;). Is there a macro defined in boost to differentiate static and dynamic builds? If there is a macro, we are planning to wrap macro around that line. Or is there any better solution for this? Thanks in advance...

1 0

[phoenix] std::function doesn't work with phoenix ?
by Kamil Zubair 31 Oct '12

31 Oct '12

When I try to do this is VC++ 2010 : #include <functional> #include <boost\bind.hpp> #include <boost\phoenix.hpp> float Func() { return 1.f; } typedef std::function<float()> F; int main() { F f2 = boost::phoenix::bind(&Func); } It failed to compile, but when I change boost::phoenix::bind to boost::bind it compiled just fine. What's going on ? I thought phoenix::bind and boost::bind is interchangeable.

2 1

[Boost.Test] What's the best way to make custom assertions?
by legalize+jeeves＠mail.xmission.com 31 Oct '12

31 Oct '12

[Please do not mail me a copy of your followup] I want to make custom assertion methods that report the failure location as the place where the custom assertion is invoked, not the location where the BOOST_REQUIRE_xxx macros are used in the implementation of the custom assertion. In my own code, when I wanted to do report the point of invocation instead of the point of implementation, I implemented my code along the lines of void report(char const* file, int line) { // ... // output a message using line and file // ... } #define REPORT() report(__FILE__, __LINE__) void code() { REPORT(); // report something interesting here } When I look at how the assertion macros are implemented in Boost.Test, it seems that __FILE__ and __LINE__ are substituted down pretty far in the macro invocation chain. This means that if I want to write my own custom assertion that reports messages at the point of invocation and not at the point of implementation, I have to call these very low-level macro facilities and duplicate a bunch of stuff that's in Boost.Test. One thing I don't want to do is make a gigantic multi-line macro for my custom assertion. I really don't like using macros for things that could be done with functions and a custom assertion, IMO, falls into that category. Is there a clean way of implementing a custom assertion in the manner I've described without replicating a bunch of the intermediate layers of Boost.Test's macros? Gennady, if you're reading this and there isn't a clean way of doing what I'd like, are you willing to accept a refactoring changeset that promotes __FILE__ and __LINE__ arguments higher in the macro call chain? -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>

3 7

[mpi] many undefined references to serialize<boost::mpi::detail::mpi_datatype_oarchive>
by Brian Budge 30 Oct '12

30 Oct '12

Hi all - I've got a class hierarchy that can already be serialized into text or binary archives. I'm explicitly instantiating the template functions for serialize and/or load/save. I'm trying to add the capability to have boost mpi perform the serialization through send/recv/broadcast. I've added explicit instantiations for the boost::mpi::packed_iarchive and packed_oarchive. My code compiles, but at the end I get a bunch of undefined references for serialize<boost::mpi::detail::mpi_datatype_oarchive>. I can add the explicit instantiations for this oarchive, and this seems to fix my linking issue, but this seems broken, i.e. I should not have to deal with anything in a boost::detail namespace? Is there another suggestion for how to get this to work? Thanks, Brian

5 11

[MPI] missing symbols using serialization's static library design
by Barrett, Brian W 30 Oct '12

30 Oct '12

Hello all - On Mac OS X Lion, we're seeing errors when linking our application using Boost.MPI. The application is rather large and uses Boost.Serialization for both checkpoint/restart and MPI communication. The checkpoint/restart bits made serialization a bit of a disaster in terms of compile times (due to headers including basically every other header in the project). To solve that problem, we followed the Boost.Serialization advice on static libraries, and all is good. Except that on Lion (and possibly elsewhere, but definitely on Lion) using the gcc front-end (i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)), we're seeing link failures due to serialization calls for MPI archivers not being found when compiling with -O2 or higher on Boost 1.50.0 and 1.51.0: CXXLD sst.x Undefined symbols for architecture x86_64: "void SST::Introspector::serialize<boost::mpi::packed_iarchive>(boost::mpi::packe d_iarchive&, unsigned int)", referenced from: boost::archive::detail::iserializer<boost::mpi::packed_iarchive, SST::Introspector>::load_object_data(boost::archive::detail::basic_iarchive &, void*, unsigned int) const in introspectedComponent.o boost::archive::detail::iserializer<boost::mpi::packed_iarchive, SST::Introspector>::load_object_data(boost::archive::detail::basic_iarchive &, void*, unsigned int) consti n simulation.o While I could simply explicitly insatiate the missing archivers, that seems like a bad idea for something in the detail namespace and it appears that the list of archivers I'd need to instantiate has changed over time. Is there a better solution to the problem? There's a test case the exhibits the problem available here on our Google code project bug tracker. It's essentially the Boost.Serialization demo_pimpl example, but using MPI instead of a text archiver. The code is at: http://sst-simulator.googlecode.com/issues/attachment?aid=280000000&name=mp i_serialization_test.tar.gz&token=1MTkBuFrhrfUUAZRZYH3kZrElIg%3A13500682075 60 Thanks, Brian -- Brian W. Barrett Scalable System Software Group Sandia National Laboratories

3 5

[boost build] Where/How is python found?
by Gottlob Frege 30 Oct '12

30 Oct '12

I'm trying to determine how boost build finds the python install. I see in boost\tools\build\v2\tools\python-config.jam that it looks in the Windows Registry (for NT at least). But this only checks for Python 2.4, 2.3, 2.2. It also seems to look for python.exe in the PATH. But I can't seem to find the code that does that. Any ideas? In particular, I would like to change it to actually check for an include directory once it finds python.exe. On my system, it finds a 'rogue' python.exe that is not part of the full python install (thus no include folder). Tony

2 2

[Boost.Test] Always leaving test code active in Release mode
by Ruediger Berlich 30 Oct '12

30 Oct '12

Hi there, we use Boost.Test to do Unit tests for the Geneva library, covering parametric optimization. Code for tests is included directly in most classes, so tests can be written "on-site", whenever a new feature is added. However, in Release mode, usually test-functions are *not* included (masked by an "#ifdef GEMTESTING" block), but can be switched on by the user prior to compilation. When this happens, it means that classes being tested have a different interface than classes without the GEMTESTING-define set. Users are meant to derive their own classes from the Geneva's core classes and overload certain functions. They are also provided with a test infrastructure, that allows them to test their own code without too much trouble for compliance with the libraries rules (as just one example, it is being tested whether their code can be serialiazed using Boost.Serialization and whether de-serialized classes are identical to the one being serialized). However, when users compile our (Open Source) library with the GEMTESTING-define set and then compile their own code without this flag, they will include headers with a different interface than the one being used to compile the library. This has led to some very hard to detect failures. We are looking for ways to circumvent this source of errors and so far see three options: a) We can give compiled libraries a different name when the test-code is included (e.g. libgeneva-testing.so or the likes) b) There could be sanity checks in the code, e.g. with a static function returning different values depending on whether test code is activated or not c) We can always compile the test code, even in Release mode, by removing the "#ifdef GEMTESTING", this leaving no ambiguities regarding the API Option a) will effectively double compilation times, as we will always have to compile both library variants. It would also force us to make many changes in the CMake-based build system. Option b) leaves a source for frustration for our users, as they will only discover the problem when compiling and/or running their code. Option c) is the easiest to implement, but leaves open some questions (see below) *** My question now is, what the trade-offs of option c) are (i.e., leaving all test code in and always linking with the Boost.Test libraries). Do we loose anything ? Will this affect our ability to debug the code ? Are there runtime-penalties ? Note that none of the test-functions is called during normal execution. *** Of course any views on a good strategy for the above scenario are also appreciated. In any case thanks and best regards, Ruediger

1 0

Typedef rejected when disambiguating a call to boost::assign
by mark pashley 30 Oct '12

30 Oct '12

I am trying to initialise a std::map of std::set using boost::assign, as follows: typedef std::set< uint32_t > the_set_t; typedef std::map< uint32_t, the_set_t > the_map_t; the_map_t data = boost::assign::map_list_of< uint32_t, the_set_t > > // bad line ( 1, boost::assign::list_of(10)(20)(30) ) Unfortunately this is rejected by GCC 4.4.6, and results in a large amount of errors, (attached below). The problem is caused by the use of the typedef the_set_t. If the typedef is replaced with std::set<uint32_t> the code compiles and works correctly. the_map_t data = boost::assign::map_list_of< uint32_t, std::set< uint32_t > > The error produced is as follows: map-assign.cpp:19: error: conversion from ‘bool’ to non-scalar type ‘the_map_t’ requested In file included from /opt/boost_1_51_0/boost/assign/list_of.hpp:397, from map-assign.cpp:7: /opt/boost_1_51_0/boost/preprocessor/iteration/detail/local.hpp: In member function ‘boost::assign_detail::generic_list<T>& boost::assign_detail::generic_list<T>::operator() (const U&, const U0&) [with U = int, U0 = boost::assign_detail::generic_list<int>, T = int]’: map-assign.cpp:17: instantiated from here /opt/boost_1_51_0/boost/preprocessor/iteration/detail/local.hpp:37: error: functional cast expression list treated as compound expression In file included from /opt/boost_1_51_0/boost/iterator/iterator_categories.hpp:15, from /opt/boost_1_51_0/boost/iterator/detail/facade_iterator_category.hpp:7, from /opt/boost_1_51_0/boost/iterator/iterator_facade.hpp:14, from /opt/boost_1_51_0/boost/range/iterator_range_core.hpp:23, from /opt/boost_1_51_0/boost/range/iterator_range.hpp:13, from /opt/boost_1_51_0/boost/assign/list_of.hpp:20, from map-assign.cpp:7: /opt/boost_1_51_0/boost/mpl/eval_if.hpp: At global scope: /opt/boost_1_51_0/boost/mpl/eval_if.hpp: In instantiation of ‘boost::mpl::eval_if_c<false, boost::range_const_iterator< boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)>, boost::range_mutable_iterator< boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)> >’: /opt/boost_1_51_0/boost/range/iterator.hpp:63: instantiated from ‘boost::range_iterator< boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)>’ /opt/boost_1_51_0/boost/range/iterator_range_core.hpp:72: instantiated from ‘bool boost::iterator_range_detail::less_than(const Left&, const Right&) [with Left = boost::assign_detail::converter< boost::assign_detail::generic_list<int>, std::_Deque_iterator<int, int&, int*> >, Right = boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)]’ /opt/boost_1_51_0/boost/assign/list_of.hpp:274: instantiated from ‘bool boost::assign_detail::operator<(const boost::assign_detail::converter<T, I>&, const Range&) [with T = boost::assign_detail::generic_list<int>, I = std::_Deque_iterator<int, int&, int*>, Range = boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)]’ /opt/boost_1_51_0/boost/assign/list_of.hpp:292: instantiated from ‘bool boost::assign_detail::operator>(const Range&, const boost::assign_detail::converter<T, I>&) [with T = boost::assign_detail::generic_list<int>, I = std::_Deque_iterator<int, int&, int*>, Range = boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)]’ map-assign.cpp:19: instantiated from here /opt/boost_1_51_0/boost/mpl/eval_if.hpp:60: error: no type named ‘type’ in ‘struct boost::range_mutable_iterator< boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)>’ In file included from /opt/boost_1_51_0/boost/range/iterator_range.hpp:13, from /opt/boost_1_51_0/boost/assign/list_of.hpp:20, from map-assign.cpp:7: /opt/boost_1_51_0/boost/range/iterator_range_core.hpp: In function ‘bool boost::iterator_range_detail::less_than(const Left&, const Right&) [with Left = boost::assign_detail::converter<boost::assign_detail::generic_list<int>, std::_Deque_iterator<int, int&, int*> >, Right = boost::assign_detail::generic_list<std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)]’: /opt/boost_1_51_0/boost/assign/list_of.hpp:274: instantiated from ‘bool boost::assign_detail::operator<(const boost::assign_detail::converter<T, I>&, const Range&) [with T = boost::assign_detail::generic_list<int>, I = std::_Deque_iterator<int, int&, int*>, Range = boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)]’ /opt/boost_1_51_0/boost/assign/list_of.hpp:292: instantiated from ‘bool boost::assign_detail::operator>(const Range&, const boost::assign_detail::converter<T, I>&) [with T = boost::assign_detail::generic_list<int>, I = std::_Deque_iterator<int, int&, int*>, Range = boost::assign_detail::generic_list<std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&)]’ map-assign.cpp:19: instantiated from here /opt/boost_1_51_0/boost/range/iterator_range_core.hpp:72: error: no matching function for call to ‘begin(boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (&) (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&))’ /opt/boost_1_51_0/boost/range/iterator_range_core.hpp:72: error: no matching function for call to ‘end(boost::assign_detail::generic_list< std::pair<unsigned int, std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > > > (&) (const unsigned int&, const std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> >&))’ In file included from map-assign.cpp:7: /opt/boost_1_51_0/boost/assign/list_of.hpp: In member function ‘Container boost::assign_detail::converter<DerivedTAssign, Iterator>::convert( const Container*, boost::assign_detail::default_type_tag) const [with Container = int, DerivedTAssign = boost::assign_detail::generic_list<int>, Iterator = std::_Deque_iterator<int, int&, int*>]’: /opt/boost_1_51_0/boost/assign/list_of.hpp:142: instantiated from ‘Container boost::assign_detail::converter<DerivedTAssign, Iterator>::convert_to_container() const [with Container = int, DerivedTAssign = boost::assign_detail::generic_list<int>, Iterator = std::_Deque_iterator<int, int&, int*>]’ /opt/boost_1_51_0/boost/assign/list_of.hpp:436: instantiated from ‘boost::assign_detail::generic_list<T>::operator Container() const [with Container = int, T = int]’ /opt/boost_1_51_0/boost/preprocessor/iteration/detail/local.hpp:37: instantiated from ‘boost::assign_detail::generic_list<T>& boost::assign_detail::generic_list<T>::operator()(const U&, const U0&) [with U = int, U1 = boost::assign_detail::generic_list<int>, T = int]’ map-assign.cpp:17: instantiated from here /opt/boost_1_51_0/boost/assign/list_of.hpp:163: error: functional cast expression list treated as compound expression /opt/boost_1_51_0/boost/assign/list_of.hpp:163: error: invalid cast from type ‘std::_Deque_iterator<int, int&, int*>’ to type ‘int’ What is wrong with using a typedef or is this a known limitation of `boost::assign`? -- View this message in context: http://boost.2283326.n4.nabble.com/Typedef-rejected-when-disambiguating-a-c… Sent from the Boost - Users mailing list archive at Nabble.com.

2 5

shared_ptr on aix
by Vojtech Fried 30 Oct '12

30 Oct '12

Hi, What is the status of boost/smart_ptr/detail/sp_counted_base_aix.hpp? It is not #included by default in sp_counted_base_aix.hpp. Is it safe to use or is it just an exprerimental version? We have a multiplatform application and I am trying to make some improvements for it on AIX platform. One candidate right now is to utilize sp_counted_base_aix.hpp (boost/smart_ptr/detail/sp_counted_base_aix.hpp). It implements atomic counter without (pthread) mutexes. Using it improves performance of our app up to 10%. But sp_counted_base_aix.hpp is not used by default. I had to add an #ifed to sp_counted_base.hpp to make it work. I tested the implementation with a small sample program that copied and removed shared_ptrs in multiple threads and it works. But I am still concerned. How widely is this AIX specific implementation used? How risky is it for us to use it? Best regards Vojtech

1 0

Boost.Test ordering
by John M. Dlugosz 30 Oct '12

30 Oct '12

If I make unit tests in different source files, I need to declare a BOOST_AUTO_TEST_SUITE in each one, right? At link time, these appear in some undetermined order. How can I cause them to be run in the desired order instead? —John

1 0

boost::container::vector fails to compile with C++03 compiler
by mark pashley 30 Oct '12

30 Oct '12

The following example compiles fine when using GCC 4.4.6 with the --std=c++0x flag but fails to compile in C++03 mode. #include <stdint.h> #include <boost/container/vector.hpp> struct data { int i_; boost::container::vector<data> v_; }; int main( int argc, char** argv ) { data myData; myData.i_ = 10; data myData2; myData2.i_ = 30; myData.v_.push_back( myData2 ); return 0; } It compiles successfully with g++ --std=c++0x test-cont.cpp However if I remove the --std=c++0x I get the following errors: g++ test-cont.cpp In file included from include/c++/4.4.6/memory:49, boost/container/container_fwd.hpp:36, boost/container/vector.hpp:20, from test-cont.cpp:2: include/c++/4.4.6/bits/stl_algobase.h: In static member function static _OI std::__copy_move<false, false, std::random_access_iterator_tag>:: __copy_m(_II, _II, _OI) [with _II = boost::container::constant_iterator<data, long int>, _OI = data*]: include/c++/4.4.6/bits/stl_algobase.h:397: instantiated from _OI std::__copy_move_a(_II, _II, _OI) [with bool _IsMove = false, _II = boost::container::constant_iterator<data, long int>, _OI = data*] include/c++/4.4.6/bits/stl_algobase.h:436: instantiated from _OI std::__copy_move_a2(_II, _II, _OI) [with bool _IsMove = false, _II = boost::container::constant_iterator<data, long int>, _OI = data*] include/c++/4.4.6/bits/stl_algobase.h:468: instantiated from _OI std::copy(_II, _II, _OI) [with _II = boost::container::constant_iterator<data, long int>, _OI = data*] boost/move/move.hpp:1147: instantiated from boost::copy_or_move(I, I, F, typename boost::move_detail::disable_if< boost::move_detail::is_move_iterator, void>::type*) [with I = boost::container::constant_iterator<data, long int>, F = data*] boost/container/detail/advanced_insert_int.hpp:58: instantiated from void boost::container::container_detail::advanced_insert_aux_proxy<A, FwdIt, Iterator>::copy_remaining_to(Iterator) [with A = std::allocator<data>, FwdIt = boost::container::constant_iterator<data, long int>, Iterator = data*] test-cont.cpp:21: instantiated from here include/c++/4.4.6/bits/stl_algobase.h:343: error: no match for operator= in * __result = __first.boost::container::constant_iterator<T, Difference>::operator* [with T = data, Difference = long int]() test-cont.cpp:5: note: candidates are: data& data::operator=(data&) It looks like boost::container::vector requires move semantics which I assumed would automatically use boost::move when compiled with a c++03 compiler. If I manually modify the struct data to define: a default constructor a copy constructor an assignment operator an emulated move constructor using BOOST_RV_REF an emulated move assignment operator using BOOST_RV_REF The example compiles. Having to manually add these move/copy constructors and assignment operators for C++03 is laborious. Is this a bug with boost::container? -- View this message in context: http://boost.2283326.n4.nabble.com/boost-container-vector-fails-to-compile-… Sent from the Boost - Users mailing list archive at Nabble.com.

4 5

Visual Studio Debugger "renderer" support for Boost.Container ?
by John M. Dlugosz 29 Oct '12

29 Oct '12

MS Visual Studio's Debugger comes pre-loaded with "renderers" (I forget what S.T.L. actually called them) for the containers and smart pointers supplied with the compiler. Looking at a Boost Container in the debugger is not nearly so nice. Has anyone looked into adding renderers for them?

3 2

Multiplying a matrix and vector ===> vector
by Vipin Varma 29 Oct '12

29 Oct '12

Dear all, My basic requirement is to multiply a matrix and a vector and then to store it into a vector using Boost's UBLAS. When I multiply a boost::numeric::ublas::compressed_matrix with a boost::numeric::ublas::vector using prod(matrix, vector), the output is a boost::numeric::ublas::matrix_vector_binary1. E.g. <PSEUDOCODE> boost::numeric::ublas::compressed_matrix m; boost::numeric::ublas::vector x; boost::numeric::ublas::matrix_vector_binary1<compressed_matrix, vector, ? > tmp; tmp = prod(m,x); <PSEUDOCODE> The problem is that in the third field --- which expects the operation type --- in line 3, I do not know what to enter or how to specify the type of operation; I tried '*' and 'prod' and 'vector' and 'compressed_matrix' but none work. Alternatively, I can avoid the tmp variable altogether and get a working program to copy the result of matrix-vector multiplication onto a new vector y but then I would need two multiplications. E.g. <CODE> std::copy(prod(m,x).begin(), prod(m,x).end(), y.begin()); <CODE> Any suggestions on how to declare a matrix_vector_binary1 correctly or how to get the finaly result efficiently onto a vector will be appreciated. Regards, Vipin

3 8

build process of boost code & lib creation
by danianton＠libero.it 29 Oct '12

29 Oct '12

Hi, I’am using boost in my application. I need an explanation about build process and library creation. I’d know if there is an alternative to bjam, could I use a make file made by me? It’s difficult to implement a build process? The .lib files generated by b2 process are created from the source file contained in the archive file? Thanks. Best regards, Daniele.

1 0

[Thread] Win32 TLS problem with dynamic libraries
by Сергей Захарченко 29 Oct '12

29 Oct '12

Hello, I need to build a shared plugin library with Boost libraries linked statically into it. As many may know, there's a problem with having a .tls section in Win32 dynamic libraries which are to be loaded via LoadLibrary, but Boost.Thread insists on having one. Assuming that I can guarantee that no Boost.Thread functions are called from non-Boost.Thread threads, it shouldn't be needed. Apart from patching the Boost.Thread sources, or the resulting binaries, what's the best way of eliminating it? I assume that I need to eliminate tss_pe.cpp from linkage, but I don't seem to be able to. Adding a namespace boost { void tss_cleanup_implemented() {} } to one of the library's sources doesn't help, as it results in a multiply defined symbol error (compiler MSVC2008 from Express edition). Any suggestions? Thank you, -- Sergey Zakharchenko

3 2

Boost installation inquiry
by mega deth 29 Oct '12

29 Oct '12

Hello Boost User Community, I am a big fan of boost C++ having used it for a college class to do threading. I want to get back into it and I previously installed boost on a windows machine, now dealing with a Linux machine would like some help as I have run into difficulties with the installation process. First off, I would like to build threads and regex libraries. I have gotten the first example show below to work correctly: #include <boost/lambda/lambda.hpp> #include <iostream> #include <iterator> #include <algorithm> int main() { using namespace boost::lambda; typedef std::istream_iterator<int> in; std::for_each( in(std::cin), in(), std::cout << (_1 * 3) << " " ); } My main issue is the next part. I have Boost is located in /usr/local/boost_1_51_0 I have run the following steps: 1. Go to the directory tools/build/v2/. 2. Run bootstrap.sh 3. Run b2 install --prefix=PREFIX where PREFIX is the directory where you want Boost.Build to be installed 4. Add PREFIX/bin to your PATH environment variable. For the 3rd step, I ran b2 as follows: b2 --build-dir=~/bin/Boos tC++1.51/ toolset=gcc stage My PATH looks like this: > echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/root/bin :/root/bin/BoostC++1.51/bin/ g++ I- /root/boost/ /root/bin/repos/c-projects/c++/C++Projects/Boost/testLinkToBoostLib.cpp -o example \ > ~/boost/stage/lib/libboost_ libboost_chrono.a libboost_regex.a libboost_chrono.so libboost_regex.so libboost_chrono.so.1.51.0 libboost_regex.so.1.51.0 libboost_filesystem.a libboost_system.a libboost_filesystem.so libboost_system.so libboost_filesystem.so.1.51.0 libboost_system.so.1.51.0 libboost_program_options.a libboost_thread.a libboost_program_options.so libboost_thread.so libboost_program_options.so.1.51.0 libboost_thread.so.1.51.0 Finally this is my issue: When I try to compile the test regex code with boost, I am unable to find the correct library to include. I fear that because I have this issue, that my thread library is not built as well. Is there a way to check? Can you provide what worked for you to install boost on your linux machine. c++ -I path/to/boost_1_51_0 example.cpp -o example \ ~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.a I am unable to find or even create this: libboost_regex-gcc34-mt-d-1_36.a If you have any advise or direction please let me know. Thank you! There was some talk about checking the configuration of the user-config.jam if there are linker or compile issues. But I do not think those could be the issues at the moment. Thank you in advance for looking at my issue! ~Jake

2 1

Boost random not looking so random
by Robin Rowe 28 Oct '12

28 Oct '12

I'm using boost to shuffle an array, but it's not looking as random as I would expect. Am I not using it right? The code below outputs sequences that look random mostly, but I see patterns such as 7 7 12 12 11. boost::random::mt19937 rng; boost::minstd_rand lcggen; lcggen.seed(clockTime); rng.seed(lcggen); unsigned min=1; unsigned max=15; for(unsigned i=0;i<5;i++) { boost::random::uniform_int_distribution<> dist(min,max); const int j = dist(rng); ... code that shuffles stuff using j ... min++; cout<<j<<' '; } Suggestions? Thanks! Robin -- www.cinepaint.org

3 3

cygwin build error on boost filesystem
by Kraus Philipp 27 Oct '12

27 Oct '12

Hello, I try to build the Boost 1.51 on the latest Cygwin version: I'm using this commands: export BZIP2_BINARY=bz2 export ZLIB_BINARY=z export ZLIB_INCLUDE=/cygdrive/c/Users/Administrator/Documents/zlib/1.2.7/include export ZLIB_LIBPATH=/cygdrive/c/Users/Administrator/Documents/zlib/1.2.7/lib export BZIP2_INCLUDE=/cygdrive/c/Users/Administrator/Documents/bzip2/1.0.6/include export BZIP2_LIBPATH=/cygdrive/c/Users/Administrator/Documents/bzip2/1.0.6/lib cd library/boost_1_51_0 ./bootstrap.sh ./b2 --with-exception --with-filesystem --with-math --with-random --with-regex --with-date_time --with-thread --with-system --with-program_options --with-serialization --with-iostreams --layout=system link=shared runtime-link=shared threading=multi variant=release install --prefix=../boost/1.51.0 ./boost/filesystem/path_traits.hpp: At global scope: ./boost/filesystem/path_traits.hpp:224: error: `std::wstring' has not been declared ./boost/filesystem/path_traits.hpp:228: error: ISO C++ forbids declaration of `to' with no type In file included from ./boost/filesystem/operations.hpp:25, from libs\filesystem\src\unique_path.cpp:20: ./boost/filesystem/path.hpp:378: error: ISO C++ forbids declaration of `wstring' with no type ./boost/filesystem/path.hpp:378: error: invalid use of `::' ./boost/filesystem/path.hpp:378: error: expected `;' before '&' token ./boost/filesystem/path.hpp:379: error: expected `;' before "const" ./boost/filesystem/path.hpp:379: error: ISO C++ forbids declaration of `wstring' with no type ./boost/filesystem/path.hpp:379: error: invalid use of `::' ./boost/filesystem/path.hpp:379: error: expected `;' before '&' token ./boost/filesystem/path.hpp:400: error: expected `;' before "template" ./boost/filesystem/path.hpp:409: error: ISO C++ forbids declaration of `wstring' with no type ./boost/filesystem/path.hpp:409: error: invalid use of `::' ./boost/filesystem/path.hpp:409: error: expected `;' before "generic_wstring" ... The Boost filesystem is not build on the command the full build process is stop with the error Is this an error on my installation and how can I solve the problem? Thanks a lot Phil

1 0

use boost preprocessor to generate T1 t1, T2 t2 ...
by weiqingh 27 Oct '12

27 Oct '12

hi there, I would like to use boost preprocessor to generate something like this: (for n from 0 to N with n = 2 in the following example) template <typename T1, typename T2> void foo(T1 t1, T2 t2) I have tried to use BOOST_PP_ENUM_PARAMS but cannot figure out how to get both T_i and t_i changed each time. is there some other macros I can use? any help is highly appreciated. Thanks, -- View this message in context: http://boost.2283326.n4.nabble.com/use-boost-preprocessor-to-generate-T1-t1… Sent from the Boost - Users mailing list archive at Nabble.com.

5 5

Re: [Boost-users] [boost] Fwd: Re: [system] symbol visibility and GCC vs. Clang
by Michel Morin 26 Oct '12

26 Oct '12

Fixed in r81068. Since dllexport/dllimport are not fully supported on clang (see http://llvm.org/bugs/show_bug.cgi?id=11170 ), I didn't add the macros (BOOST_SYMBOL_EXPORT/BOOST_SYMBOL_IMPORT) for the Windows platform. Regards, Michel

1 0

[unique_ptr] How should I assign unique_ptr returned from a factory function, possibly using boost::move, in C++03
by Adam Romanek 26 Oct '12

26 Oct '12

Hi, the question is: how should I assign boost::interprocess::unique_ptr returned from a factory function, possibly using boost::move, in C++03? Here's an example: --- #include <boost/interprocess/smart_ptr/unique_ptr.hpp> using namespace boost::interprocess; class my_class { public: my_class() {} }; struct my_class_deleter { void operator()(my_class *p) {} }; typedef unique_ptr<my_class, my_class_deleter> uptr; uptr create() { return uptr(); } int main() { uptr x; x = create(); // return 0; } --- The problem is that gcc fails to compile the above code saying: main.cpp:22: error: ambiguous overload for ‘operator=’ in ‘x = create()()’ ../../boost_latest/boost/interprocess/smart_ptr/unique_ptr.hpp:211: note: candidates are: boost::interprocess::unique_ptr<T, D>& boost::interprocess::unique_ptr<T, D>::operator=(boost::rv<boost::interprocess::unique_ptr<T, D> >&) [with T = my_class, D = my_class_deleter] ../../boost_latest/boost/interprocess/smart_ptr/unique_ptr.hpp:249: note: boost::interprocess::unique_ptr<T, D>& boost::interprocess::unique_ptr<T, D>::operator=(int boost::interprocess::unique_ptr<T, D>::nat::*) [with T = my_class, D = my_class_deleter] I use gcc v4.4.3 and Boost v1.51.0. BTW: I posted the same question on StackOverflow: http://stackoverflow.com/questions/13086428/how-should-i-assign-boostinterp…

1 0

Re: [Boost-users] boost wave memory leak
by Hartmut Kaiser 26 Oct '12

26 Oct '12

> I apologize if this is not standard procedure (not quite sure what > that is) but I was wondering if you've been able to reproduce the issue > using the information from my last email. Sorry, I have not had any time to look into this issue. Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu > > Rob Conde > > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Hartmut Kaiser > Sent: Monday, October 22, 2012 8:00 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] boost wave memory leak > > > I'm getting a report of a memory leak when using boost wave. I see a > > similar problem at: > > > > https://svn.boost.org/trac/boost/ticket/4346 > > > > but supposedly that is fixed for a while. > > > > The call stack is: > > How did you get that call stack? What do I need to do to reproduce this > problem? > > Regards Hartmut > --------------- > http://boost-spirit.com > http://stellar.cct.lsu.edu > > > > > > MyDll.dll!operator new(unsigned int count, const std::nothrow_t & > > __formal) > > Line 18 + 0x9 bytes C++ > > > > MyDll.dll!operator new[](unsigned int count, const std::nothrow_t & x) > > Line > > 15 + 0xd bytes C++ > > > > MyDll.dll!boost::default_user_allocator_new_delete::malloc(const > unsigned > > int bytes) Line 97 + 0xe bytes C++ > > > > MyDll.dll!boost::pool<boost::default_user_allocator_new_delete>::mallo > > c_ne > > ed > > _resize() Line 693 + 0x9 bytes C++ > > > > > MyDll.dll!boost::pool<boost::default_user_allocator_new_delete>::malloc() > > Line 432 C++ > > > > MyDll.dll!boost::singleton_pool<boost::fast_pool_allocator_tag,12,boos > > t::d > > ef > > ault_user_allocator_new_delete,boost::mutex,32,0>::malloc() Line 137 > > + 0xb > > bytes C++ > > > > > MyDll.dll!boost::fast_pool_allocator<std::_List_nod<boost::wave::cpplexer: > > :l > > ex_token<boost::wave::util::file_position<boost::wave::util::flex_stri > > ng<c > > ha > > r,std::char_traits<char>,std::allocator<char>,boost::wave::util::CowSt > > ring > > <b > > oost::wave::util::AllocatorStringStorage<char,std::allocator<char> > > >,char *> > > > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > >::_Node,boost::default_user_allocator_new_delete,boost::mutex,32,0>:: > > >al > > >loca > > te(const unsigned int n) Line 419 + 0xb bytes C++ > > > > MyDll.dll!std::list<boost::wave::cpplexer::lex_token<boost::wave::util > > ::fi > > le > > > _position<boost::wave::util::flex_string<char,std::char_traits<char>,std:: > > al > > locator<char>,boost::wave::util::CowString<boost::wave::util::Allocato > > rStr > > in > > gStorage<char,std::allocator<char> >,char *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > >>::_Buynode() > > Line 1172 + 0x7 bytes C++ > > > > MyDll.dll!std::list<boost::wave::cpplexer::lex_token<boost::wave::util > > ::fi > > le > > > _position<boost::wave::util::flex_string<char,std::char_traits<char>,std:: > > al > > locator<char>,boost::wave::util::CowString<boost::wave::util::Allocato > > rStr > > in > > gStorage<char,std::allocator<char> >,char *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > >::list<boost::wave::cpplexer::lex_token<boost::wave::util::file_posit > > >io > > >n<bo > > ost::wave::util::flex_string<char,std::char_traits<char>,std::allocato > > r<ch > > ar > > >,boost::wave::util::CowString<boost::wave::util::AllocatorStringStora > > >ge > > ><cha > > r,std::allocator<char> >,char *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> >() Line > > >436 > > + 0x68 bytes C++ > > > > MyDll.dll!`dynamic initializer for > > > 'boost::wave::util::impl::gen_unput_queue_iterator<boost::wave::cpplexer:: > > le > > x_iterator<boost::wave::cpplexer::lex_token<boost::wave::util::file_po > > siti > > on > > <boost::wave::util::flex_string<char,std::char_traits<char>,std::alloc > > ator > > <c > > har>,boost::wave::util::CowString<boost::wave::util::AllocatorStringSt > > har>or > > har>age< > > char,std::allocator<char> >,char *> > > > > > >,boost::wave::cpplexer::lex_token<boost::wave::util::file_position<bo > > >os > > >t::w > > ave::util::flex_string<char,std::char_traits<char>,std::allocator<char > > >,bo > > os > > t::wave::util::CowString<boost::wave::util::AllocatorStringStorage<cha > > r,st > > d: > > :allocator<char> >,char *> > > > > >,std::list<boost::wave::cpplexer::lex_token<boost::wave::util::file_p > > >os > > >itio > > n<boost::wave::util::flex_string<char,std::char_traits<char>,std::allo > > cato > > r< > > char>,boost::wave::util::CowString<boost::wave::util::AllocatorStringS > > char>to > > char>rage > > <char,std::allocator<char> >,char *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > > >>::last''() > > Line 155 + 0x28 bytes C++ > > > > msvcr90d.dll!__initterm() + 0x1c bytes > > > > > > _______________________________________________ > > Boost-users mailing list > > Boost-users(a)lists.boost.org > > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] boost wave memory leak
by Hartmut Kaiser 26 Oct '12

26 Oct '12

> I'm getting a report of a memory leak when using boost wave. I see a > similar problem at: > > https://svn.boost.org/trac/boost/ticket/4346 > > but supposedly that is fixed for a while. > > The call stack is: How did you get that call stack? What do I need to do to reproduce this problem? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu > > MyDll.dll!operator new(unsigned int count, const std::nothrow_t & > __formal) > Line 18 + 0x9 bytes C++ > > MyDll.dll!operator new[](unsigned int count, const std::nothrow_t & x) > Line > 15 + 0xd bytes C++ > > MyDll.dll!boost::default_user_allocator_new_delete::malloc(const unsigned > int bytes) Line 97 + 0xe bytes C++ > > MyDll.dll!boost::pool<boost::default_user_allocator_new_delete>::malloc_ne > ed > _resize() Line 693 + 0x9 bytes C++ > > MyDll.dll!boost::pool<boost::default_user_allocator_new_delete>::malloc() > Line 432 C++ > > MyDll.dll!boost::singleton_pool<boost::fast_pool_allocator_tag,12,boost::d > ef > ault_user_allocator_new_delete,boost::mutex,32,0>::malloc() Line 137 + > 0xb > bytes C++ > > MyDll.dll!boost::fast_pool_allocator<std::_List_nod<boost::wave::cpplexer: > :l > ex_token<boost::wave::util::file_position<boost::wave::util::flex_string<c > ha > r,std::char_traits<char>,std::allocator<char>,boost::wave::util::CowString > <b > oost::wave::util::AllocatorStringStorage<char,std::allocator<char> >,char > *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > >::_Node,boost::default_user_allocator_new_delete,boost::mutex,32,0>::al > >loca > te(const unsigned int n) Line 419 + 0xb bytes C++ > > MyDll.dll!std::list<boost::wave::cpplexer::lex_token<boost::wave::util::fi > le > _position<boost::wave::util::flex_string<char,std::char_traits<char>,std:: > al > locator<char>,boost::wave::util::CowString<boost::wave::util::AllocatorStr > in > gStorage<char,std::allocator<char> >,char *> > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > >>::_Buynode() > Line 1172 + 0x7 bytes C++ > > MyDll.dll!std::list<boost::wave::cpplexer::lex_token<boost::wave::util::fi > le > _position<boost::wave::util::flex_string<char,std::char_traits<char>,std:: > al > locator<char>,boost::wave::util::CowString<boost::wave::util::AllocatorStr > in > gStorage<char,std::allocator<char> >,char *> > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > >::list<boost::wave::cpplexer::lex_token<boost::wave::util::file_positio > >n<bo > ost::wave::util::flex_string<char,std::char_traits<char>,std::allocator<ch > ar > >,boost::wave::util::CowString<boost::wave::util::AllocatorStringStorage > ><cha > r,std::allocator<char> >,char *> > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> >() Line > >436 > + 0x68 bytes C++ > > MyDll.dll!`dynamic initializer for > 'boost::wave::util::impl::gen_unput_queue_iterator<boost::wave::cpplexer:: > le > x_iterator<boost::wave::cpplexer::lex_token<boost::wave::util::file_positi > on > <boost::wave::util::flex_string<char,std::char_traits<char>,std::allocator > <c > har>,boost::wave::util::CowString<boost::wave::util::AllocatorStringStor > har>age< > char,std::allocator<char> >,char *> > > > > >,boost::wave::cpplexer::lex_token<boost::wave::util::file_position<boos > >t::w > ave::util::flex_string<char,std::char_traits<char>,std::allocator<char>,bo > os > t::wave::util::CowString<boost::wave::util::AllocatorStringStorage<char,st > d: > :allocator<char> >,char *> > > > >,std::list<boost::wave::cpplexer::lex_token<boost::wave::util::file_pos > >itio > n<boost::wave::util::flex_string<char,std::char_traits<char>,std::allocato > r< > char>,boost::wave::util::CowString<boost::wave::util::AllocatorStringSto > char>rage > <char,std::allocator<char> >,char *> > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > >>::last''() > Line 155 + 0x28 bytes C++ > > msvcr90d.dll!__initterm() + 0x1c bytes > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 2

How can I make the libboost_regex.a static library?
by Scott Johnson 26 Oct '12

26 Oct '12

Transitioning an application from CentOS 5 to CentOS 6 and I noticed that neither the boost-devel nor boost-static rpms contain the libboost_regex.a static library. The boost-static rpm has most of the static libs but not that one. The CentOS 5 boost-devel package had the static library. I know dynamic libraries are encouraged but I still need the static lib. I grabbed the boost src rpm. I guess I need to build a custom version of the static rpm, but not sure yet which Makefile or where to make a change to get the libboost_regex.a. Thanks for any help.

2 1