|
Boost : |
Subject: Re: [boost] Announcing boost dependency analyzer
From: Jens Weller (JensWeller_at_[hidden])
Date: 2013-07-23 15:51:02
> Gesendet: Dienstag, 23. Juli 2013 um 13:36 Uhr
> Von: "Mathias Gaunard" <mathias.gaunard_at_[hidden]>
> An: boost_at_[hidden]
> 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.
>
> Therefore you end up with way more than what you actually care about.
Thats why I want to add filters, most of the library views are already now readable.
Filtering will allow to filter after name or categories (Headers,libs, doc, test, etc.)
kind regards,
Jens Weller
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk