- Boost - lists.boost.org

[winapi] [thread] Conflicting declarations on MinGW
by Antony Polukhin 01 Jan '16

01 Jan '16

Hi, Some of the Boost.DLL tests produce following warnings: ../boost/thread/win32/thread_primitives.hpp:175:83: warning: declaration of 'void* boost::detail::win32::GetModuleHandleA(const char*)' with C language linkage ../boost/detail/winapi/dll.hpp:47:1: warning: conflicts with previous declaration 'HINSTANCE__* GetModuleHandleA(boost::detail::winapi::LPCSTR_)' ../boost/thread/win32/thread_primitives.hpp:195:94: warning: declaration of 'int (__attribute__((__stdcall__)) * boost::detail::win32::GetProcAddress(void*, const char*))()' with C language linkage ../boost/detail/winapi/dll.hpp:82:1: warning: conflicts with previous declaration 'int (__attribute__((__stdcall__)) * GetProcAddress(boost::detail::winapi::HMODULE_, boost::detail::winapi::LPCSTR_))()' Andrey, Vicente what's the best way to resolve such issues? -- Best regards, Antony Polukhin

5 12

[qvm] deduce_xx traits wouldn't introduce ODR issues.
by Vicente J. Botet Escriba 31 Dec '15

31 Dec '15

Hi, I wonder if the deduce_xx traits wouldn't introduce ODR issues. Remember the TBoost.Conversion library where conversion between two types was customizable. The fact that deduce_xx traits have two types would promote ODR as there is no one type that is expected to do the customization. I believe that changing the default to something depending on the first argument will be better than using the specific qvm type as result. If this is not enough, you could add symbolic operations taken the result type as parameter, e.g. if a+b is not something specified by A, the user could use sum<C>(a,b) Forget my comment if there is no ODR issue. Best, Vicente

7 33

[dll] ready for master branch. Please merge
by Antony Polukhin 29 Dec '15

29 Dec '15

Hi, Boost.DLL is ready to appear in next release of Boost. Please, merge the DLL related changes into the master branch of boostorg/boost (changes for the develop branch were merged here: https://github.com/boostorg/boost/pull/94) Thanks! -- Best regards, Antony Polukhin

2 2

[qvm] Today is the last day of QVM formal review extended period
by Adam Wulkiewicz 23 Dec '15

23 Dec '15

Dear Boost Community! Today is the last day of the extended period of QVM library formal review. Since now we received 4 reviews. I encourage you to send more, there is still some time left. I'd like to thank all of you who have sent reviews as well as those who have taken part in the discussions. I'm going to wait for additional reviews a few days in case someone wanted to send one after the end of the review period. Does any of you plan to do it? Regards, Adam

1 0

Broken Link
by Mudit Sharma 23 Dec '15

23 Dec '15

All, The boost.python link provided on this page is broken: http://www.boost.org/doc/libs/1_60_0/more/getting_started/windows.html (See Boost.Python in section 3) Can anyone fix this? Thanks M

2 1

[autoindex] Default building with an Index
by Edward Diener 22 Dec '15

22 Dec '15

The documentation for VMD supports building with an index but I had not made this the default situation. This is my mistake. Can I assume the official build of the docs for a release supports building with an index via autoindex ? If so I will change the jamfile to support this as the default for the future and assume any end-user wishing to regenerate the docs has autoindex support also as part of the distribution as long as my jamfile is setup correctly for autoindex.

2 1

[doc] Releases 1.59 and 1.60 missing some tools documentation
by Edward Diener 22 Dec '15

22 Dec '15

In the 1.60 release, and I also just noticed in at least the 1.59 release also, the documentation links to the Release and Regression tools go to an invalid URL. Also while the documentation link to Boost.Build goes to a general explanation page the subsequent documentation link to Documentation goes to an invalid URL. Is this what we want, and that the end-user should have to "build" the documentation ? It seems doubtful, considering what a trial it often is for developers themselves to build the documentation given the tools available to do so. I think that this needs to be corrected in upcoming releases.

1 0

[regression] run.py merge option
by Antony Polukhin 22 Dec '15

22 Dec '15

Hi, How hard would it be to add a --merge option to run.py? Motivation: I'm experimenting with running all the regression tests on TravisCI https://github.com/apolukhin/boost_indirect_testing. Unfortunately, it has some hard limits, so a task can not work more than 2 hours. I've ended up splitting all the Boost tests by libraries and running tests on per library basis. Unfortunately, when the test results are send to server, only one library result is displayed in resulting matrix (search http://www.boost.org/development/tests/develop/developer/summary.html for indirect_travisci_tests) So I'd like to get a --merge option, that will allow merge of all the results by tester_name+revision. For example if results for 'geometry' and 'any' are sent with tester name `indirect_travisci_tests` and revision 74f85d, then show them in a single column. This may be also useful for those test runners that run tests on embedded or emulated devices (running all the Boost tests on emulated MIPS device may take a few weeks; running the tests on multiple emulated MIPS devices will speed up things) -- Best regards, Antony Polukhin

1 0

Software Freedom Conservancy Support
by Jon Kalb 22 Dec '15

22 Dec '15

This is not a technical message, but instead focuses on Boost Administration. Software Freedom Conservancy in a Financial Fight for its Life Software Freedom Conservancy, the non-profit home of Boost is facing an existential threat. Historically, Conservancy has been funded by corporate donations. This works great when it works, but a management shake-up, change in priorities, or a bad quarter at a large donor can derail the organization¹s programs. It has become obvious that Conservancy must move to a Supporter-driven funding model, where individuals who believe in Conservancy¹s mission of supporting open source projects, such as Boost, make a personal commitment to support that effort. Conservancy's fundraiser, found at https://sfconservancy.org/supporter/, is centered around asking individuals who care about the work that Conservancy does to donate $120/year, or just $10/month, to support the organization. Conservancy seeks about 2,500 Supporters to continue its current work, and 750 Supporters to continue a ³bare minimum² of services to its projects. What does this mean to Boost? Boost receives a myriad of important services (see https://sfconservancy.org/members/services/ ) from Conservancy. We¹ve relied on Conservancy since 2007 to provide them. Here are some of the things that Conservancy does for Boost that are in the ³bare minimum² category: * Dealing with all the financial and contractual details regarding our annual C++ Now conference. It was BoostCon that brought Boost and Conservancy together. C++Now 2016 will the the tenth annual BoostCon and it is a tribute to what we¹ve accomplished working together. * Handle our Google Summer of Code payments and travel, including handling all financial transactions with Google to receive and then disperse the money. * Coordinating travel reimbursements for Boost contributors (both developers and students) to attend conferences. * Receiving and tracking all donations to Boost. * Keeping the non-profit status for us so that we don't have to form our own org and file our own paperwork. As the Chair of the Boost Steering Committee, I cannot overstate how important this is to our existence as an organization. Here are some of the services Boost has received in the wider category: * Dealing with questions from the community (including license-governing bodies like OSI) about Boost's license. * Discussing the issue of copyright governance and contributions with large corporations who want their employees to contribute to Boost but need legal assurances or have questions relating to Boost's license or contribution policies. * Reviewing and handling licensing terms of third-party software that relate to Boost in some way, and giving us feedback and answers about issues related to it. * General legal consulting on issues that we run into as an open source non-profit. As you can see, Boost really relies on the important work of Conservancy. Support from Boost Boost, like all of Conservancy¹s projects, contributes 10% of our revenue to Conservancy¹s general fund. (The other 90% is maintained and administered by Conservancy at the direction of the Boost Steering Committee to advance the Boost project.) But that 10% of revenue from all Conservancy¹s member projects doesn¹t add up to enough to even employee one full time person, let alone the already overworked staff of three that Conservancy has. Donors must make up the difference. When Conservancy launched its fundraising effort, I sent out a request to past BoostCon/C++Now attendees asking for support and I¹m proud and delighted to say that a number of Boost community members have already stepped up. One told me that her company will be matching her support. Boost is one of Conservancy¹s oldest and largest projects, so it is right that Boost community members make up a fair proportion of its supporters. I encourage you to choose Conservancy as one of your charitable gifts this holiday season. (Conservancy is a 501(c)(3) charity incorporated in New York, and donations are typically deductible on U.S. taxes.) Please visit: https://sfconservancy.org/supporter/ If you are able to join the others from the Boost community that are making this gift, please let me know. I¹d like to personally thank you. Jon Kalb Chair, Boost Steering Committee

1 0

Becoming Maintainer of the Iterator Library
by Nathan Wilson 21 Dec '15

21 Dec '15

Hi all, There was talk on the mailing list a few months back, and was apparently discussed at CppCon in September, about becoming a Library Maintainer. This was pertaining to Libraries which are either being maintained by the CMT, or as Edward Diener mentioned, Libraries which aren't in the CMT's hands but the current maintainer(s) don't have time to devote to maintaining the particular library. That said, after having discussed it with a few people outside the mailing list, I would like to volunteer to become a Maintainer of Boost's Iterator Library. I have not been active on Boost's mailing list, but have participated in the C++ Standardization Process with the paper Delimited Iterators (http://open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4257.html) which will be in the Library Technical Specification 2. I have also submitted/committed some Patches in Clang as well. I just wanted to mention those couple of things as a point of reference so this didn't seem entirely random. Anyway, I'd be really excited to help contribute and help Boost by becoming a Maintainer of the Iterator Library. I do have some concern about compiling on various versions of Windows/OSX though. I have a Windows 8.1 machine and could obviously use Visual Studio, but I'm not too sure about verification of older Windows/OSX versions. On Linux I can certainly create VMs for various distros. If anyone has some best practices or advice about handling different OS distros/versions, that would be great. Please let me know if there are any questions. Thank you, Nathan

1 0