Re: [boost] [modular boost] non-linked headers

Subject: Re: [boost] [modular boost] non-linked headers
From: Edward Diener (eldiener_at_[hidden])
Date: 2013-12-02 18:39:49

On 12/2/2013 5:29 PM, Bjørn Roald wrote:
> On 12/02/2013 10:45 PM, Edward Diener wrote:
>> On Windows after the .\b2 headers step, there are these directories
>> under the modular-boost/boost diectory which are not symbolic links:
>>
>> detail
>
> It is because they have more than one source directory, so a symbolic
> link will not do what is needed.

Symbolic links can be created to individual files also.

>  I do not think windows is changing
> anything unless you are on a version not supporting symbolic links.
>
> $ find libs -name detail | grep include/boost/detail
> libs/optional/include/boost/detail
> libs/detail/include/boost/detail
> libs/thread/include/boost/detail
> libs/config/include/boost/detail
> libs/smart_ptr/include/boost/detail
> libs/utility/include/boost/detail
> libs/conversion/include/boost/detail
> libs/graph/include/boost/detail
> libs/dynamic_bitset/include/boost/detail

Just looking at detail we are evidently creating duplicating files 
rather than creating symbolic links to files.

For instance in libs/detail, which is a submodule, we have 
allocator_utilities.hpp. In boost/detail we have 
allocator_utilities.hpp. Let us suppose that the 
libs/detail/allocator_utilities.hpp gets updated in git. When this 
happens, how is the boost/detail/allocator_utilities.hpp supposed to be 
updated if it is an entirely separate file ?