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

[geometry] Best Fit Plane
by Manoj Lnu 07 Oct '17

07 Oct '17

Is there a function available in boost geometry to find the best fit plane ? I have a set of 3D points as input. Thanks, Manoj

2 1

Memory usage of boost::unordered_multimap and boost::unordered_multimap
by Ram 06 Oct '17

06 Oct '17

Hi, I need help in determining the amount of memory used by boost::unordered_multimap and boost::unordered_multimap. We have a large code base and we have some optimizations done using boost::unordered_multimap and boost::unordered_multimap. The speed it really good, but we want to measure the amount of space it is occupying. Can somebody please help with that? I would not be able to change to use a custom new/delete. Thanks

3 5

Why no mpl::_double?
by Florian Lindner 06 Oct '17

06 Oct '17

Hello, is there a reason why there are only integral types in the boost MPL, no double or alike? http://www.boost.org/doc/libs/1_65_1/libs/mpl/doc/refmanual/numeric.html What is the best way to achieve: template<> struct getArg<Multiquadrics> : boost::mpl::double_<1e-3> {}; so that it is compatible with mpl::list? besides just writing the struct myself :-) Thanks, Florian

1 0

[stacktrace] Test failures with Xcode 9
by Nat Goodspeed 06 Oct '17

06 Oct '17

I've just started building Boost 1.65.1 Stacktrace. On Mac with Xcode 9, I'm dismayed that it has failed a couple of its own self-tests. Lengthy (albeit snipped) output follows. darwin.compile.c++ bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o "g++" -O3 -Wall -pedantic -g -dynamic -gdwarf-2 -fexceptions -Wno-long-long -Wno-inline -fPIC -arch x86_64 -DBOOST_STACKTRACE_GNU_SOURCE_NOT_REQUIRED -O3 -fPIC -gdwarf-2 -stdlib=libc++ -mmacosx-version-min=10.9 -iwithsysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/ -DLL_RELEASE=1 -DLL_RELEASE_FOR_DOWNLOAD=1 -DNDEBUG -DPIC -DLL_DARWIN=1 -DLL_OS_DRAGDROP_ENABLED=1 -DCARES_STATICLIB -DLIB_NDOF=1 -Wno-c99-extensions -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef -Wno-variadic-macros -std=c++14 -DBOOST_ALL_NO_LIB=1 -DBOOST_STACKTRACE_USE_ADDR2LINE -DNDEBUG -I"." -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include" -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include/zlib" -c -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o" "libs/stacktrace/test/test.cpp" darwin.compile.c++ bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o "g++" -O3 -Wall -pedantic -g -dynamic -gdwarf-2 -fexceptions -Wno-long-long -Wno-inline -fPIC -arch x86_64 -DBOOST_STACKTRACE_GNU_SOURCE_NOT_REQUIRED -O3 -fPIC -gdwarf-2 -stdlib=libc++ -mmacosx-version-min=10.9 -iwithsysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/ -DLL_RELEASE=1 -DLL_RELEASE_FOR_DOWNLOAD=1 -DNDEBUG -DPIC -DLL_DARWIN=1 -DLL_OS_DRAGDROP_ENABLED=1 -DCARES_STATICLIB -DLIB_NDOF=1 -Wno-c99-extensions -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef -Wno-variadic-macros -std=c++14 -DBOOST_ALL_NO_LIB=1 -DBOOST_STACKTRACE_USE_ADDR2LINE -DNDEBUG -I"." -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include" -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include/zlib" -c -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o" "libs/stacktrace/test/test_impl.cpp" darwin.link bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho "g++" -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o" -g -Wl,-dead_strip -no_dead_strip_inits_and_terms -arch x86_64 testing.capture-output bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.run status=0 if test $status -ne 0 ; then echo Skipping test execution due to testing.execute=off exit 0 fi "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho" > "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" 2>&1 < /dev/null status=$? echo >> "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" echo EXIT STATUS: $status >> "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" if test $status -eq 0 ; then cp "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.run" fi verbose=0 if test $status -ne 0 ; then verbose=1 fi if test $verbose -eq 1 ; then echo ====== BEGIN OUTPUT ====== cat "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" echo ====== END OUTPUT ====== fi exit $status ====== BEGIN OUTPUT ====== ... 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 14# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 15# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 16# void test_nested<15ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 17# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho libs/stacktrace/test/test.cpp(200): test 'min_size > 2' failed in function 'void test_frame()' ' 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 300# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 301# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 302# void test_nested<300ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 303# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ' 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 300# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 301# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 302# void test_nested<300ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 303# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho libs/stacktrace/test/test.cpp(282): test 'boost::stacktrace::stacktrace(1, 1).size() == 1' failed in function 'int main()' 2 errors detected. EXIT STATUS: 1 ====== END OUTPUT ======

1 3

[Units]
by CD Clark 06 Oct '17

06 Oct '17

I am trying to create a set of units to use in a library, but I having trouble getting IO to work for some of them. Here is a simple example that demonstrates the problem. ============================ #include<iostream> #include <boost/units/systems/si.hpp> #include <boost/units/systems/si/io.hpp> using namespace boost::units; // short hand for meter namespace t { typedef si::length m; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m, t::m ); } // centimeter namespace t { typedef make_scaled_unit< si::length, scale< 10, static_rational<-2> > >::type cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( cm, t::cm ); } // meter squared namespace t { typedef multiply_typeof_helper< m, m>::type m_m; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m_m, t::m_m ); } // centimeter squared namespace t { typedef multiply_typeof_helper< cm, cm>::type cm_cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( cm_cm, t::cm_cm ); } // meter centimeter namespace t { typedef multiply_typeof_helper< m, cm>::type m_cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m_cm, t::m_cm ); } // override default output, which prints "c(m^2)" namespace boost { namespace units { inline std::string name_string(const t::m_cm&) { return "meter centimeter"; } inline std::string symbol_string(const t::m_cm&) { return "m cm"; } } } // trying to overload output for centimeter squared namespace boost { namespace units { inline std::string name_string(const t::cm_cm&) { return "centimeter squared"; } inline std::string symbol_string(const t::cm_cm&) { return "cm^2"; } } } int main(int argc, char *argv[]) { std::cout << i::m << std::endl; std::cout << i::cm << std::endl; std::cout << i::m_m << std::endl; std::cout << i::m_cm << std::endl; //std::cout << i::cm_cm << std::endl; // this won't compile quantity<t::m_m> a1(100*i::cm_cm); std::cout << a1<< std::endl; // should be 0.01 m^2 quantity<t::m_m> a2(100*i::m_cm); std::cout << a2<< std::endl; // should be 1 m^2 return 0; } ============================ Basically, I am just trying to create a convenient set of short hands. Unit types are put in a 't' namespace and instances are put in a 'i' namespace with the same name. This works fine for doing calculations and conversions with the units, but I am having trouble with getting output to work for some of them. In the example above I create a centimeter unit by scaling the meter. Then I create three different area units with the product_typeof_helper struct: meter squared, meter centimeter, and centimeter squared. Conversions work for all three of these, but output will not work for the centimeter squared unit. The program above outputs m cm m^2 m cm 0.01 m^2 1 m^2 If I uncomment the line that tries to print i::cm_cm it won't compile. I get an error that says 'symbol' is not a member of ... and points at a line that says str += Begin::item::symbol() I can't understand why it doesn't work for a product of two scaled units. cdclark

2 4

Re: [Boost-users] boost::process
by Chris Rodgers 05 Oct '17

05 Oct '17

To answer my own question - this is one working possibility using boost::process::extend... #include <boost/process.hpp> #include <boost/process/extend.hpp> int main() { boost::filesystem::path myPath(".........toRun.exe......."); auto set_own_window = [](auto & exec) { exec.creation_flags |= boost::detail::winapi::CREATE_NEW_CONSOLE_; std::cerr << "in set_own_window" << std::endl; /* just for debugging */ }; bp::child c(myPath, "argument1", boost::process::extend::on_setup=set_own_window); return 0; } This works. Is it the right approach, or is there a better way? Best wishes, Chris. On 05/10/2017 17:14, Chris Rodgers wrote: > Hi, > > I'm trying to use Boost 1.65.1's boost::process::child in a Windows > console program. > > At the moment, the child process is launched in the same console window > as the parent. > > Is there an option to make a new console window for the child? > > The pre-boost-incorporation version of boost::process seemed to allow > manipulation of the startupInfo struct directly (e.g. > https://stackoverflow.com/questions/43582022/boostprocess-hide-console-on-w…) > and then a win32_launch call. But this seems to have been removed now? > > Any tips gratefully received. > > Thanks, > > Chris. >

1 0

PolyCollection requiring copyable
by d3fault 05 Oct '17

05 Oct '17

I'm impressed with PolyCollection. I use the list<interface*> strategy tons in my projects, and I didn't think NOT using a pointer there was even possible... but somehow you managed. It also makes sense why PolyCollection is faster to execute etc, the tutorial was well written. The only 'con' is that it requires a copy constructor. You mention later that some copy traits thing can be used to move the "copy code" outside of the class, but I am questioning the need for copying altogether. Is "copying" of the polymorphic types necessary for: a) Technical requirement otherwise it wouldn't compile b) Design decision because you think it's superior and helpful c) To facilitate copying of the PolyCollection object itself ....? If (b) or (c), can there be a slightly altered version of PolyCollection which does not allow/require copying? I'm completely fine (and even happier) _not_ being able to copy the PolyCollection. When I use the list<interface*> strategy, I tend to consider the list to be the owner of it's objects (and delete them when the list is deleted). There should be PolyCollection::emplace and the poly instances should "live" in the PolyCollection. Accessing the poly instances should be by [const] reference only (isn't this already the case? what benefit does the copy constructor bring?!?). I didn't examine the source so maybe it's (a) after all, in which case I apologize for wasting precious time, bandwidth, and disk space. d3fault

5 11

boost::process
by Chris Rodgers 05 Oct '17

05 Oct '17

Hi, I'm trying to use Boost 1.65.1's boost::process::child in a Windows console program. At the moment, the child process is launched in the same console window as the parent. Is there an option to make a new console window for the child? The pre-boost-incorporation version of boost::process seemed to allow manipulation of the startupInfo struct directly (e.g. https://stackoverflow.com/questions/43582022/boostprocess-hide-console-on-w…) and then a win32_launch call. But this seems to have been removed now? Any tips gratefully received. Thanks, Chris.

1 0

looking for a memory leak in an asio based application
by David Medine 05 Oct '17

05 Oct '17

I know that the answer to this question is /always/ 'no'. But is it possible, just possible that one can leak memory out of boost::asio? Let me explain. I work on an open source client/server data streaming library for multi-modal data streaming called labstreaminglayer (https://github.com/sccn/labstreaminglayer) At the core of the data transmission architecture is boost::asio. Now, to avoid calling collisions, the original author of the library shipped the source code with a name-mangled version of boost. Over the years this has yet to be updated so we are still relying on boost 1.57. The memory leak starts on the server side after a client is connected to it. This went undetected for years because it is very very slow and it depends on the sampling rate of the data stream. LSL (labstreaminglayer) is widely used in the neurophysiological research community (for whom the tool was intended), but normally in that field you are not sending samples faster than 500 Hz or so. But some devices are now available that offer relatively high sampling rates (e.g. Brain Products' actiCHamp can go as fast as 100kHz). The amount of memory that leaks seems to depend on how often data is sent, not how much data is send at a time. So, when the data is flowing quickly, the leak is severe. I am 99.99% sure that the allocation of memory for all the data I am sending is getting deallocated correctly. I don't see any leaking memory according to Visual Studio's diagnostic tools, nor can Deleaker spot anything. However, when I look at a server process in task manager, I can see the memory rising. I tried the asio::io_service::work trick (https://stackoverflow.com/questions/32258890/c-boost-asio-async-send-to-mem…) on my io_services, but this didn't have any effect. I have not gone through the whole pipeline yet, but I've been at this for two harrowing days already. So I just thought I would ask the list if anyone has seen anything like this before or if there has been any slow-leak fixes in boost (particularly asio) since 1.57 (I didn't see anything in the logs, but maybe I missed something). Due to the state of the project at this moment, it is non-trivial to update the name-mangled boost to another version, but it is far less trivial than the needle-in-a-haystack game I am playing right now. So, if someone can say with authority a boost update will fix everything I'll just do that and be happy. It's a long-shot, I know.

2 1

Bost Logging
by Mário Costa 04 Oct '17

04 Oct '17

Hi, I'm havving a bad time trying to figure out how to add and log custom keywords using boost/log. I havent been able to understand how exactly attribute keywords (BOOST_LOG_ATTRIBUTE_KEYWORD) bind with logging e.g. using BOOST_LOG_STREAM_WITH_PARAMS(logger, (??) (??)). For instance, if I define a keyword line_number, BOOST_LOG_ATTRIBUTE_KEYWORD(line_number, "LineNumber", unsigned int) and add it to the formmater logging::formatter formatter = expr::stream << "[" << line_number << "]" How do I use BOOST_LOG_STREAM_WITH_PARAMS(logger, (??)) Tanking an exemple from the severities, I should use a keyword parameter defining something like BOOST_PARAMETER_KEYWORD(sometag, line_number) then I should be able to use BOOST_LOG_STREAM_WITH_PARAMS(logger, (line_number = 10)) But those things just don add up together. I for sure missing the logics of the logging ... Thanks for any help! Cheers, mc

1 0

[geometry] Get points within certain radius?
by Florian Lindner 03 Oct '17

03 Oct '17

Hello, first of all thanks for the repliest to my previous geometry question! What is the best, especially fastest way to get all points within a certain radius of a point? Using the iterator method with nearest(pt, X) highly depends on X. Since I don't know this number, I have to guess it rather high. for (auto it = rtree.qbegin(bgi::nearest(point, results)) ; it != rtree.qend() ; ++it) { std::ignore = it; break; } results = 10 => time = 3.0s results = 100 => time = 22.6s results = 200 => time = 71.4s results = 300 => time = 153.2s though I always use just one result. The loop is inside another loop, not depending on results, so of course, the times are multiples of the actual times for that query. But clearly, choosing high numbers for results is not feasible. Another idea is to use the within() query with a circle of a radius. But bg seems to have no circle or sphere model. A workaround would be to use a box instead of a sphere. That means I have to test the results again, whether they are actually contained in th sphere. Alternatively, I could use the satisfies predicate. But wouldn't I give up all spatial information? This predicate needs to compare all vertices, don't it? It does include the knowledge, that when one point is discarded, all other points with a greater distance will discarded too. According to https://stackoverflow.com/questions/22909171/boostgeometry-nearest-neighbor…, the way to go seems to be to combine within(boundingBox) and satisfies(). Any other ideas? Thanks, Florian

2 1

[test] Is standalone use possible?
by Adam Nielsen 02 Oct '17

02 Oct '17

Hi all, I'm in the process of trying to remove the Boost dependency from my project, as it is causing too many difficulties for non-developers trying to run my code. This has been mostly solved by switching to C++11 and using the std:: implementations instead, however rather than rewrite all my unit tests I am hoping I can use a standalone version of Boost.Test, and distribute the code alongside my own. Unfortunately I am not quite sure how to extract the Test library out of the main Boost distribution. I have compiled "bcp" and used it to copy "test" into a new folder, but it seems to copy a huge chunk of Boost as well, including a bunch of libraries (system, thread, date_time, etc.) and I end up with 29 MB of source files, which seems wrong (especially considering my own codebase is barely 500 kB). Am I doing something wrong? I was hoping to use the header-only version of Boost.Test and this does seem to work when I #include the system-wide version of Boost (and don't link to any libraries), so it would seem that I don't need all those libraries that bcp copies. Is there any other way to access a slimmed-down standalone version of Boost.Test? Many thanks, Adam.

6 12

ק
by Ami Tavory 29 Sep '17

29 Sep '17

1 0

Enhancing the boost::asio::connect() socket interface
by martin doc 29 Sep '17

29 Sep '17

(apologies if this should be on -developers...) The connect() interface provided by boost caters to most common use and through access to the socket, various options can be managed without much hindrance. But there's one situation that boost does not handle well - when it is desirable to specify the local address to bind to. Going back to C, the usual program flow in this situation is something like this: fd = socket() bind(fd, local ip address) connect(fd, remote ip address) As boost::asio::connect() closes an open socket passed to it before making the remote connection, it's not possible to pass connect() a prebaked socket. In fact the amount of code required to use boost when binding a socket to a local address is more complicated than simply not using boost. What I'd like the boost community to consider is extending boost::asio to provide one or more variants of connect() that allows for a local endpoint (whether or not as an iterator I'll leave to others to debate but this isn't necessary - and then there's the M*N behavior or paired to decide) to be supplied in addition to the remote endpoint. I suppose I'm open minded as to whether or not the local address is supplied as an Iterator/endpoint as an extra arg or whether connect() is adopted to take endpoint pairs. Thoughts?

5 4

Analogous to DESTDIR for Boos installation
by Leo Cacciari 29 Sep '17

29 Sep '17

Hi, I need to prepare a binary distribution of Boost for deploying on company hosts. For this, I need to configure libraries with a prefix of say /usr/local, doing as per documentation ./bootstrap.sh --prefix=/some/path where /some/path is the actual path where the libraries and header flles will be installed on the various hosts. To prepare the package to be distributed (the actual packaging system used is irrelevant here, simply assuming a tar.gz would do) I need, however, to "install" everything under some other path, say /path/to/package/content. When using gnu packages, I usually do something like ./configure --prefix=/some/path make make DESTDIR=/path/to/package/content install and then I can prepare and distribute my package. I'm unable to find an analogous procedure for Boost. More exactly, I do not found a way to invoke the install phase of b2 with a different prefix than the one specified to the stage phase through the --prefix options to boostrap.sh I solved the problem in a unsatisfactory way by manually copying the files from both the source and the build directory to the content folder, but I'd really like to have an automated way to do it. Is this possible? If yes, how? And if not, does anyone have a better idea than manual copying? Thanks for the help -- Leo Cacciari Aliae nationes servitutem pati possunt. Populi Romani est propria libertas.

2 1

[review] The review period of Boost.DoubleEnded has been extended with one week. Now ends 7th of October.
by Thorsten Ottosen 28 Sep '17

28 Sep '17

Dear users and members of Boost, People have been requesting extra time for the review of Boost.DoubleEnded. We therefore continue one week extra, so the final date will be October the 7th. kind regards Thorsten Original review announcement ------------------------------------------ I'm proud to announce that the formal review of Benedek Thaler's Boost.DoubleEnded library starts today, September 21, and runs through September 30. This library is the result of Benedek's participation in Google Summer of Code 2015. The library may be downloaded from https://github.com/erenon/double_ended and the documentation may be found here: http://erenon.hu/double_ended/ Anyone is welcome to post a review and/or take part in subsequent discussions (see below for review guidelines). Introduction ------------ This is a container library that provides two containers: A. boost::devector B. boost::batch_deque Both containers provides efficient push_front and push_back operations, hence the name DoubleEnded. The boost::devector class can be seen as an extension of std::vector with efficient support for push_front (so boost::devector provides contiguous storage). In addition, it provides a customizable small buffer optimization like boost::small_vector(*). It furthermore allows for customization of the growth factor such that the user can decide if a reallocation should allocate 1.5 or 2 or whatever more memory. And finally it provides new functionality that does not exist in normal vector implementations -- this functionality allow the class to excel in performance in certain situations like serialization or transfer of data from sources that require a preallocated buffer. The boost::batch_deque is similar to std::deque, but with two important twists. Like std::deque, it provides reference stability when calling push_front/push_back. Reference stability is crucial for programs that uses intrusive containers e.g. using Boost.Intrusive (**). boost::batch_deque has the following main advantages: 1. It allows the user to specify the segment size 2. It allows for external iteration over the segments Taken together, they provide a very efficient and flexible basis for intrusive containers. Access to the segments also increases performance for tasks such as serialization. Finally, boost::batch_deque may be seen as an efficient alternative to std::vector if you want to replace a percent-wise memory overhead with a constant memory overhead and have no need for contiguous storage. Review guidelines ----------------- Please provide in your review whatever information you think is valuable to understand your final choice of ACCEPT or REJECT including Boost.DoubleEnded as a Boost library. Please be explicit about your decision. Some other questions you might want to consider answering: - 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 which compiler(s)? 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? More information about the Boost Formal Review Process can be found here: http://www.boost.org/community/reviews.html Kind regards Thorsten, Review manager (*) boost::small_vector: https://tinyurl.com/ycslp4ot (**) http://www.boost.org/doc/libs/1_64_0/doc/html/intrusive.html -- Best regards, Thorsten Jørgen Ottosen, Ph.D. Director of Research +45 23308797 Dezide (www.dezide.com)

1 0

[geometry] Runtime dimensionality
by Florian Lindner 28 Sep '17

28 Sep '17

Hello, I just started yesterday looking into boost.geometry to use on our own legacy system of Vertices (Points) in Meshes. I'm quite impressed how easy it is to adapt to existing code and got it working (with some workarounds) really quick. However, some problems remain. We have a Vertex object, with a dimension determined at runtime. The actual position is saved as VECTOR_T (usually an Eigen::VectorXd (double vector of arbitrary dimension)). One can get the coordinates using "const Eigen::VectorXd& Vertex::getNormal()" I was able to adapt to geometry by adding getters/setts for the dimensions: double getX() and getY() and BOOST_GEOMETRY_REGISTER_POINT_2D_GET_SET(mesh::Vertex, double, cs::cartesian, getX, getY, setX, setY) and it works! But in theory the vertices can be of arbitrary dimension, in practice it's usually 1, 2 or 3. What is the best way to adapt our Vertex object to geometry? - Change our Vertex so that it meets the model::point requirements. It worked so far, for the access I use: template<size_t Dimension> struct access<Vertex, Dimension> { static double get(Vertex const& p) { return p.getCoords()[Dimension]; } static void set(Vertex& p, double const& value) { Eigen::VectorXd vec = p.getCoords(); vec[Dimension] = value; p.setCoords(p); } }; In our code we rarely set the entries of an vector, so the code is a but ugly. Will likely change that to a compile-time get<Dim>() as a member of Vertex. My biggest problem is the dimensionality template<> struct dimension<Vertex> : boost::mpl::int_<2> {}; but I have no idea currently how to get that for an Eigen::VectorXd at compile-time? Do you have any idea? Thanks! Florian

5 8

Problem updating code to boost 1.64
by Tim Burgess 26 Sep '17

26 Sep '17

Hi, I have an application that I'm resurrecting. I originally coded it using Visual Studio 2010 with the boost that was current at the time (not sure what version that was). The following line of code used to build fine: if (CurrentAction[ 0].As <std::wstring>().compare( wstrFunctionName) == 0) With my current boost 1.64, I get the following error: >c:\users\tim\projects\surfacereader\screenreaderfunctionsdlg.cpp(146): error C2039: 'As': is not a member of 'boost::any' The intent of the code is as follows: If CurrentAction[ 0] (which is a boost::any) contains an std::wstring value, compare it to wstrFunctionName. Can anybody offer some guidance, please? Best wishes. Tim Burgess

2 1

[review][Fit] Review Results
by Matt Calabrese 24 Sep '17

24 Sep '17

Hello everyone, It is my privilege to announce that the Boost library count will once again be incremented as Paul Fultz II's library Fit has been accepted into Boost without conditions. Further details about this decision follow, but before that I'd like to thank Paul for all of the hard work he has put into Fit. Thanks also to everyone who participated in the review, with additional thanks to Vicente who was the review manager for the previous Fit review and who also provided a very detailed review and discussion during this review period. //////////////////////////////////////////////////////////////////////////////// Overview //////////////////////////////////////////////////////////////////////////////// Complete Reviews Considered: Zach Laine: Accept Vicente J. Botet Escriba: Accept John P. Fletcher: Accept Robert Ramey: Accept Jason Rice: Accept Barrett Adair: Accept Lee Clagett: Accept Glen Fernandes: Accept Louis Dionne: Accept Partial Reviews/Discussions Considered: Edward Diener Andrea Bocci Further Discussions (Previous Review): Steven Watanabe Peter Dimov Vladimir Batov Gavin Lambert Rob Stewart Bjorn Reese Manu Sanchez Artyom Beilis //////////////////////////////////////////////////////////////////////////////// Summary //////////////////////////////////////////////////////////////////////////////// Though not all responders reviewed every single aspect of the library, the reviews together adequately covered everything that is necessary for a decision to be made. This decision is made with additional confidence coming from usage of the library by some reviewers going back since during or before the initial review in early 2016. //////////////////////////////////////////////////////////////////////////////// Improvements Since Previous Review //////////////////////////////////////////////////////////////////////////////// This time around we received several more complete reviews than in the previous review period making it easier to be confident in a decision. A couple of notable changes since the 2016 review include: * Improved documentation * Default semantics for "capture" no longer try to determine whether to capture by reference or by value based on the argument being an lvalue or an rvalue (users can still get this via basic_capture) * Improved ADL awareness (internal calls are qualified) Throughout all of the discussions in this second review period, there were no explicit rejections of the library as a whole, though there were several recommendations from participants. A selection of those are listed here, though no changes are strictly required for acceptance: //////////////////////////////////////////////////////////////////////////////// Current Concerns //////////////////////////////////////////////////////////////////////////////// ////////// Design concerns: * Inheritance from user-callables has some potential pitfalls * Generated "infix" operators are "gimmicky" and don't add much value/may cause confusion * Placeholders should live in their own namespace ////////// Documentation concerns (not a complete list): * More examples requested * It is not always clear what files need to be #included for certain facilities in early examples * Better rationale for ConstFunctionObjects * Raw code is not linked from the examples ////////// Suggested name changes from reviewers: * Suggested rename of "partial()" to "partial_apply()" or "curry()" * Suggested rename of "conditional()" to "invoke_first()" or "call_first_of()" * Suggested rename of "apply" to "invoke" * Refer to "Callables" instead as "Invocables" (due to C++17 direction) * Library name "Fit" is not indicative of what it provides //////////////////////////////////////////////////////////////////////////////// Regarding the Author //////////////////////////////////////////////////////////////////////////////// Paul has been active in the Boost community for several years now. He is aware of his responsibilities going forward and I am confident that he will be a reliable maintainer for Fit for the foreseeable future (or whatever the library may be called). //////////////////////////////////////////////////////////////////////////////// Comments on the Name Boost.Fit //////////////////////////////////////////////////////////////////////////////// Note that what I say here is my personal opinion as a member of the community and does not necessarily reflect the opinions of others in the community nor of those in the steering committee. A few reviewers voiced that they would like to see a change of the library name "Fit". While multiple people did suggest this, my opinion is that this should be up to the author to choose whether or not he will change the name before it is added to boost and so I do not think it would be appropriate for us to strictly require or encourage such a change. If the author found the arguments against the name compelling, then he is welcome to change the name, but he should not feel obligated to do so. As a quick note on that, we have several high quality and highly regarded libraries in Boost with names that may not directly tell users what the library is for. Based on their popularity, I do not believe that it has significantly negatively affected their usage or ability to be found. A library name also may be important to an author as a creative outlet and I think it would be... poor form us to force such a change in this particular case and in other cases unless there are very strong reasons (i.e. the name is overly or intentionally misleading or there are legal concerns). I am not convinced that the current name is misleading enough to strictly require a change. As for existing precedent, some examples of libraries already in Boost with names that do not directly tell the user what the library is for include some of Boost's most highly regarded libraries such as Boost.Spirit (including Qi and Karma), Boost.Phoenix, Boost.Wave, Boost.Hana, and the recently accepted Boost.Beast. //////////////////////////////////////////////////////////////////////////////// Thanks again to everyone who participated in this review and in the previous review, and once again, congratulations to Paul on his library's acceptance into Boost. -- -Matt Calabrese -- -Matt Calabrese

1 0

[review] The review of Boost.DoubleEnded starts today: September 21 - September 30
by Thorsten Ottosen 21 Sep '17

21 Sep '17

Dear users and members of Boost, I'm proud to announce that the formal review of Benedek Thaler's Boost.DoubleEnded library starts today, September 21, and runs through September 30. This library is the result of Benedek's participation in Google Summer of Code 2015. The library may be downloaded from https://github.com/erenon/double_ended and the documentation may be found here: http://erenon.hu/double_ended/ Anyone is welcome to post a review and/or take part in subsequent discussions on the boost developer list (see below for review guidelines). Introduction ------------ This is a container library that provides two containers: A. boost::devector B. boost::batch_deque Both containers provides efficient push_front and push_back operations, hence the name DoubleEnded. The boost::devector class can be seen as an extension of std::vector with efficient support for push_front (so boost::devector provides contiguous storage). In addition, it provides a customizable small buffer optimization like boost::small_vector(*). It furthermore allows for customization of the growth factor such that the user can decide if a reallocation should allocate 1.5 or 2 or whatever more memory. And finally it provides new functionality that does not exist in normal vector implementations -- this functionality allow the class to excel in performance in certain situations like serialization or transfer of data from sources that require a preallocated buffer. The boost::batch_deque is similar to std::deque, but with two important twists. Like std::deque, it provides reference stability when calling push_front/push_back. Reference stability is crucial for programs that uses intrusive containers e.g. using Boost.Intrusive (**). boost::batch_deque has the following main advantages: 1. It allows the user to specify the segment size 2. It allows for external iteration over the segments Taken together, they provide a very efficient and flexible basis for intrusive containers. Access to the segments also increases performance for tasks such as serialization. Finally, boost::batch_deque may be seen as an efficient alternative to std::vector if you want to replace a percent-wise memory overhead with a constant memory overhead and have no need for contiguous storage. Review guidelines ----------------- Please provide in your review whatever information you think is valuable to understand your final choice of ACCEPT or REJECT including Fit as a Boost library. Please be explicit about your decision. Some other questions you might want to consider answering: - 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 which compiler(s)? 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? More information about the Boost Formal Review Process can be found here: http://www.boost.org/community/reviews.html Kind regards Thorsten, Review manager (*) boost::small_vector: https://tinyurl.com/ycslp4ot (**) http://www.boost.org/doc/libs/1_64_0/doc/html/intrusive.html

1 0

Linker error when using Boot regex on AIX
by Jyoti Sharma 18 Sep '17

18 Sep '17

I am using boost_1_61_0. In my code I have: #include <boost/regex.hpp> static boost::regex testxp("["); I have these libraries: libboost_regex.a libboost_regex.so I can see these libraries have symbols: LIBRARY: Shared object libboost_regex.so: 136 symbols imported. LIBRARY: Shared object libboost_system.so: 7 symbols imported. To build my program I have added these linking options: -Wl,-bnoquiet -Wl,-Bstatic -lboost_regex -lboost_system -Wl,-Bdynamic But I get this error during linking: ld: 0711-317 ERROR: Undefined symbol: .boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int) But that symbol is there: machine:/home> nm libboost_regex.so nm libboost_regex.so |grep do_assign ._ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEE9do_assignEPKcS7_j T 268508592 machine:/home> c++filt ._ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEE9do_assignEPKcS7_j .boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int)

2 3

Last Day for Boost Community Dinner Sign up
by Jon Kalb 18 Sep '17

18 Sep '17

Boost Users, Today is the last day to register for the Boost Community Dinner at CppCon. http://sched.co/Bhcr You do not need to be registered to attend CppCon to register for the Boost Community Dinner: https://cppcon.org/registration/ If you are going to be in the Seattle area a week from Tuesday, join us for a rare face-to-face get together of the Boost Community. See you there. Jon

1 0

[fiber] pooled_fixedsize_stack
by DePizzottri 14 Sep '17

14 Sep '17

Hi, I'm trying to replace fixedsize_stack with pooled_fixedsize_stack in my application witch spawns many fibers to reduce allocations, and got random crashes. For reproduction it is enough to replace fixedsize_stack with pooled_fixedsize_stack in performance\fiber\skynet_stealing_detach.cpp. Playing with stack size parameter does not help. Can anyone give some tip how to use pooled stack with fiber correctly? -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Users-f2553780.html

3 5

Help trying to compile boost 1_65_1 on Windows (Visual Studio 2017) with LZMA filter support
by Diego Luna 12 Sep '17

12 Sep '17

Hello everyone, this is my first post. Like the subject says, I need some help compiling boost 1_65_1 on Windows (Visual Studio 2017) on 64 bits with LZMA filter support. I've been compiling boost on Windows and Linux for some time without any problems, but the LZMA support in Windows, caused me some problems. I've downloaded and compiled the LZMA lib (XZ utils from https://tukaani.org/xz/) producing static (lib) and shared(dll+lib) libraries, in release and debug variants, then I have written the following user config jam (I think the problem is in the syntax of the file): ########################################## ## Using Python 3.6 (64 bits). ## using python : 3.6 : C:\\APPS\\PROGRAMMING\\Python36-64\\python.exe : C:\\APPS\\PROGRAMMING\\Python36-64\\include : C:\\APPS\\PROGRAMMING\\Python36-64\\libs : <address-model>64 ; ## Using lzma library 5.2.3. ## ## using lzma : 5.2.3 : <name>liblzma <include>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\include <search>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\lib64 : <variant>release <link>shared ; using lzma : 5.2.3 : <name>liblzmad <include>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\include <search>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\lib64 : <variant>debug <link>shared ; using lzma : 5.2.3 : <name>liblzma_static <include>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\include <search>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\lib64 : <variant>release <link>static ; using lzma : 5.2.3 : <name>liblzma_staticd <include>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\include <search>C:\\APPS\\PROGRAMMING\\LIBRARIES\\lzma\\lib64 : <variant>debug <link>static ; ########################################## The command line for the actual compiling (after bootstrap), (omitting the path to the other libraries for shortness, those are linked\compiled without any problem) is: .\b2 -j6 --user-config=.\user-config-64.jam --build-type=complete -q -sZLIB_SOURCE="%ZLIB_ROOT%" -sBZIP2_SOURCE="%BZIP2_ROOT%" -sICU_PATH="%ICU_LIB%" toolset=msvc-14.1 link="static,shared" threading=multi ^ variant="debug,release" architecture=x86 address-model=64 runtime-link=shared stage --debug-symbols=on --debug-store=database --debug-configuration -d2 The output is: notice: found boost-build.jam at E:/DATA/TMP/boost/boost_1_65_1/boost-build.jam notice: loading Boost.Build from E:/DATA/TMP/boost/boost_1_65_1/tools/build/src notice: Searching 'C:\WINDOWS' 'C:\Users\bakaneko' 'C:\APPS\TOOLS\UNIX-HOME' 'C:\Users\bakaneko' 'E:\DATA\TMP\boost\boost_1_65_1\tools/build/src' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/kernel' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/util' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/build' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/tools' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/contrib' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/.' for site-config configuration file 'site-config.jam'. notice: Configuration file 'site-config.jam' not found in 'C:\WINDOWS' 'C:\Users\bakaneko' 'C:\APPS\TOOLS\UNIX-HOME' 'C:\Users\bakaneko' 'E:\DATA\TMP\boost\boost_1_65_1\tools/build/src' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/kernel' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/util' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/build' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/tools' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/contrib' 'E:/DATA/TMP/boost/boost_1_65_1/tools/build/src/.'. notice: Loading explicitly specified user configuration file: E:\DATA\TMP\boost\boost_1_65_1\user-config-64.jam notice: Searching 'E:\DATA\TMP\boost\boost_1_65_1' for user-config configuration file 'user-config-64.jam'. notice: Loading user-config configuration file 'user-config-64.jam' from 'E:/DATA/TMP/boost/boost_1_65_1'. notice: [python-cfg] Configuring python... notice: [python-cfg] user-specified version: "3.6" notice: [python-cfg] user-specified cmd-or-prefix: "C:\APPS\PROGRAMMING\Python36-64\python.exe" notice: [python-cfg] user-specified includes: "C:\APPS\PROGRAMMING\Python36-64\include" notice: [python-cfg] user-specified libraries: "C:\APPS\PROGRAMMING\Python36-64\libs" notice: [python-cfg] user-specified condition: "<address-model>64" notice: [python-cfg] Checking interpreter command "C:\APPS\PROGRAMMING\Python36-64\python.exe"... notice: [python-cfg] running command 'DIR /-C /A:S "C:\APPS\PROGRAMMING\Python36-64\python.exe" 2>&1' notice: [python-cfg] running command 'C:\APPS\PROGRAMMING\Python36-64\python.exe -c "from sys import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1' notice: [python-cfg] ...requested configuration matched! notice: [python-cfg] Details of this Python configuration: notice: [python-cfg] interpreter command: "C:\APPS\PROGRAMMING\Python36-64\python.exe" notice: [python-cfg] include path: "C:\APPS\PROGRAMMING\Python36-64\include" notice: [python-cfg] library path: "C:\APPS\PROGRAMMING\Python36-64\libs" notice: [python-cfg] DLL search path: "C:\APPS\PROGRAMMING\Python36-64" notice: [python-cfg] Checking for NumPy... notice: [python-cfg] running command 'C:\APPS\PROGRAMMING\Python36-64\python.exe -c "import sys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())"' notice: [python-cfg] NumPy enabled notice: [lzma] Using pre-installed library notice: [lzma] Condition <link>shared <variant>release notice: [lzma] Using pre-installed library notice: [lzma] Condition <link>shared <variant>debug notice: [lzma] Using pre-installed library notice: [lzma] Condition <link>static <variant>release notice: [lzma] Using pre-installed library notice: [lzma] Condition <link>static <variant>debug notice: Searching '.' for project-config configuration file 'project-config.jam'. notice: Loading project-config configuration file 'project-config.jam' from '.'. notice: [msvc-cfg] msvc-14.0 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl.exe' notice: [msvc-cfg] msvc-11.0 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\cl.exe' notice: [msvc-cfg] msvc-14.1 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.11.25503\bin\HostX64\arm\cl.exe' notice: will use 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.11.25503\bin\HostX64\arm\cl.exe' for msvc, condition <toolset>msvc-14.1 'notice: [generate-setup-cmd] 14.1 is 14.1' 'notice: [generate-setup-cmd] 14.1 is 14.1' 'notice: [generate-setup-cmd] 14.1 is 14.1' 'notice: [generate-setup-cmd] 14.1 is 14.1' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvars32_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>32', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvars32_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvars32_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>32', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvars32_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>/<address-model>64', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_amd64_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>x86/<address-model>64', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_amd64_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>ia64/<address-model>', setup: 'call "C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Auxiliary/Build/vcvarsall.bat" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>ia64/<address-model>64', setup: 'call "C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Auxiliary/Build/vcvarsall.bat" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>arm/<address-model>', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_arm_.cmd" >nul ' notice: [msvc-cfg] condition: '<toolset>msvc-14.1/<architecture>arm/<address-model>32', setup: 'call "C:\Users\bakaneko\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_arm_.cmd" >nul ' notice: [zlib] Building zlib from source as boost_zlib notice: [zlib] Condition notice: [zlib] found zlib source in C:\APPS\PROGRAMMING\LIBRARIES\zlib\src_inc notice: [bzip2] Building bzip from source as boost_bzip2 notice: [bzip2] Condition notice: [bzip2] found bzip source in C:\APPS\PROGRAMMING\LIBRARIES\bzip2\src notice: [lzma] Using pre-installed library notice: [lzma] Condition Performing configuration checks - 32-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes - symlinks supported : no - junctions supported : yes - hardlinks supported : yes - C++11 mutex : yes - Boost.Config Feature Check: cxx11_auto_declarations : yes - Boost.Config Feature Check: cxx11_constexpr : yes - Boost.Config Feature Check: cxx11_defaulted_functions : yes - Boost.Config Feature Check: cxx11_final : yes - Boost.Config Feature Check: cxx11_hdr_mutex : yes - Boost.Config Feature Check: cxx11_hdr_tuple : yes - Boost.Config Feature Check: cxx11_lambdas : yes - Boost.Config Feature Check: cxx11_noexcept : yes - Boost.Config Feature Check: cxx11_nullptr : yes - Boost.Config Feature Check: cxx11_rvalue_references : yes - Boost.Config Feature Check: cxx11_template_aliases : yes - Boost.Config Feature Check: cxx11_thread_local : yes - Boost.Config Feature Check: cxx11_variadic_templates : yes - icu (64-bit) : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - lzma : yes - iconv (libc) : no - iconv (separate) : no - native-atomic-int32-supported : yes - message-compiler : yes - native-syslog-supported : no - pthread-supports-robust-mutexes : no - compiler-supports-visibility : no - compiler-supports-ssse3 : yes - compiler-supports-avx2 : yes - gcc visibility : no - long double support : yes warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. - libbacktrace builds : no - addr2line builds : no - WinDbg builds : yes - WinDbgCached builds : yes - lzma : yes (cached) - lzma : yes - lzma : yes (cached) Component configuration: - atomic : building - chrono : building - container : building - context : building - coroutine : building - date_time : building - exception : building - fiber : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - metaparse : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - stacktrace : building - system : building - test : building - thread : building - timer : building - type_erasure : building - wave : building ...patience... ...patience... ...patience... ...patience... ...patience... ...found 29592 targets... ...updating 2728 targets... ... When the compiling is done the related libraries (iostream) are: boost_iostreams-vc141-mt-1_65_1.dll boost_iostreams-vc141-mt-1_65_1.lib boost_iostreams-vc141-mt-gd-1_65_1.dll boost_iostreams-vc141-mt-gd-1_65_1.lib libboost_iostreams-vc141-mt-1_65_1.lib libboost_iostreams-vc141-mt-gd-1_65_1.lib The problem is that both, "boost_iostreams-vc141-mt-gd-1_65_1.dll" and "boost_iostreams-vc141-mt-1_65_1.dll" were linked to the debug version of the LZMA dll (libzmad.dll), and examining the log, both "libboost_iostreams-vc141-mt-gd-1_65_1.lib" and "libboost_iostreams-vc141-mt-1_65_1.lib" were statically linked to the debug version of the static LZMA library (liblzma_staticd.lib). I tried with some more combinations in the user jam file, but without success, and in most cases failing to detect LZMA. If you require any further information to help find the problem, please, let me know, I'd appreciate any help with this problem. Sorry for my English, best regards, Diego. P.S: The config log can be found here: config.log <https://www.dropbox.com/s/kkut7kuka2jgi57/config.log?dl=0>.

1 0

Re: [Boost-users] [stacktrace] Getting a stacktrace from unhandled exception in windows
by Don 12 Sep '17

12 Sep '17

-------- Original Message -------- Subject: Boost-users Digest, Vol 4770, Issue 1 From: boost-users-request(a)lists.boost.org To: boost-users(a)lists.boost.org Date: 9/10/2017 10:56 PM > Subject: Re: [Boost-users] [stacktrace] Getting a stacktrace from unhandled exception in windows > From: Stian Zeljko Vrba <vrba(a)quine.no> > Date: 9/10/2017 10:54 PM > > Unless you need the stacktrace to be logged to a text file, I suggest you look at this system-provided >facility: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).… ><https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85…> > > ...> IOW, you can get out more information than with boost.stacktrace with zero coding. > >> *Sent:* Monday, September 11, 2017 1:27:47 AM >> *To:* boost-users(a)lists.boost.org >> *Subject:* [Boost-users] [stacktrace] Getting a stacktrace from unhandled exception in windows >>>> I am trying use boost stacktrace to get a stack dump when my program encounters an unhandled exception >> under windows. I have installed a signal handler as described in the stacktrace documentation, and it >> gets called. However, the resulting stack trace is after everything has been unwound. >> >> For example, when I force a failure by dereferenceing a null pointer many levels down in my function >> hierarchy, the stack trace shows: >> >> 0# boost::stacktrace::detail::this_thread_frames::safe_dump_to_impl<char const *> at f:\home\tools\boost\boost\stacktrace\safe_dump_to.hpp:68 >> 1# boost::stacktrace::safe_dump_to at f:\home\tools\boost\boost\stacktrace\safe_dump_to.hpp:120 >> 2# my_signal_handler at f:\home\test\main.cpp:233 >> 3# 0x5171407B >> 4# my_signal_handler at f:\home\test\main.cpp:235 >> 5# 0x51713883 >> 6# __tmainCRTStartup at f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c:603 >> 7# WinMainCRTStartup at f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c:403 >> 8# BaseThreadInitThunk in kernel32 >> 9# RtlInitializeExceptionChain in ntdll >> 10# RtlInitializeExceptionChain in ntdll >> >> This is not particularly helpful, of course -- I want to know the call stack at the point of the >> failure. Is there any way to get that? What am I missing? Thanks for the suggestion, but yes, I want to log the data to a log file. It seems from the stacktrace documentation that this should work. Don

1 0