Re: Limiting dependency Boost libraries

Subject: Re: Limiting dependency Boost libraries
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2018-06-22 18:38:26

On 2018-06-22 02:13 PM, Mateusz Loskot wrote:
> Hi,
>
> (Post-The Grand Merge ideas)
>
> The depinst.py below calculates maximum set of Boost libraries
> which are requirements of GIL:
>
> ```
> $ cd boost_root
> $ python tools/boostdep/depinst/depinst.py -v gil | grep dependency
> Adding dependency config
> Adding dependency core
> Adding dependency mpl
> Adding dependency iterator
> Adding dependency integer
> Adding dependency type_traits
> Adding dependency concept_check
> Adding dependency static_assert
> Adding dependency bind
> Adding dependency preprocessor
> Adding dependency function
> Adding dependency lexical_cast
> Adding dependency smart_ptr
> Adding dependency array
> Adding dependency lambda
> Adding dependency numeric/conversion
> Adding dependency algorithm
> Adding dependency filesystem
> Adding dependency test
> Adding dependency crc
> ```
>
> The depinst.py does
> - only scan GIL headers
> - not analyse conditional #include-s, so for some compilation
>    cases, some dependencies may not be required.

In addition, it would be very useful to know whether the dependencies 
are for the library itself, or for the tests only.

>
> Since GIL switched to C++11, some may be obvious candidates to get rid of.
>
> Could we brainstorm some priority list of dependencies?
> - trivial to remove
> - non-trivial to remove
> - impossible to removed
>
> Shall we open GH issue for this?

I have created https://github.com/boostorg/gil/projects/3 so we can 
experiment with the (relatively) new "project" artefact on github. Yes, 
I think such an endeavor would be very useful indeed.

Stefan

--
       ...ich hab' noch einen Koffer in Berlin...