Re: [boost] [conversion] Serious header integrity test failures.

Subject: Re: [boost] [conversion] Serious header integrity test failures.
From: Dave Abrahams (dave_at_[hidden])
Date: 2013-11-27 11:05:26

Daniel James <daniel_at_[hidden]> writes:

> On 25 November 2013 14:07, Beman Dawes <bdawes_at_[hidden]> wrote:
>> On Mon, Nov 25, 2013 at 8:18 AM, Daniel James <daniel_at_[hidden]>wrote:
>> ...
>>
>>>  just tried:
>>>
>>> git clone --recursive -b develop git_at_[hidden]:boostorg/boost.git
>>> boost-develop
>>>
>>> And that worked fine.
>>>
>>> I think you're doing a recursive clone of master and then switching to
>>> the branch. In which case I think you need to use 'git submodule
>>> update --init' to initialise modules on this branch before updating
>>> (untested and possibly wrong).
>>>
>>
>> At Dave's suggestion, I tried this last night:
>>
>> git clone --recursive git_at_[hidden]:boostorg/boost.git modular-boost
>> cd modular-boost
>> ...
>> git checkout develop
>> git module update
>>
>> It worked fine, and that's what I used to run the develop header file
>> verification that worked correctly.
>
> But it was missing sync, wasn't it? That's why I think you need to use
> 'git module update --init'.

I think you would need --init if the branch to which you were switching
contained submodules that weren't present in the branch from which you
were switching.  In any case, it can't hurt.

>
>> git clone --recursive git_at_[hidden]:boostorg/boost.git modular-boost
>> cd modular-boost
>> ./bootstrap.sh
>> ./b2 headers
>> git checkout master
>> git submodule update
>> cd libs/my-lib
>> git checkout develop
> [...]
>> Is the sequence of commands above what the developer of my-lib should do to
>> get started?
>
> I didn't need 'git checkout master' and 'git submodule update'. The
> wiki page says the modular-boost repo will be detached, but it wasn't
> for me (the submodules were).
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost