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

[Boost.Test] Test Ordering?
by John M. Dlugosz 06 Nov '12

06 Nov '12

If I make unit*test*s in different source files, I need to declare a BOOST_AUTO_*TEST*_SUITEin 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?

3 3

On Windows, how does Boost decide which MSVS version to use, if I have more than one installed?
by Ramon F Herrera 05 Nov '12

05 Nov '12

When I tried to build some app, I ended up with this error message: 1>LINK : fatal error LNK1104: cannot open file 'libboost_filesystem-vc80-mt-1_51.lib' I am sure it is due to the fact that I have a couple of Boost installations and 2 Versions of MSVS as well (2005 and 2010). NB: This is the way I build Boost on Windows: .\bootstrap.bat .\bjam.exe --with-date_time --with-filesystem --with-regex --with-system --stagedir=. --build-type=complete toolset=msvc The question is about that last parameter above. Does the install procedure: (a) Go to "Program Files" and takes a look at the name of the highest numbered MSVS folder? or (b) Is this info extracted from the Registry or something? TIA, -Ramon

2 1

Boost 1.52.0 released!
by Marshall Clow 05 Nov '12

05 Nov '12

Release 1.52.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains numerous enhancements and bug fixes for existing libraries. For details, including download links, see http://www.boost.org/users/news/version_1_52_0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.52.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Beman Dawes Daniel James Eric Niebler Marshall Clow Rene Rivera Vladimir Prus

3 2

Linking problems with boost serialization and MinGW
by Florian Burkart 05 Nov '12

05 Nov '12

Hi, I am having a bit of trouble linking to boost serialization with MinGW. If I don't include -lboost_serialization-mgw46-mt-d-1_50 I get loads of undefined references, however, if I do include it, most disappear but I still get some, namely I get RDebug/libFlamLib.a(Common_Collector.o): In function `ZN5boost7archive21basic_text_oprimitiveISoE4saveINS0_14object_id_typeEEEvRKT_': /Sys/boost/MinGW32/boost_1_50_0/include/boost-1_50/boost/archive/basic_text_oprimitive.hpp:89: undefined reference to `boost::archive::archive_exception::archive_exception(boost::archive::archive_exception::exception_code, char const*, char const*)' RDebug/libFlamLib.a(Common_Collector.o): In function `ZN5boost7archive21basic_text_oprimitiveISoE4saveINS0_21object_reference_typeEEEvRKT_': /Sys/boost/MinGW32/boost_1_50_0/include/boost-1_50/boost/archive/basic_text_oprimitive.hpp:89: undefined reference to `boost::archive::archive_exception::archive_exception(boost::archive::archive_exception::exception_code, char const*, char const*)' RDebug/libFlamLib.a(Common_Collector.o): In function `ZN5boost7archive21basic_text_oprimitiveISoE4saveINS0_13class_id_typeEEEvRKT_': /Sys/boost/MinGW32/boost_1_50_0/include/boost-1_50/boost/archive/basic_text_oprimitive.hpp:89: undefined reference to `boost::archive::archive_exception::archive_exception(boost::archive::archive_exception::exception_code, char const*, char const*)' RDebug/libFlamLib.a(Common_Collector.o): In function `ZN5boost7archive21basic_text_oprimitiveISoE4saveINS0_23class_id_reference_typeEEEvRKT_': /Sys/boost/MinGW32/boost_1_50_0/include/boost-1_50/boost/archive/basic_text_oprimitive.hpp:89: undefined reference to `boost::archive::archive_exception::archive_exception(boost::archive::archive_exception::exception_code, char const*, char const*)' RDebug/libFlamLib.a(Common_Collector.o): In function `ZN5boost7archive21basic_text_oprimitiveISoE4saveINS0_13tracking_typeEEEvRKT_': /Sys/boost/MinGW32/boost_1_50_0/include/boost-1_50/boost/archive/basic_text_oprimitive.hpp:89: undefined reference to `boost::archive::archive_exception::archive_exception(boost::archive::archive_exception::exception_code, char const*, char const*)' RDebug/libFlamLib.a(Common_Collector.o):/Sys/boost/MinGW32/boost_1_50_0/include/boost-1_50/boost/archive/basic_text_oprimitive.hpp:89: more undefined references to `boost::archive::archive_exception::archive_exception(boost::archive::archive_exception::exception_code, char const*, char const*)' follow Basically they all refer to "`boost::archive::archive_exception::archive_exception". boost serialization built fine with .\b2.exe --prefix=c:\Sys\boost\MinGW32\boost_1_50_0 toolset=gcc address-model=32 --with-serialization install The same code compiles and links just fine with gcc on linux and MSVC on windows. I haven't isolate the issue yet, so am afraid can't give a reproducible sample, but any ideas so far? Maybe look familiar? Thanks, Florian

2 3

Symantec Norton shold not longer flag boost_signals-vc100-mt-gd-1_50.dll as suspicious
by Paul A. Bristow 05 Nov '12

05 Nov '12

I was slightly inconvenienced by having the new version of boost_signals-vc100-mt-gd-1_50.dll that I had just built flagged by Norton as suspicious and placed in 'quarantine'. "Name of detection given by Symantec product: suspicious.cloud.7.f" But I was impressed that reporting this to Symantec I got (in 48 hours) this response: "Dispute Submission [2985065] Symantec FP Incident Response falsepositives(a)symantec.com" saying that it was now whitelisted in the daily virus definitions update. Paul PS I have had bjam/b2 also flagged in the past saying it only had five users! --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

1 0

[range] questions about documentation and usage
by Robert Ramey 05 Nov '12

05 Nov '12

I want to use Boost.Range in a bigger way. But I have a few problems with it. I think most of them are just issues of understanding and the writting of the documentation a) I see examples like std::vector<T> v; boost::range::find(v, 0); find(SinglePassRange& rng, Value val); BUT when looking at the documentation at http://www.boost.org/doc/libs/1_51_0/libs/range/doc/html/range/concepts/sin… I see only two valid expressions boost::begin(a) boost::end(a) where in this case a would be v which is of type std::vector<int>. BUT boost:begin(v) is NOT a valid expression for the above. Spelunking into the range header code reveals the following: template< class T > inline BOOST_DEDUCED_TYPENAME range_iterator<T>::type begin( T& r ) { #if !BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x564)) && \ !BOOST_WORKAROUND(__GNUC__, < 3) \ /**/ using namespace range_detail; #endif return range_begin( r ); } and template< typename C > inline BOOST_DEDUCED_TYPENAME range_iterator<C>::type range_begin( C& c ) { // // If you get a compile-error here, it is most likely because // you have not implemented range_begin() properly in // the namespace of C // return c.begin(); } This effectively means that the "Valid Expressions" for SinglePassRange part of the documenation should read: a.begin() a.end() Doesn't it. I would be interested to know if I got this wrong. b) I see the template iterator_range<ForwardTraversalIterator> - which seem to be to in an instance of what the ForwardRangeConcept should be. To me, the range documentation is out of whack. I can figure it out - but it's misleading - atleast to me. c) Another really annoying thing is that every thing is directly in the boost namespace. This breaks the convention that library headers are in boost/<library name> and in the namespace boost::<library name>. This creates a lot of opportunity for conflict. Robert Ramey

8 38

Debug Assertion with MFC
by Yiğit Çağrı Akkaya 05 Nov '12

05 Nov '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

[Program_options] Positional options are not parsed, "unrecognised option". A bug?
by Dmitry Shintyakov 04 Nov '12

04 Nov '12

Hello, everybody. I am having problems using Boost::Program_options library. I have a program, that have several optional keyword arguments, and 3 positional arguments. Keyword arguments are parsed well, but positional arguments are always causing an exception? saying: "unrecognised option" After spending 2 hours trying to find a problem, I decided to ask for help. I am using Boost 1.50.0-2, GCC 4.7.2 under Arch linux (32 bit). My example is almost exact copy from the tutorial, so I suspect that there is some bug. Example code (with all non-relevant code removed) follows. To test it, run it as following: ./a.out 123 123 test Expected behaviour is to see a line: Arguments: output=output.png width=123 height=123 Instead, I see this: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail:: error_info_injector<boost::program_options::unknown_option> >' what(): unrecognised option '1' ==Test code== #include <iostream> #include <boost/program_options.hpp> using namespace std; int main( int argc, char * argv[] ) { namespace po = boost::program_options; string output_file; po::options_description desc("converter [options] width height source"); desc.add_options() ("help", "Show help message") ("output,o", po::value<string>( &output_file )->default_value("output.png"), "Output file to put converted image data to. Default is output.png") ; po::positional_options_description pos_desc; pos_desc.add("width",1).add("height",1).add("input-file",1); po::variables_map vm; po::store( po::command_line_parser(argc, argv) .options(desc) .positional(pos_desc) .run() , vm ); po::notify( vm ); if( vm.count("help") ){ cout << desc <<endl; return 0; } if (!vm.count("width") || !vm.count("height") || !vm.count("input-file") ){ cerr<<"Error: width, weight and input file must be specified"<<endl; return 1; } cout << "Arguments: output="<<output_file << " width="<<vm["width"].as<string>() << " height="<<vm["height"].as<string>()<<endl; return 0; }

1 0

MingW compilation errors
by Alice Gamewell 04 Nov '12

04 Nov '12

I have managed to build the boost libraries with b2 and the gcc toolset option. Alas, whenever I use a header which invokes such a library in Code::Blocks chained with MingW I get these errors: undefined reference to _Unwind_SiLj_Register undefined reference to _Unwind_SiLj_Unregister undefined reference to _Unwind_SiLj_Resume undefined reference to __gxx_personality_sj0 undefined reference to _WSACleanup@0 undefined reference to _WSAStartup@8 All but the last two repeatedly. I would really appreciate anyone who could point me out of this mess. Thanks!

3 2

[Date Time] MSVC CRT assertion stops execution in debug mode
by Fumito Hamamura 03 Nov '12

03 Nov '12

Hi, I'm testing the code below using boost 1.50.0 and Visual C++ 2008. What I expected was, the ptime t doesn't throw an exception even though it doesn't get a valid date time string passed by the wstringstream ss. When it is compiled in Release mode, it works as expected, i.e. the program runs without an error, but when compiled in Debug mode, the program stops because debug assertion fails in _chvalidator in isctype.c, which is called by std::isspace. Is there a known workaround for this? Thanks, Fumito ----- #include <iostream> #include <string> #include "boost/date_time/posix_time/posix_time.hpp" int wmain(int argc, wchar_t* argv[]) { boost::posix_time::wtime_input_facet* dt_facet(new boost::posix_time::wtime_input_facet(L"%Y/%m/%d %H:%M")); std::wstringstream ss; boost::posix_time::ptime t; ss.imbue(std::locale(ss.getloc(), dt_facet)); ss << L"あいうえお"; ss >> t; return 0; } -----

2 1