- Boost-users - lists.preview.boost.org

[Build] First Boost build experience
by Robert Jones 23 Dec '10

23 Dec '10

I have been using Boost at work for quite a while, so I'm no stranger to Boost, or this list, and need no convincing about Boost's general high quality and utility. However, I've recently installed Boost on my home PC, and found the experience surprisingly difficult, and to be honest found that the "Getting Started" instructions are a wee bit poor. I'm installing on Fedora 13, 32 bit, on fairly old hardware, with Gnu C++ 4.5.1, which I've also just built from source for the first time, so maybe there's something I've missed from that process which is having some impact on my Boost experience. Here's a few observations... * First time round I figured that the right place to unpack the zip archive was to the place I ultimately wanted the include files to be (say /usr/local/include), because it's only when you get to the build binaries stuff that the whole copy/build thing is mentioned. Ok, so I should have read all the instructions first, but maybe this could be made clearer earlier. * Having come finally to step 5, the whole 'path/to/installation' thing appears, so I backtracked and put my zip expansion somewhere else. I'm keen to set this up so that I can support several boost versions, so am using the --prefix argument to bootstrap. I think I also need to supply this argument to bjam, at least it seemed to work that way. * That seemd to work ok, although there were some failures for things like MPI and zip, which are, I now realise, ok, but disconcerting. Maybe the instructions could say a few words about the log output expected. I know this is mentioned in the Custom Build stuff, but I'm following the easy idiot's guide. (Appropriate you may think, and you may very well be right!) * Then I came to link the example regex program... what is all that stuff about library naming? I didn't seem to have libraries with names like that at all, my regex libraries were libboost_regex.{a,so,so.1.45.0}, so I used that, and I still don't know what all the stage stuff is about - it seemed to work without it, but maybe there's something that's going to bite me. * Finally my link was failing with "`GLIBCXX_3.4.14' not found", which Googling seemed to suggest was because I need Fedora 14 libstdc++. So I installed that, and now it seems to work.. so far! Ok, so I got there, as I'm sure most people do, but it's not exactly a shrink-wrapped install experience, and a good deal harder than installing on Windoze. I wonder how many people are put off by this. Hmmm... reading that back it sounds like a lot of minor whinging, which is a shame 'cos I think Boost is 'triffic. Thx - Rob.

2 1

Quickbook: source-mode teletype highlighting as c++
by Wilhelm 22 Dec '10

22 Dec '10

Hi, experimenting with source-mode teletype seems to have no effect: all imports are highlighted as c++. -- Wilhelm

3 2

Quickbook: source-mode for java
by Wilhelm 22 Dec '10

22 Dec '10

Hi, are there efforts to add a java source-mode to quickbook? -- Wilhelm

2 1

[gil] New format guidelines about custom Device
by Mateusz Loskot 22 Dec '10

22 Dec '10

Hi, I'm implementing new image format support for Boost.GIL based on the new IO implementation which has been reviewed [1] lately. [1] http://lists.boost.org/boost-announce/2010/11/0273.php What would be the guidelines regarding custom Device implementation? Currently, only TIFF format implements it. When it is required to implement custom Device for the IO? When recommended as a good practice? I think it would be good to have such details documented. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org

2 3

[interprocess] Unmap resource of the object constructed from managed_mapped_file
by Ryan47＠cgcg.com.tw 22 Dec '10

22 Dec '10

Hi, I have a managed_mapped_file and use it to dynamically construct lots of interprocess::vector<size_t> objects(all the objects and elements are resided in the mapped file). Now I'm looking for a way to keep the run-time memory consumption below a certain amount. Is it possible to unmap the resource of the vector object? Although all the resources would be freed when the managed_mapped_file is destroyed, but the cost of highly frequently mapping/un-mapping seems too expensive for my purpose. Is there any way to workaround this? Any suggestion is welcome. Thanks in advance. Regards, Ryan

2 1

Re: [Boost-users] pthread_exit() from boost::thread segfaults
by Bogdan Cristea 22 Dec '10

22 Dec '10

There is no reason for your snippet to fail. I have tested on openSUSE 11.3, 64 bits with gcc 4.5.0 and libboost_thread 1.42. Try to remove from the thread starter function the call to pthread_exit() and see if you still get the error.

3 4

[serialization] serialize std::unique_ptr
by Dmitry Vinogradov 21 Dec '10

21 Dec '10

Does there exists a common way to serialize std::unique_ptr?

1 0

Boost.Log build problem
by Anand Arumugam 21 Dec '10

21 Dec '10

Hello All, I installed Boost v1.42 that was available from Synaptic Package Manager in Xubuntu 10.10. Downloaded the Boost.Log library from sourceforge and extracted it under /usr/include/boost. From the command line I issued the following to build it: bjam --with-log variant=release stage And got this as output: notice: could not find main target stage notice: assuming it's a name of file to create /usr/share/boost-build/build/project.jam:699: in attribute warning: rulename $($(project).attributes).get expands to empty string /usr/share/boost-build/build/project.jam:709: in project.target /usr/share/boost-build/build-system.jam:395: in load /usr/share/boost-build/kernel/modules.jam:261: in import /usr/share/boost-build/kernel/bootstrap.jam:132: in boost-build /usr/share/boost-build/boost-build.jam:1: in module scope /usr/share/boost-build/build/project.jam:699: in project.attribute warning: rulename $($(project).attributes).get expands to empty string /usr/share/boost-build/build/targets.jam:203: in object(project-target)(a)36.__init__ /usr/share/boost-build/kernel/class.jam:93: in new /usr/share/boost-build/build/project.jam:709: in project.target /usr/share/boost-build/build-system.jam:395: in load /usr/share/boost-build/kernel/modules.jam:261: in import /usr/share/boost-build/kernel/bootstrap.jam:132: in boost-build /usr/share/boost-build/boost-build.jam:1: in module scope /usr/share/boost-build/build/project.jam:699: in project.attribute warning: rulename $($(project).attributes).get expands to empty string /usr/share/boost-build/build/targets.jam:222: in get /usr/share/boost-build/build/targets.jam:284: in targets-to-build /usr/share/boost-build/build/targets.jam:253: in object(project-target)(a)36.generate /usr/share/boost-build/build-system.jam:414: in load /usr/share/boost-build/kernel/modules.jam:261: in import /usr/share/boost-build/kernel/bootstrap.jam:132: in boost-build /usr/share/boost-build/boost-build.jam:1: in module scope /usr/share/boost-build/build/project.jam:699: in project.attribute warning: rulename $($(project).attributes).get expands to empty string /usr/share/boost-build/build/targets.jam:222: in get /usr/share/boost-build/build/targets.jam:285: in targets-to-build /usr/share/boost-build/build/targets.jam:253: in object(project-target)(a)36.generate /usr/share/boost-build/build-system.jam:414: in load /usr/share/boost-build/kernel/modules.jam:261: in import /usr/share/boost-build/kernel/bootstrap.jam:132: in boost-build /usr/share/boost-build/boost-build.jam:1: in module scope don't know how to make <e>stage ...found 1 target... ...can't find 1 target... I found a similar help request at: http://lists.boost.org/boost-build/2007/06/16748.php but I want to know whether what I am doing is correct - that is trying to build one library from source (that is not officially part of boost), while installing all other boost libraries from a package manager? In /usr/lib all the other boost static and shared libraries are installed. Thank you for your time. cheers, Anand.

2 1

Re: [Boost-users] Boost-users Digest, Vol 2579, Issue 2
by Bogdan Cristea 21 Dec '10

21 Dec '10

On Tuesday 21 December 2010 11:55:23 boost-users-request(a)lists.boost.org wrote: > Hmm, looking into thread.cpp implementation of thread_proxy (callback > function for pthread_create()) and boost::thread::join I do not see how > this join implementation would work with any abnormal thread termination. > In thread.cpp boost::thread::join waits the thread termination on line: > local_thread_info->done_condition.wait(lock); > > The lock gets signaled only at end of thread_proxy(), which is reached > only if the user thread routine does "return" or is interrupted with > boost::thread means. pthread_exit(), as well as any other emergency > termination does only stack unwinding (on most but not all systems), so > done_condition is simply never signaled in these circumstances. To be > correct the thread_proxy() should have installed cleanup routine with > pthread_cleanup_push() and, to be sure, have an local object which > destructor would signal done_condition as well, but I do not see it in > boost::thread code. > > Bogdan, when you said, the test program works for you - did you means it > does return with status 0? If so, I wonder, which way the execution goes > in your thread_proxy implementation - can you please debug it a little if > you have some time? To build debug version of boost you need to add > "variant=debug" option to bjam. I tried the same test program on ubuntu > 10.04 TLS with gcc 4.4.3 and boost 1.40 - the same result as with latest > boost: it freezes in boost::thread::join() on condition.wait(). Hi pthread_exit() is used to pass data to the parent thread at exit. pthread_join() should receive this data to its second parameter. I will try to have a closer look, but I doubt that boost doesn't handle correctly such situation. regards Bogdan

1 0

quickbook syntaxhighlighting in katepart
by Wilhelm 21 Dec '10

21 Dec '10

Hi, I tried to get the syntaxhighlighting for kate working, but with no success. I copied the *.xml files with the highlighting definitions to the katepart/syntax directory (both for kate-3 and kate-4), but nothing changed opening *.qbk files. Any hints? -- Wilhelm

1 0