January 2020 - Boost - lists.boost.org

Query on Project Multiprecision/Math GSoC 2020
by Christopher Kormanyos 06 Jan '20

06 Jan '20

Dear Boost Is there a place to post and describe a potentialGSoC 2020 project? We have a potential project for GSoC 2020. It involvessignificantly extending the precision of Boost.Multiprecisionand harmonizing these extensions and tests with Boost.Math.I have the proposal worked out in plain text and would liketo post it or share it. We have discussed this project (in PM) with the knownrecent authors and maintainers of Multiprecision and Math,and interest is strong. On a personal note, my name isChristopher Kormanyos, previous three-time Boost GSoCmentor. In previous years, I have also contributed to bothMath and Multiprecision. Thank you and kind regards, Chris

1 0

Re: [boost] Recommended way of generating documentation
by pbristow＠hetp.u-net.com 06 Jan '20

06 Jan '20

> -----Original Message----- > From: Boost <boost-bounces(a)lists.boost.org> On Behalf Of Richard Hodges via > Boost > Sent: 1 January 2020 12:03 > To: boost(a)lists.boost.org List <boost(a)lists.boost.org> > Cc: Richard Hodges <hodges.r(a)gmail.com> > Subject: Re: [boost] Recomended way of generating documentation > > Treading carefully here as I'm new to boost library maintenance... > > > So that you can cross-reference the Doxygen reference with whatever > > other > documentation you have > > http://www.doxygen.nl/manual/autolink.html suggests that links to external URLs > are recognised by doxygen. Presumably linking to the correct place vis-a-vis > release/developer builds can be controlled with a macro in a generated Doxyfile? > > > And it's Doxygen to XML, XML to Boostbook. Then of course Boostbook to > Docbook, and Docbook to HTML. > > Other than the very pleasing boost documentation styling, is this seemingly > convoluted conversion route necessary? Is it not possible to configure a Doxyfile to > contain the correct styling? > > I have no knowledge of the evolution of boost documentation and have no axe to > grind, but as a newcomer it seems to me that there is a lot of 'unnecessary' > compication in the production of documentation. I appreaciate that there's no real > sense in revisting existing libraries, but for new ones wouldn't it be prudent to > choose the shortest possible path which involves the least learning and > maintenance? It depends on the size of the documentation. For 'trivial' documentation, the Doxygen and Markdown combination is acceptable, but I believe strongly that the best Boost documentation is done using the Quickbook toolchain (including Doxygen syntax comments to provide a references section). A killer feature of Quickbook is the ability to include code snippets from actual C++ examples that can be run, ensuring that what you get is what compiles and runs. As a mark-up language Quickbook is pretty obvious (apart from the gotcha of using indent-spaces as a way to add code sections - a common but quick'n'dirty markup feature that can cause some confusion). Paul

1 0

Boost ASIO
by live man 03 Jan '20

03 Jan '20

Hi, We have been using Boost for our firmware product which runs in ARM processor. However for development we make use of Visual Studio IDE. We also have our own TCP / IP suite which defines its own socket.h file. We are facing issue related to using Boost ASIO in Windows development platform. It seems that the library by default includes windows networking header files - which we do not want. Instead we want Boost ASIO to make our own library socket headers and declaration. We noticed that if we include Boost ASIO and our TCP / IP socket declaration we get re-definition error and compilation fails with lots of errors? Please let us know how we can resolve the issue with the objective mentioned above? Thanks in advance. Regards, Prakash

2 2

Google Summer of Codes 2020
by saloni garg 02 Jan '20

02 Jan '20

Hello, My name is Saloni Garg. I am an undergraduate student of B.tech in computer engineering. Currently, I am in my second year and I am looking forward to participate in this year's Google Summer of code 2020. So, I want to know, if Boost organization is planning to be a part of this year's Google Summer of codes 2020? Thank you! Saloni Garg

1 0

Recomended way of generating documentation
by Alexander Grund 01 Jan '20

01 Jan '20

Hi, I'm currently in the process of generating documentation in a Boost usable format and got a couple questions. The documentation is currently in-source in Doxygen format and has a markdown file for the start page. 1. Which aliases do I need and for what? I've seen boostdoc and boostrelease but couldn't find a description what and why they are 2. Where do the documentation files need to go? It seems using BJam naively outputs them to bin.v2 not to the libraries doc folder which I'd even see useful because generated files should not clobber the source tree 3. What benefit is there going from Doxygen (over multiple conversions) to boostbook? Can't I just go from Doxygen to HTML? 4. If the above: Calling `doxygen mylib.html` in BJam generates a mylib folder and a mylib.html redirecting into that folder. Both hardcoded to go into a subfolder of bin.v2. How is that useful/useable? Wouldn't I want a 'html' folder and an index.html redirecting to the index.html contained or no redirection file at all? 5. As I'm thinking about calling doxygen manually: Do I need to do anything so e.g. mylib shows up in boost/doc/html? Why is only a subset of the libraries there? Thanks for any help or pointers! Alexander Grund

6 5