On Fri, Jun 13, 2014 at 11:53 PM, Andrzej Krzemienski
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