September 2005 - Boost-users

Managing builds
by Aaron Griffin 02 Oct '05

02 Oct '05

I have a question, and it's something that has been bothering me for some time when dealing with boost. There are certain boost libs which require link libraries (static/dynamic). That's normal. However, if I wanted to statically link against, say, multithreaded Boost.Filesystem (gcc), I would need to add -Bstatic -lboost_filesystem-gcc-mt (or something to that effect). A majority of projects provide some sort of pkg-config files, or even their own app (gtk-config ?). Is there any functionality like this out there? Is there any way I can make this re-buildable on multiple target machines with multiple install locations in an easy manner? Ideally, something like: boost-config --static-libs filesystem would fit the standard scheme and allow for different machine to have different boost installation roots, and things of that nature. Without something like that, I am forced to either add configure flags, or force a user to modify a "config.mk" style file.

3 4

scoped_ptr help.
by John Sun 01 Oct '05

01 Oct '05

New to this topic,and need some help here. I have a class which use the scoped_ptr as a member variable. Class CTest { public: CTest(); Initialize(); ~CTest(); private: scoped_ptr<CTest2> m_spTest2; } For some reason, that I cannot initialize m_spTest2 in the member initialization list of the constructor, so I have to initialize in some other functions like in Initialize. CTest::Initialize() { int aa, bb; m_spTest2=new CTest2(aa, bb); } The compiler will complain about that, so what's the right way to do it. Thanks, Jianwei

6 8

Library's binary size
by Ugo Mendes Donelli 30 Sep '05

30 Sep '05

In the "Getting Started" section of boost web site, there should be a requirements section. When actually built and installed on Windows, the library 1.33 required more than 2GB of disk space. I was targeting VC++ 7.1. The 1.32 library used more or less 1GB of disk. The disk space requirements that I mention include the bin subdirectory created by the build process in the library's source tree, directory that I generally delete by hand shortly after. I don't think that any user will run out of disk space but it's better if the users know about this before they build the library. Ciao, Ugo

2 1

composing stream iterators?
by Robert Mathews 30 Sep '05

30 Sep '05

I have a collection of streams that I want to read from sequentially, and I want it to look like a single stream iterator to the calling code. Is there a boost template for a stream iterator that wraps a collection of other stream iterators? Thanks, Rob.

1 0

[serialization] Bug in demo.cpp?
by Paul Giaccone 30 Sep '05

30 Sep '05

Does the demo program demo.cpp <http://boost.org/libs/serialization/example/demo.cpp> have a bug in it? When I run it, it crashes at the line that does the actual serialisation: oa << s; in save_schedule(), reporting the error: Unhandled exception at 0x7c59bbf3 in SerializationDemo.exe: Microsoft C++ exception: __non_rtti_object @ 0x0012ee98 at line 260 of dbgheap.c: pvBlk = _heap_alloc_dbg(nSize, nBlockUse, szFileName, nLine); The call stack is > SerializationDemo.exe!_nh_malloc_dbg(unsigned int nSize=33, int nhFlag=1240696, int nBlockUse=5007849, const char * szFileName=0xe06d7363, int nLine=1) Line 260 + 0x15 C SerializationDemo.exe!malloc(unsigned int nSize=0) Line 139 + 0x15 C I'm compiling in Windows 2000 using Visual .NET, if this helps. Paul Giaccone PS: I modified the filename so it is correct for Windows (using backslashes) - it might be a good idea to use a boost::path here to make the code portable.

2 3

[TR1 Review] TR1 Formal Review Beginning
by Beman Dawes 30 Sep '05

30 Sep '05

The formal review of the Boost TR1 Library by John Maddock begins today, Saturday, September 24th, and runs through Wednesday, October 5th. The TR1 library provides an implementation of the C++ Technical Report on Standard Library Extensions. This library does not itself implement the TR1 components, rather it's a thin wrapper that will include your standard library's TR1 implementation (if it has one), otherwise it will include the Boost Library equivalents, and import them into namespace std::tr1. Functionality supported includes: * Reference Wrappers * Smart Pointers * Class template result_of. * Function template mem_fn. * Function Object Binders. * Polymorphic function wrappers. * Type Traits. * Random Number Generators and Distributions. * Tuples. * Tuple Interface to std::pair. * Fixed Size Array. * Hash Function Objects. * Regular Expressions. * Complex Number Algorithm Overloads. * Complex Number Additional Algorithms. Functionality in TR1 but not yet available: * Mathematical Special Functions. * Unordered Associative Set (Hash Table). * Unordered Associative Map (Hash Table). * C99 C language additions. Additional information including online documentation is available at http://freespace.virgin.net/boost.regex/tr1/index.html The complete TR1 lib source and docs can be downloaded from http://freespace.virgin.net/boost.regex/tr1/tr1-20050816.zip Please help Boost by posting your formal review of this library. Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. --Beman Dawes, Review Manager

6 18

[spirit] parser trees
by Aaron Griffin 30 Sep '05

30 Sep '05

Just a couple of "noob" spirit questions for you all which are more experiences in the zen ways of Spirit. If I chose to use a parser tree (or ast) instead of cluttering my code with semantic actions, is there any trade off in parse speed, besides the obvious tree generation itself? Now, let's say I generate a parse tree, and output the results to some sort of XML or structured format. Would spirit allow me to regenerate the tree from that format? i.e. Are there any issues/complications with generating the tree manually? What is more common, an AST or a parser tree? I understand the technical differences, but not the reasons behind them (yet). Thanks in advance.

1 0

[Fwd: [pointer container] Error populating pointer container with stack based objects]
by Allen Cronce 30 Sep '05

30 Sep '05

2 2

Newbie help please - trying to build for QNX6
by Jim Douglas 30 Sep '05

30 Sep '05

Hi, (New to Boost & bjam - not QNX) I am trying to build the Boost libs for QNX 6.3.0 on both the Windows hosted and QNX hosted development platforms using the gcc tools. What happens if I build out of the box is - Under Windows most of the libraries build, but they have Windows suffixes ".lib" and ".dll" which suggest that the build options are targeting Windows. Under QNX most of the build fails. The principal error seems to be a message "g++: unrecognised option -pthread". I have tried running './configure' but that does not make any difference. If I have interpreted the docs correctly perhaps the version 2 build system would be more appropriate for cross platform builds? Can I specify or detect the host, target and toolset independently? Any help and advice greatly appreciated... Jim Douglas

2 7

Re: [Boost-users] MSVC v6 build fails in file boost\detail\shared _count.hpp
by David Balazic 30 Sep '05

30 Sep '05

Correction. MSVC6 builds OK without this change. My project is compiled for win (msvc6) and winCE (evc4), so the changes are, it seems, needed for the evc4 compiler. I use STLport there anyway, so this issues might be a ... non-issue :-) Regards, David > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Aaron Griffin > Sent: Thursday, September 29, 2005 10:29 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] MSVC v6 build fails in file > boost\detail\shared_count.hpp > > > On 9/29/05, David Balazic <david.balazic(a)hermes.si> wrote: > > from : > > void * get_deleter(std::type_info const & ti) const > > > > to > > void * get_deleter(type_info const & ti) const > > > > I have Visual Studio c++ 6.0. > > > > Is this a known problem ? > > Will it be pathced ? > > Well, it's been a while since I've used VS6, but if it does not > support the std:: namespace, it does not support C++. It may be the > compiler, in which case you should get a new one (mingw works well on > Windows). It might just be your STL headers, in which case, I'd > suggest replacing it with STLPort or something .... better. > > Aaron Griffin > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0