How do I download module Core?

newer
[boost.test] Invoking test case...

older
[modular] Re: [regression] Test...

Andrzej Krzemienski

13 Jun 2014 13 Jun '14

3:16 p.m.

Hi, I can see that module Core is already available on branch Master. But when I try to pull the sources from GitHub (with 'git pull --rebase') it doesn't show up in my clone. Do I need to do anything to see it? Regards, &rzej

Show replies by date

Andrey Semashev

13 Jun 13 Jun

3:20 p.m.

On Friday 13 June 2014 17:16:02 Andrzej Krzemienski wrote:

...

Hi, I can see that module Core is already available on branch Master. But when I try to pull the sources from GitHub (with 'git pull --rebase') it doesn't show up in my clone. Do I need to do anything to see it?

You need to run 'git submodule update --init' to initialize new submodules in the local copy. Also don't forget to recreate the links to headers by removing boost folder and running 'b2 headers'.

Edward Diener

6:48 p.m.

On 6/13/2014 11:20 AM, Andrey Semashev wrote:

...

On Friday 13 June 2014 17:16:02 Andrzej Krzemienski wrote:

...
Hi, I can see that module Core is already available on branch Master. But when I try to pull the sources from GitHub (with 'git pull --rebase') it doesn't show up in my clone. Do I need to do anything to see it?

You need to run 'git submodule update --init' to initialize new submodules in the local copy. Also don't forget to recreate the links to headers by removing boost folder and running 'b2 headers'.

Is it really necessary to remove the boost folder before running 'b2 headers' in any situation ?

Andrey Semashev

7:52 p.m.

On Fri, Jun 13, 2014 at 10:48 PM, Edward Diener wrote:

...

On 6/13/2014 11:20 AM, Andrey Semashev wrote:

...
Also don't forget to recreate the links to headers by removing boost folder and running 'b2 headers'.

Is it really necessary to remove the boost folder before running 'b2 headers' in any situation ?

Frankly, I don't know. But I know this way it works 100%.

Peter Dimov

7:57 p.m.

Edward Diener wrote:

...

Is it really necessary to remove the boost folder before running 'b2 headers' in any situation ?

I think that when a header is removed altogether, the hard link (under Windows) can remain in boost/ and doesn't seem to be pruned by "b2 headers". Apart from that, everything else should be updated properly, at least in theory.

Edward Diener

14 Jun 14 Jun

6:11 a.m.

On 6/13/2014 3:57 PM, Peter Dimov wrote:

...

Edward Diener wrote:

...
Is it really necessary to remove the boost folder before running 'b2 headers' in any situation ?

I think that when a header is removed altogether, the hard link (under Windows) can remain in boost/ and doesn't seem to be pruned by "b2 headers". Apart from that, everything else should be updated properly, at least in theory.

Running 'b2 headers' now creates symbolic links in Windows for me.

Paul A. Bristow

8:37 a.m.

...

-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Edward Diener Sent: 13 June 2014 19:48 To: boost@lists.boost.org Subject: Re: [boost] How do I download module Core?

On 6/13/2014 11:20 AM, Andrey Semashev wrote:

...
On Friday 13 June 2014 17:16:02 Andrzej Krzemienski wrote:

...
Hi, I can see that module Core is already available on branch Master. But when I try to pull the sources from GitHub (with 'git pull --rebase') it doesn't show up in my clone. Do I need to do anything to see it?

You need to run 'git submodule update --init' to initialize new submodules in the local copy. Also don't forget to recreate the links to headers by removing boost folder and running 'b2 headers'.

Is it really necessary to remove the boost folder before running 'b2 headers' in any situation ?

I found/got things in a muddle and deleting /boost was the only action that resolved the problem. It should not be necessary, but equally it *should not* cause trouble? This whole system is too complicated for its or our good ! But I fear it is the price of GIT :-( Paul PS Doesn't b2 headers get hard links unless 'run as administrator' on Windows for symlinks? --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 01539 561830

Andrzej Krzemienski

13 Jun 13 Jun

7:53 p.m.

2014-06-13 17:20 GMT+02:00 Andrey Semashev :

...

On Friday 13 June 2014 17:16:02 Andrzej Krzemienski wrote:

...
Hi, I can see that module Core is already available on branch Master. But when I try to pull the sources from GitHub (with 'git pull --rebase') it doesn't show up in my clone. Do I need to do anything to see it?

You need to run 'git submodule update --init' to initialize new submodules in the local copy. Also don't forget to recreate the links to headers by removing boost folder and running 'b2 headers'.

Ouch. I wish I hadn't done it. Now I cannot compile my lib anymore. It looks like throw_exception uses BOOST_NORETURN, whose definition cannot be found. Where is BOOST_NORETURN supposed to be defined? Regards, &rzej

Peter Dimov

7:59 p.m.

Andrzej Krzemienski wrote:

...

Ouch. I wish I hadn't done it. Now I cannot compile my lib anymore. It looks like throw_exception uses BOOST_NORETURN, whose definition cannot be found. Where is BOOST_NORETURN supposed to be defined?

In boost/config/suffix.hpp.

Andrey Semashev

8:08 p.m.

On Fri, Jun 13, 2014 at 11:53 PM, Andrzej Krzemienski wrote:

...

2014-06-13 17:20 GMT+02:00 Andrey Semashev :

...
On Friday 13 June 2014 17:16:02 Andrzej Krzemienski wrote:

...
Hi, I can see that module Core is already available on branch Master. But when I try to pull the sources from GitHub (with 'git pull --rebase') it doesn't show up in my clone. Do I need to do anything to see it?

You need to run 'git submodule update --init' to initialize new submodules in the local copy. Also don't forget to recreate the links to headers by removing boost folder and running 'b2 headers'.

Ouch. I wish I hadn't done it. Now I cannot compile my lib anymore. It looks like throw_exception uses BOOST_NORETURN, whose definition cannot be found. Where is BOOST_NORETURN supposed to be defined?

BOOST_NORETURN is defined by Boost.Config. You probably didn't update all submodules. Strange, I thought 'git submodule update --init' would do that. I usually use these two commands to perform the complete Boost tree update: git pull --recurse-submodules git submodule foreach git merge --ff-only Note that the second command uses merge.defaultToUpstream = true setting so that I don't have to specify the branch. If you didn't set this parameter in your git config and you have all submodules checked out on a particular branch (e.g. master), you can modify the second command like this: git submodule foreach git merge --ff-only origin/master

Andrzej Krzemienski

10:59 p.m.

2014-06-13 22:08 GMT+02:00 Andrey Semashev :

...

On Fri, Jun 13, 2014 at 11:53 PM, Andrzej Krzemienski wrote:

...
2014-06-13 17:20 GMT+02:00 Andrey Semashev :

...
On Friday 13 June 2014 17:16:02 Andrzej Krzemienski wrote:

...
Hi, I can see that module Core is already available on branch Master. But when I try to pull the sources from GitHub (with 'git pull --rebase') it doesn't show up in my clone. Do I need to do anything to see it?

You need to run 'git submodule update --init' to initialize new submodules in the local copy. Also don't forget to recreate the links to headers by removing boost folder and running 'b2 headers'.

Ouch. I wish I hadn't done it. Now I cannot compile my lib anymore. It looks like throw_exception uses BOOST_NORETURN, whose definition cannot be found. Where is BOOST_NORETURN supposed to be defined?

BOOST_NORETURN is defined by Boost.Config. You probably didn't update all submodules. Strange, I thought 'git submodule update --init' would do that.

I usually use these two commands to perform the complete Boost tree update:

git pull --recurse-submodules git submodule foreach git merge --ff-only

Note that the second command uses merge.defaultToUpstream = true setting so that I don't have to specify the branch. If you didn't set this parameter in your git config and you have all submodules checked out on a particular branch (e.g. master), you can modify the second command like this:

git submodule foreach git merge --ff-only origin/master

Thanks. This solved most of my problems. However, I observed that some links are just not created when I run `b2 headers`, no matter if I remove boost, re-run. I had to manually add a couple of links when compiling with `toolset=gcc`. When compiling with visual C++, I had to manually copy some folders: folder modular-boost\libs\preprocessor\include\boost\preprocessor\iteration\detail\ contents of modular-boost\libs\preprocessor\include\boost\preprocessor\slot folder modular-boost\libs\exception\include\boost\exception\detail Regards, &rzej

3818

Age (days ago)

3819

Last active (days ago)

List overview

Download

10 comments

5 participants

participants (5)

Andrey Semashev
Andrzej Krzemienski
Edward Diener
Paul A. Bristow
Peter Dimov