- Boost - lists.preview.boost.org

[winrt support] Adding support for Windows 8 store/phone to Boost libraries
by stgates 22 Jul '14

22 Jul '14

Hi, I work for Microsoft and we’ve been taking a look at making a some of the libraries in Boost work in the Windows 8 store and phone 8 runtime environment (WinRT). The main issue is use of Win32 desktop APIs that are banned in WinRT. The fixes generally involve updating to a newer non-banned version, like CreateEvent to CreateEventEx, or replace areas that call banned APIs using ifdef macro techniques. Similar to what already exists in some places of Boost when targeting different platforms or operating system versions. Files which do not use any banned APIs are largely unaffected. So far we’ve made the thread, chrono, system, and date_time libraries work in WinRT. To facilitate building and testing, changes are also required to the build and test libraries. Listed at the end of this message is a summary of the major changes made. I’m unfamiliar with the process for contributing back to Boost and would like to know what is the best way to work, to contributing back these changes to each of the individual libraries? I see the documentation for working with the git submodules (https://svn.boost.org/trac/boost/wiki/StartModPatchAndPullReq) Right now the changes for each library are in a forked repository on a new branch called ‘winrt’ from the ‘develop’ branch. For example the changes we've made for the chrono library can be located here: https://github.com/MSOpenTech/chrono/tree/winrt. Is the best way to proceed, or should I to just initiate a pull request to the develop branch on each of the individual libraries? Thanks, Steve Boost Build To support deciding which Windows API to target I added a new feature <windows-api> with values desktop, store, and phone. When utilizing the Visual Studio 2012 on Windows 8 or later the store and phone options are available, otherwise desktop is the default. Most of the changes in msvc.jam are to deal with selecting the correct vcvars setup script since with phone it is in a different location. I also added ARM support to the msvc toolset. For libraries which support the new Windows Runtime they now produce both the desktop and store binaries by default. This is done by calling the supported-windows-api rule I added in toolset.msvc which is called in the default-build section of each library’s Jamfile to indicate if targeting WinRT is supported. When building for the Windows 8 store or phone a new macro is now defined BOOST_WINAPI_FAMILY, set with the same value as WINAPI_FAMILY. This is then used in the individual Boost libraries to detect if targeting the new Windows Runtime and avoid certain banned APIs. To handle running tests against WinRT in an automated fashion that integrates well into the Boost workflow of running tests as part of the build, if windows-api is set to store, the test and all its binary dependencies need to have the APPCONTAINER requirement stripped. This then allows execution outside of the sandboxed Windows store environment. To do this all dependent dlls are copied into the tests executable’s folder, if using <link>shared. This is necessary to avoid modifying the APPCONTAINER flag on the actual product binaries. Just let me know if this needs more explanation, I’ll be glad to go into more detail if necessary. With this change the tests for Windows store run just like the existing Windows tests. I also added a new feature to control whether or not test binaries are actually executed, disable-test-execution. This is used to avoid running the ARM tests when building since Visual Studio 2012 doesn’t install on ARM devices. All these changes are in testing.msvc. Chrono The GetProcessTimes and GetThreadTimes functions doesn’t exist for WinRT and there are no replacements so the thread_clock and process user, system, and cpu clock features are disabled. Only process_real_cpu_clock is supported. Thread For the thread library most of the changes are around the fact that there is no way to directly create a thread in WinRT. To work around this I implemented the boost::thread class itself on top of std::thread. This actually leads to pretty clean code, much cleaner than directly targeting the WRL thread pool like in the C runtime. Other changes include moving from TLS to FLS and basic banned API replacements like WaitForSingleObjectEx for WaitForSingleObject. In general where it makes sense updates were made to utilize new APIs on platforms when available. Test For the Boost test library I added a new macro for turning on/off debugging support (BOOST_TEST_HAS_DEBUG_SUPPORT). WinRT doesn’t support creating processes so attaching a debugger to execution like this is disabled. There also are no APIs for accessing registry keys, so this feature has been disabled as well. -- View this message in context: http://boost.2283326.n4.nabble.com/winrt-support-Adding-support-for-Windows… Sent from the Boost - Dev mailing list archive at Nabble.com.

8 22

a release manager for Boost 1.56
by Andrzej Krzemienski 22 Jul '14

22 Jul '14

Hi, According to Boost calendar at http://www.boost.org/community/index.html, Master is open for bug fixes and doc changes. Can I thus merge this pull request: https://github.com/boostorg/optional/pull/6, which I consider a fix for a performance bug, but I anticipate other people may have other opinions? Regards, &rzej

6 9

New cross-platforms toolsets
by José Agustín Terol Sanchis 22 Jul '14

22 Jul '14

Hi, I am trying to add a new toolset for cross-compile to several platforms. So, I've added some ".jam" files (<mytoolset>_<platform>.jam) in path "tools/build/v2/tools", and I can use them to compile and test Boost libraries using bjam's parameter "toolset=<mytoolset>_<platform>". But I have some doubts/questions: 1) Do I need to add a .py file? Why some toolsets have a .py file? 2) Are .jam files generated by executing a Python script that translates all these .py files to .jam? That would be great since bjam's syntax is complex. 3) Should I add a .jam file per platform? Or can I made a unique .jam file for all platforms? If so, how do I change the resultant build-path in order to avoid possible overwrittings (or make it shorter)? I read most of the documentation of Boost's build system and Bjam that I found on the webpage, but maybe I've missed something. Thank you in advance, Agus Terol

2 1

VMD library version 1.7
by Edward Diener 22 Jul '14

22 Jul '14

The latest version of the VMD library, version 1.7, has been released. The VMD library is an advanced macro preprocessor library using variadic macros to provide the ability to parse/identify various types of preprocessor data as well as emptiness. The library works well within constraints that the designer of macros may impose on the end-user. I have re-engineered the library to provide extensive functionality beyond what had been there before. In particular the library can parse/identify pp-identifiers, Boost PP numbers, Boost PP arrays, Boost PP lists, Boost PP seqs, Boost PP tuples, and empty data. The library is also capable of parsing a sequence of such preprocessor type above as a single paarameter. It also adds better variadic support for Boost PP ASSERTs as well as for generating empty data and invoking identity. The library makes it possible to design macros whose logic changes depending on what type of preprocessor data is input, within the constraints of the preprocessor data it can parse. The library is on Github at https://github.com/eldiener/variadic_macro_data.git as well as in the Boost Library Incubator at http://rrsd.com/blincubator.com/bi_library/vmd/?gform_post_id=908. The library is on the Boost review queue and I am looking for a review manager for the library. The library is designed to be added to modular-boost beneath the libs sub-directory and needs the 'develop' branch of Boost PP to work properly. Once Boost 1.56 is released I will be merging the 'develop' branch of Boost PP into the 'master' branch and VMD will then work with the latest Boost in 'master'. Instructions for using the library, regenerating documentation, and running the test are in the top-level *.txt files. The library works with gcc 3.3 on up, all versions of clang, and VC++ 8 on up. It should also work with the latest version(s) of Intel C++. I realize that preprocessor metaprogramming is not as interesting as template metaprogramming but if you are at all interested in what the preprocessor can do using varaiadic macros, please take a look at the VMD library. Questions, comments, and whatever other remarks are welcome both here in this mailing list and/or a the Boost Library Incubator sight. if you would be willing to serve as a Review Manager for the library feel free to contact me personally. I realize nearly everyone is busy with the 1.56 release but if you are interested and eventually have time to look at the VMD and critique it, it would be greatly appreciated by me. Thank you ! Edward Diener

1 0

Re: [boost] [website] Library metadata and version history
by Adam Wulkiewicz 21 Jul '14

21 Jul '14

2014-07-21 0:44 GMT+02:00 Daniel James <dnljms(a)gmail.com>: > On 20 July 2014 22:32, Adam Wulkiewicz <adam.wulkiewicz(a)gmail.com> wrote: > > Btw, what needs to be done to modify this page? > > Is it stored in QBK and built automatically or is it stored in HTML > format > > only? > > It's generated by php. It can be updated with a 'meta/libraries.json' > in a module. Let me know if you want me to generate one for a module. > Is something like this ok: https://github.com/boostorg/geometry/blob/develop/meta/libraries.json ? I assume it should be in master branch/released? How this info is generated for modules without meta/libraries.json? Is it also hardcoded somewhere? Is website/generated/libraries.txt and/or boostorg/libs/maintainers.txt generated using this metadata? I'm asking because it seems that this data is duplicated in many places which is hard to maintain. > > > The same question for > > http://www.boost.org/users/history/version_1_56_0.html, however in this > case > > I managed to find HTML file in the Website module. > > If I'd like to modify those pages what should I do? > > That's generated from the quickbook file at: > > > https://github.com/boostorg/website/blob/master/feed/history/boost_1_56_0.q… > Ok, thanks. So for this pull request should be sent. Wouldn't it be convenient to also define it in modules as metadata? E.g. also in json file containing a table of pairs: - Boost version, - release notes in QBK format Regards, Adam

2 1

Printing Variables in Jam Files
by Axel Ismirlian 21 Jul '14

21 Jul '14

Hello, I am trying to debug the gcc.jam in for my platform, and I really wanted to know what the value of a certain variable model is. local model = [ feature.get-values address-model : $(properties) ] ; How do I print this out? How do you print anything in jam files really? Sincerely, -Axel

2 3

[boost-test] Is there interest in BOOST_AUTO_TEST_SUITE_TEMPLATE
by Damian Vicino 21 Jul '14

21 Jul '14

I was working last few days in refactoring some tests for some class templates we have to use BOOST_AUTO_TEST_TEMPLATE in place of having several BOOST_AUTO_TEST with different hardcoded parameters. In our testing setup, we usually have one suite per class we are testing. Since we want to cover all test of the suite using same template parameters, I defined the same parameters to every BOOST_AUTO_TEST_TEMPLATE. I was thinking, that maybe, it was nice to have the template parameter assigned to the test suite in place of the tests itself. Is someone else interested in this feature? If there is interest I can try to implement it. Regards, Damian

1 0

[boost-mpl] question about using template template class
by Damian Vicino 21 Jul '14

21 Jul '14

Hi, I quoted a template class to put it into a mpl::vector doing this: boost::mpl::vector<int, boost::mpl::quote2<std::pair>> Then, I obtained the 2nd element like this: using A=typename boost::mpl::at<T, boost::mpl::int_<2>>::type; I need now to pass the original template class to a class like this: template<class A, template<class, class> class C> class B{ C<A, B*> _c; }; I'm tried using apply or bind, but couldn't figure out the way to make it in a way that B accept it as second parameter. I get errors of the kind: error: template argument for template template parameter must be a class template or type alias template I also posted the question in stack overflow so if someone participates in stack overflow and want some potints the question is: http://stackoverflow.com/q/24856504/861649?sem=2 Thanks in advance, Damian

1 0

[website] Invalid characters in authors' names on the libraries lists
by Adam Wulkiewicz 20 Jul '14

20 Jul '14

Hi, I noticed that there are some invalid characters in the names, e.g. on the page http://www.boost.org/doc/libs/1_56_0_b1 Vicente J. Botet EscribÃ¡ Ion GaztaÃ±aga JoaquÃn M LÃ³pez MuÃ±oz AFAIU it's not a problem with the charset because it's explicitly written this way in HTML: Vicente J. Botet EscribÃ¡ Ion GaztaÃ±aga JoaquÃn M LÃ³pez MuÃ±oz So I'm guessing that there is a problem with some conversion from ... to HTML or with the ... source file. If the problem couldn't be fixed, the replacing of the problematic letters would be an obvious workaround. Btw, what needs to be done to modify this page? Is it stored in QBK and built automatically or is it stored in HTML format only? The same question for http://www.boost.org/users/history/version_1_56_0.html, however in this case I managed to find HTML file in the Website module. If I'd like to modify those pages what should I do? Regards, Adam

2 1

Re: [boost] [EXTERNAL] Re: [Boost-users] [1.56.0] Beta 1 Available
by Belcourt, Kenneth 20 Jul '14

20 Jul '14

On Jul 20, 2014, at 1:58 AM, Rainer Deyke <rainerd(a)eldwood.com> wrote: > On 18.07.2014 17:01, Marshall Clow wrote: >> Boost release 1.56.0 beta 1 is now available from SourceForge > > I'm experiencing problems cross-compiling Boost 1.56.0b1 (host Linux > Mint 17 x86_64, target x86_64-w64-mingw32), and I think this is due to > the build system not picking up my user-config.jam. In Boost 1.55.0, I > placed my user-config.jam in <boost_root>/tools/build/v2, and it worked. > In Boost 1.56.0b1 this directory no longer exists, so I tried placing > my user-config.jam in <boost_root>/tools/build and in > <boost_root>/tools/build/example where the example user-config.jam is > located. Neither of these seem to work, i.e. the invoked compiler is the native compiler g++ and not the cross-compiler specified in user-config.jam. Try putting user-config.jam into tools/build/src and see if it finds it there. If not, you can run b2 —debug-configuration and it will output where it searches for user-config.jam (and other components). — Noel

1 0