2013/7/23 Jens Weller

...

Gesendet: Dienstag, 23. Juli 2013 um 13:36 Uhr Von: "Mathias Gaunard" An: boost@lists.boost.org Betreff: Re: [boost] Announcing boost dependency analyzer

On 23/07/13 12:08, Jens Weller wrote:

...

Hello to the boost community,

I'd like to announce the release of a small tool, that allows you analyze the dependencies in boost. It is based on bcp, requirement is that you have bcp build and well a version of boost to analyze installed.

Simply select the boost directory (the tool also might find BOOST_ROOT) and the location of bcp, and the tool will start. This will take a little time, depending on your machine, on my multicore intel ist 90 seconds - 2 minute. The tool will store this information into a database, so that with the next start, this will be a lot shorter.

This is probably the biggest problem of this tool.

AFAIK bcp doesn't distinguish between header dependencies, source dependencies, link dependencies, test dependencies and documentation dependencies. Not really, but I could. There will be a nother release very soon, as I found that a bunch of libraries are not covered by maintainers.txt, my current source for feeding bcp.

I found 6 libraries (+ lexical_cast) which aren't covered through maintainers.txt, most prominent mpi and system.

I've merged maintainers.txt from trunk to release branch. This must fix at least some of the issues. But Boost.MPI and boost.System are still missing. -- Best regards, Antony Polukhin

Gesendet: Dienstag, 23. Juli 2013 um 23:24 Uhr Von: "Daniel James" An: boost@lists.boost.org Betreff: Re: [boost] Announcing boost dependency analyzer

On Tue, 23 Jul 2013, at 12:08 PM, Jens Weller wrote:

...

What libraries might be missing? I'm reading the libs from maintainers.txt, which isn't all the boost libs. For example, lexical_cast is missing, and function_types is twice in there. (C&P error or missing library?)

Looking at the file's history it was inserted in the wrong place the first time, and then was later added in the right place, apparently not noticing the existing entry.

Sometimes the idea of what is a library, or part of a library, is quite fluid. Lexical cast is often seen as part of 'conversion', similarly 'math' is sometimes considered a collection of libraries itself. You might have better luck considering the new modules, as some will contain multiple libraries, and at least one will contain none, but still be a dependency.

Well, as I'm based on boost bcp, I'm kind of viewing boost through its eyes. I've done some research in the bcp code to find out, how its reading, but couldn't find a single source for library name mappings. Looking for an easily readable source, maintainers.txt is a good source distributed.

'maintainers.txt' was never intended to be a list of libraries, but a list of who's responsible for various parts of boost. A better list of libraries is possibly the one used for the website:

http://www.boost.org/doc/libraries.xml

To get the list for a specific version you need to filter based on 'boost-version', and the optional 'boost-min-version' and 'boost-max-version' tags. After modularization the idea is to store this data within the modules, although the complete details will have to be stored somewhere, so it might be possible to keep that file up.

See, thats the problem for my tool currently, its based on the directory you select. Is libraries.xml part of the distribution? I could not find it under %boost_root%/doc. kind regards, Jens Weller

Gesendet: Dienstag, 23. Juli 2013 um 23:49 Uhr Von: "Daniel James" An: boost@lists.boost.org Betreff: Re: [boost] Announcing boost dependency analyzer

On Tue, 23 Jul 2013, at 11:34 PM, Jens Weller wrote:

...

See, thats the problem for my tool currently, its based on the directory you select. Is libraries.xml part of the distribution? I could not find it under %boost_root%/doc.

No, it's part of the website.

Well, thanks for your feedback, downloading isn't the huge problem with Qt. Added to the feature list. kind regards, Jens Weller