December 2009 - Boost-users

Re: [Boost-users] issues when building the boost trunk
by Vladimir Prus 05 Dec '09

05 Dec '09

Sean Farrow wrote: > Hi: > > There is currently an issue when trying to build the boost trunk. Below is > the output from the bjam program. > > C:/Program Files/boost/tools/build/v2\build-system.jam:903: syntax error at > keyword = > > C:/Program Files/boost/tools/build/v2\build-system.jam:903: syntax error at > keyword ; > > C:/Program Files/boost/tools/build/v2\build-system.jam:951: syntax error at > keyword } > > don't know how to make all > > ...found 1 target... > > ...can't find 1 target.... I do not get this error on the trunk. In fact I don't even have '=' on line 903. Are you sure this file is unmodified relative to SVN? Can you attach it? > The command line I'm using is bjam -toolset=msvc -stage This should be bjam toolset=msvc stage to be correct, and 'stage' is the default anyway. - Volodya

1 0

issues when building the boost trunk
by Sean Farrow 05 Dec '09

05 Dec '09

Hi: There is currently an issue when trying to build the boost trunk. Below is the output from the bjam program. C:/Program Files/boost/tools/build/v2\build-system.jam:903: syntax error at keyword = C:/Program Files/boost/tools/build/v2\build-system.jam:903: syntax error at keyword ; C:/Program Files/boost/tools/build/v2\build-system.jam:951: syntax error at keyword } don't know how to make all ...found 1 target... ...can't find 1 target.... The command line I'm using is bjam -toolset=msvc -stage Any help appreciated. Sean.

1 0

[Fwd: boost::function Small Buffer Optimization (SBO) and allocators]
by Chris Hite 04 Dec '09

04 Dec '09

I would really like to specify the SBO size on boost::function! How about changing the signature to?: template<typename Signature,std::size_t SBOSize=3*sizeof(void*)> class function; I've been trying to do a work around using the constructor with the allocator. I was going to define my own function class derived from the boost one, with a private one time allocator using a private buffer. This approach works find as long as constructors where the Functor type is present. The copy constructor and equals operators require serious hackery, since these constructors on boost function don't allow you to pass a new allow you to pass a new allocator. There's no template<typename Allocator> functionN(const functionN&, Allocator); This means that the Function constructor has to affect data underlying the const Function instance it's copying such that when the allocator is copied over it mutates into one that points at the private buffer of the new constructing instance. This is doable, but kind of scary since I'm making assumptions about when and how the Allocator is copied. This is also not such a wonderful solution, because the SBO is wasted. Any chance of just parameterizing the SBO size? Chris

2 1

boost::date visualizer in vs debugger
by Hicham Mouline 04 Dec '09

04 Dec '09

Hello Has anyone been able to write a msvc8/9 debugger visualizer for boost::gregorian::date? Given that class stores its date in an internal int, I wonder if it's doable to display the date in some human readable format at all? Rds,

1 0

[serialization] speed & size optimized binary archive
by Sebastian Karlsson 04 Dec '09

04 Dec '09

I'm trying to create a binary archive which manages serialization of derived type through base and archive versioning ( not on a type by type basis ). Looking at the binary archive which ships with the distribution it serializes a whole lot of things which is unnecessary for our use case. Going by the documentation and looking on how other archives are implemented I've created a basic implementation, which while compiling doesn't handle serialization of exported types. Even though the documentation is mostly great, this is a small area which seems to be left out, namely the requirements of an archive to be able to serialize / deserialize exported types properly. Looking at the provided archive types it's not clearly distinguishable exactly what's needed for this functionality. The documentation mentions BOOST_SERIALIZATION_REGISTER_ARCHIVE, which is used for the archive. Also, it would be great to know more in depth what actually gets serialized, even if it's subject of change for newer versions. For example, I'm interested in knowing how serialization of exported types will impact archive size. I'm thinking just an extra id per instance? Reading the documentation I got a hunch that extra meta data on a per type basis gets serialized to the archive as well. Under "Types used by the serialization library" several types are mentioned, which of these can be ignored for our use case? This is a reduced form of the output archive which together with an analogous input archive doesn't manage to serialize derived types through their base even if exported, checked to work with the supplied binary archive type. class BinaryOArchive : public boost::archive::detail::common_oarchive< BinaryOArchive > { typedef std::ostream Sink; friend class boost::archive::save_access; template< typename Type > void save( Type& a_Type ) { m_Out.write( reinterpret_cast< const char* >( &a_Type ), sizeof( Type ) ); } public: BinaryOArchive( Sink& a_Out ) : m_Out( a_Out ) {} void save_binary( void *a_Address, std::size_t a_Count ) { m_Out.write( static_cast< const char* >( a_Address ), a_Count ); } private: Sink& m_Out; }; #include "boost/archive/impl/archive_serializer_map.ipp" BOOST_SERIALIZATION_REGISTER_ARCHIVE(Altus::BinaryOArchive) BOOST_SERIALIZATION_USE_ARRAY_OPTIMIZATION(Altus::BinaryOArchive)

3 5

[boost::any] struct tm with boost::any
by Pascal Kesseli 04 Dec '09

04 Dec '09

Hi everyone These two lines of code: any a = tm(); tm t = any_cast<tm>(a); result in a bad_any_cast exception: boost::bad_any_cast: failed conversion using boost::any_cast Is that a bug or what am I missing here? I am using MinGW version 4.4.0 and boost 1.40.0. Thanks for a quick reply and best regards Pascal

1 0

1_41_0 exposes macro collision with thread
by Stonewall Ballard 04 Dec '09

04 Dec '09

Just a heads-up that since 1_41_0 removes libs/thread/src/pthread/exceptions.cpp file from the thread library (its now header-only), it's exposed to any precompiled headers with XCode. If you're using Carbon or (I think) CoreFoundation, that defines a macro named "check", which causes compilation errors in exception/diagnostic_information.cpp. I've had to add #undef check in files that include boost to eliminate this problem. - Stoney -- Stonewall Ballard stoney(a)sb.org http://stoney.sb.org/

2 3

BGL: How to construct voronoy diagram?
by Arman Khalatyan 04 Dec '09

04 Dec '09

Hi, I need to have a voronoy digram over the point data. I would like to visit the facets around the given point and find the occupied volume. Let suppose I have a set of 3D points: typedef typeP struct{float x[3];}; std::vector<typeP> Pdata; How can I generate Voronoy diagram on top of this set? Is BGL situable with this job? thanks Arman.

3 6

[DateTime] Using the system's tzdata?
by Roland Bock 04 Dec '09

04 Dec '09

Hi, DateTime has the Time Zone Database and a respective .csv with time zone information which is probably outdated here and there, judging by the frequent updates of tzdata on Linux systems. I therefore wonder: is there an easy way to use the system's tzdata information in combination with boost::date_time? Regards, Roland

1 0

Compilation errors 1.39, 1.41
by Pfligersdorffer, Christian 04 Dec '09

04 Dec '09

Hello all, I do not always find time to update our project to use the latest and greatest boost version but occasionally I do. At the moment I try to move to at least version 1.39 for my target (power-pc, 32-bit, embedded linux, gcc-4.0.0 cross compiler) and see the following error when compiling the math libs: ./boost/math/special_functions/expm1.hpp:270: error: '::expm1l' has not been declared With version 1.41 it's even more severe since bjam exits with an error before any compilation can take place: error: Duplicate name of actual target: <pstage/lib>libboost_date_time.so.1.41.0 error: previous virtual target { common%common.copy-libboost_date_time.so.1.41.0.SHARED_LIB { gcc%gcc.link.dll-libboost_date_time.so.1.41.0.SHARED_LIB { gcc%gcc.compile.c++-gregorian/greg_month.o.OBJ { gregorian/greg_month.cpp.CPP } } { gcc%gcc.compile.c++-gregorian/greg_weekday.o.OBJ { gregorian/greg_weekday.cpp.CPP } } { gcc%gcc.compile.c++-gregorian/date_generators.o.OBJ { gregorian/date_generators.cpp.CPP } } } } error: created from ./stage-proper error: another virtual target { common%common.copy-libboost_date_time.so.1.41.0.SHARED_LIB { gcc%gcc.link.dll-libboost_date_time.so.1.41.0.SHARED_LIB { gcc%gcc.compile.c++-gregorian/greg_month.o.OBJ { gregorian/greg_month.cpp.CPP } } { gcc%gcc.compile.c++-gregorian/greg_weekday.o.OBJ { gregorian/greg_weekday.cpp.CPP } } { gcc%gcc.compile.c++-gregorian/date_generators.o.OBJ { gregorian/date_generators.cpp.CPP } } } } error: created from ./stage-proper error: added properties: <debug-symbols>off <define>NDEBUG <inlining>full <optimization>speed <runtime-debugging>off <variant>release error: removed properties: <debug-symbols>on <inlining>off <optimization>off <runtime-debugging>on <variant>debug /home/cpf/boost_1_41_0/tools/build/v2/build/virtual-target.jam:490: in actualize-no-scanner from module object(file-target)@4875 /home/cpf/boost_1_41_0/tools/build/v2/build/virtual-target.jam:135: in object(file-target)(a)4875.actualize from module object(file-target)@4875 /home/cpf/boost_1_41_0/tools/build/v2/build-system.jam:717: in load from module build-system /home/cpf/boost_1_41_0/tools/build/v2/kernel/modules.jam:283: in import from module modules /home/cpf/boost_1_41_0/tools/build/v2/kernel/bootstrap.jam:142: in boost-build from module /home/cpf/boost_1_41_0/boost-build.jam:17: in module scope from module I hope someone can look into this. Regards, -- Christian Pfligersdorffer Software Engineering http://www.eos.info

1 0