January 2015 - Boost - lists.boost.org

libraries.json missing boost-version, update-version
by Peter Dimov 05 Jan '15

05 Jan '15

I notice that the library list at the website has a "First Release"entry for each library; these apparently come from the tag <boost-version> in libraries.xml, which also has an <update-version>. The meta/libraries.json files, however, appear to have no such data. Is this intentional?

2 1

[build] Tests automatically create header links, but library builds do not
by Peter Dimov 05 Jan '15

05 Jan '15

If I remove my boost/ directory, and attempt to build, for example, atomic, by going into libs/atomic/build and invoking b2, it fails due to a missing header: D:\tmp2\libs\atomic\build>b2 toolset=msvc-8.0 ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_x86_amd64.cmd ...updated 1 target... Performing configuration checks - symlinks supported : no - junctions supported : yes - hardlinks supported : yes ...found 208 targets... ...updating 5 targets... common.mkdir ..\..\..\bin.v2\libs\atomic\build\msvc-8.0\debug\threading-multi compile-c-c++ ..\..\..\bin.v2\libs\atomic\build\msvc-8.0\debug\threading-multi\lockpool.obj lockpool.cpp ..\..\..\boost/atomic/detail/ops_msvc_x86.hpp(20) : fatal error C1083: Cannot open include file: 'boost/type_traits/make_signed.hpp': No such file or directory [...] Same if I do b2 --with-atomic from root. However, if I go into, say, libs/smart_ptr/test and invoke b2 there, it works: D:\tmp2\libs\smart_ptr\test>b2 toolset=msvc-8.0 ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsa ll_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsa ll_x86_amd64.cmd ...updated 1 target... Performing configuration checks - symlinks supported : no - junctions supported : yes - hardlinks supported : yes ...patience... ...found 1722 targets... ...updating 1253 targets... common.mkdir ..\..\..\bin.v2\libs\smart_ptr common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test\yield_k_test~mt.test common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test\yield_k_test~mt.test\msvc-8.0 common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test\yield_k_test~mt.test\msvc-8.0\debug common.mkdir ..\..\..\bin.v2\libs\smart_ptr\test\yield_k_test~mt.test\msvc-8.0\debug\threading-multi mklink-or-dir ..\..\..\boost\smart_ptr Junction created for ..\..\..\boost\smart_ptr <<===>> ..\include\boost\smart_ptr link.hardlink ..\..\..\boost\predef.h Hardlink created for ..\..\..\boost\predef.h <<===>> ..\..\predef\include\boost\predef.h [...] Why is that? My first thought was that this was due to the fact that I was missing libs/Jamfile.v2 (I do various "clean" installations as an experiment to see what's needed and what isn't), but I put it back there and it doesn't help.

4 15

Linux regression test runners - What do devs want?
by Tom Kent 05 Jan '15

05 Jan '15

I've been pondering this recently, but a forced upgrade of my azure VMs last night is pressing the issue...and I wanted to solicit feedback before I go and set things back up... I've currently been running three testing machines for linux, with several testers on each, (windows is completely separate, and I'm happy with how that is running)...here was my past strategy: teeks99-03 - develop - lots of compiler versions (all I could get to run on ubuntu 12.04: gcc-4.4-4.8, clang-3.0-3.4) teeks99-04 - develop - only two compilers, with fast turnaround times (gcc-4.8, clang-3.4) teeks99-05 - master - lots of compiler versions (all I could get to run on ubuntu 12.04: gcc-4.4-4.8, clang-3.0-3.4) I can try to set things up like this again, but there are two reasons I was thinking about changing: 1) It seems that a lot of the gcc/clang versions have the same pass/fail results as the other versions of that compiler, so we're not adding a ton (though we may be adding the crucial points where a compiler change breaks something...is this something that devs have seen in practice?) 2) The new version of my runners (Ubuntu 14.04) doesn't easily support the old gcc versions, it would take a lot of effort to get some of the old ones running. Clang is even worse...it is much more difficult to get even two versions running side by side now. Instead of running lots of different versions, I was thinking about running various compatibility options of the two main compilers...I've seen some other test runners with things like libc++, c++11, c++14, etc. My real question, would developers be better served by these options than different versions? Would they prefer both with longer revisit times between each test type? Other thoughts? Tom

6 5

gcc.archive fails under Windows/Cygwin
by Peter Dimov 05 Jan '15

05 Jan '15

Fails like this: gcc.archive ..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\libboost_system-gcc48-1_58.a The system cannot find the path specified. The system cannot find the path specified. "/usr/i686-pc-cygwin/bin/ar.exe" rc "..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\libboost_system-gcc48-1_58.a" "..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\error_code.o" "/usr/i686-pc-cygwin/bin/ranlib.exe" "..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\libboost_system-gcc48-1_58.a" ...failed gcc.archive ..\..\..\bin.v2\libs\system\build\gcc-4.8.3\release\link-static\libboost_system-gcc48-1_58.a...

1 0

Help required to start contributing to Boost.
by Ameya Prabhu 03 Jan '15

03 Jan '15

Hello, I am new to Boost. I'm fairly well at C++ and am programming since the last 6 months. I would like to contribute to its development. Can someone please help me out? I had a look at the website but I am unable to find bugs that are suitable for beginners. Thanks!

5 4

[move] traits file problem causing many test failures.
by Fletcher, John P 03 Jan '15

03 Jan '15

There is a problem on the develop tests which was not there yesterday. In file included from ../libs/phoenix/test/regression/bug4853.cpp:16: In file included from ../boost/range/adaptor/transformed.hpp:15: In file included from ../boost/range/detail/default_constructible_unary_fn.hpp:13: In file included from ../boost/optional/optional.hpp:48: In file included from ../boost/move/utility.hpp:25: ../boost/move/traits.hpp:27:10: fatal error: 'boost/move/detail/type_traits.hpp' file not found #include <boost/move/detail/type_traits.hpp> ^ 1 error generated. I hope this can be sorted out soon. Happy New Year John

2 2

[build] msvc.write_setup-script always called for msvc-12.0
by Peter Dimov 02 Jan '15

02 Jan '15

When I do (for example) C:\Projects\boost-git\boost\tools\boostdep\build>b2 toolset=msvc-8.0 I get ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86_amd64.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_x86_amd64.cmd ...updated 1 target... which correctly generates the setup scripts for the specified msvc-8.0, but also unconditionally generates the setup scripts for msvc-12.0, which are not needed at this time. This msvc-12.0 generation occurs even if I use a non-msvc toolset, or even just do b2 --show-libraries. C:\Projects\boost-git\boost>b2 --show-libraries ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86.cmd ...updated 1 target... ...found 1 target... ...updating 1 target... msvc.write-setup-script C:\Users\PETERD~1\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86_amd64.cmd ...updated 1 target... The following libraries require building: - atomic - chrono [...]

1 0

[filesystem] Junction support on Windows?
by Peter Dimov 02 Jan '15

02 Jan '15

Filesystem provides support for hard and symbolic links, but on Windows, hard links do not work on directories and symbolic links do not work for the majority of users because they require elevation by default. That is why, for example, "b2 headers" was changed to also use junctions, if possible. But if I, for another example, want to replicate "b2 headers" from a C++ program using Filesystem, I can't, because it offers no junction support. Should create_directory_symlink be enhanced to create a junction, if CreateSymbolicLink is not available or fails with ERROR_ACCESS_DENIED?

2 2

[filesystem] resize_file_api leaks a HANDLE
by Peter Dimov 02 Jan '15

02 Jan '15

... when SetFilePointerEx or SetEndOfFile fails. BOOL resize_file_api(const wchar_t* p, boost::uintmax_t size) { HANDLE handle = CreateFileW(p, GENERIC_WRITE, 0, 0, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, 0); LARGE_INTEGER sz; sz.QuadPart = size; return handle != INVALID_HANDLE_VALUE && ::SetFilePointerEx(handle, sz, 0, FILE_BEGIN) && ::SetEndOfFile(handle) && ::CloseHandle(handle); }

3 2

updated Boost.Test devel->master: documentation needs
by Dave Gomboc 02 Jan '15

02 Jan '15

> What left in docs: > > * general reformating of existing pages and separation to "user's guide" and "advanced usage scenarios" (I am working on this) > * BOOST_TEST tool, including figuring out what to do with old testing tools description and reference > * data driven test cases (Raffi works on this) > * decorators support (Andrzej volunteered to help with this) > * run by name/label description. Including multitude of new syntax options > * figure out doxigen issues > * figure out new format for examples > * few minor issues with Boost.Logos > * investigate Boost.pp style left side menu (optional) > * interaction testing (optional) > * production use of Boost.Test (optional) > * anything else missing from above (hopefully nothing big) > > Any takers? > Gennadiy Thanks for posting this list, Gennadiy. I'll volunteer to write up a section on the production use of Boost.Test. I will, however, need source material in order to do so. Boosters, have you ever or do you now use either Boost.Test or an alternative testing framework in a production-like manner? - with more complicated or less common build systems - when regression testing across multiple versions of dependent libraries - when regression testing across multiple toolchains and/or platforms - as part of deployments within virtualized containers - et cetera If so, could you please describe your setup, either here on-list or privately to myself? I will collect the responses received, and from them, prepare documentation so that people new to Boost.Test can get started with setting up production-quality regression testing environments. Dave

2 1